Once toolset is activate, I'm getting error for each action

This support ticket is created hace 5 años, 6 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	-
-	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	-

Supporter timezone: Europe/London (GMT+00:00)

Etiquetado: Types plugin, Views plugin

Este tema contiene 1 respuesta, tiene 2 mensajes.

Última actualización por Nigel hace 5 años, 6 meses.

Asistido por: Nigel.

Autor

Mensajes

mayo 14, 2019 at 9:00 am #1243467

linaS

Hello,

I installed a "clean" version of wordpress (last version 5.2),
Then Iv'e installed types & views plugin,
Once it activated I'm getting error on each action I'm, doing- contact update, enable / disable plugin or thems ETC
the action is apply but its redirect me to error page (image attached).

Once I disabled toolset plugins everything works well,

mayo 14, 2019 at 10:34 am #1243536

Nigel

Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

Hi there

Do you see any problems in your debug.log?

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

That will create a debug.log file in your /wp-content/ directory which you can examine in any text editor. With Types and Views active try performing some of the actions that are creating problems as you describe above. Then inspect the log. If you don't find the debug.log file it means it didn't generate any warnings or errors.

Can you let me know what you find?