error 500 when cred updated to 2.21 on wprdpress 5

Este hilo está resuelto. Aquí tiene una descripción del problema y la solución.

Problem:
error 500 when cred updated to 2.21 on wprdpress 5

Solution:
User somehow do not able to update the plugins correctly. To resolve this issue, delete the existing Toolset plugins and upload it manually using the plugins page.

You can find the proposed solution, in this case, with the following reply:
https://toolset.com/forums/topic/error-500-when-cred-updated-to-2-21-on-wprdpress-5/#post-1169628

Relevant Documentation:

This support ticket is created hace 6 años, 1 mes. 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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	10:00 – 13:00	10:00 – 13:00	10:00 – 13:00	10:00 – 13:00	10:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Kolkata (GMT+05:30)

Etiquetado: Toolset Forms

Este tema contiene 6 respuestas, tiene 3 mensajes.

Última actualización por AndreG3332 hace 6 años.

Asistido por: Minesh.

Autor

Mensajes

diciembre 7, 2018 at 9:06 am #1161402

AndreG3332

The Cred plugin 2.2.1 cause an error 500 on WordPress 5 when activated. We had to remove the plugin and revert to the previous version to carry on working.

This is for information more than support

diciembre 7, 2018 at 10:23 am #1161463

Beda

I have WordPress 5.0 and Forms 2.2.1 installed since they are in RC (and now stable), and have no issues.
I also see no other reports of this so far.

Error 500 always means there is an underlying PHP error
Can you enable WP Debug and tell us the error, as well as if it still happens when not using any other Plugin but Toolset (on testing site, eventually)
https://codex.wordpress.org/WP_DEBUG

Then we will be able to tell why the E500, and what to do to solve it.

You can also add a copy of your site, if you have one, so we can take a look, in case it persist after above steps:
https://toolset.com/faq/provide-supporters-copy-site/

diciembre 19, 2018 at 9:36 am #1169468

AndreG3332

After activating the wp-debug and activating the views plugin i got this error message. I am now running on wordpress 5.01 and views 2.7.

Fatal error: Uncaught Error: Undefined class constant 'CALLBACK_GET_VIEW_BLOCK_PREVIEW' in /home/trackdoc/bvigrg.trackdoc.co.za/wp-content/plugins/wp-views/application/controllers/compatibility/editor-blocks/blocks/view/view.php:61 Stack trace: #0 /home/trackdoc/bvigrg.trackdoc.co.za/wp-includes/class-wp-hook.php(286): OTGS\Toolset\Views\Controller\Compatibility\EditorBlocks\View\Block->register_block_editor_assets('') #1 /home/trackdoc/bvigrg.trackdoc.co.za/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #2 /home/trackdoc/bvigrg.trackdoc.co.za/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #3 /home/trackdoc/bvigrg.trackdoc.co.za/wp-settings.php(467): do_action('init') #4 /home/trackdoc/bvigrg.trackdoc.co.za/wp-config.php(90): require_once('/home/trackdoc/...') #5 /home/trackdoc/bvigrg.trackdoc.co.za/wp-load.php(37): require_once('/home/trackdoc/...') #6 /home/trackdoc/bvigrg.trackdoc.co.za/wp-admin/admin.php(31): require_once('/home/trackdoc/...') #7 /home/trackdoc/bvigrg.trackdoc.co.za/wp in /home/trackdoc/bvigrg.trackdoc.co.za/wp-content/plugins/wp-views/application/controllers/compatibility/editor-blocks/blocks/view/view.php on line 61

diciembre 19, 2018 at 10:00 am #1169491