Skip Navigation

[Gelöst] Critical error trying to edit content template

Dieser Thread wurde gelöst. Hier ist eine Beschreibung des Problems und der Lösung.

Problem:

I just installed toolset blocks, created a content template and when it went to edit I get this error:

https://toolset.com/forums/topic/critical-error-trying-to-edit-content-template/#post-2339865

Solution:

Uninstalled and reinstalled all toolset plugins, and the issue was resolved

Relevant Documentation:

This support ticket is created vor 2 Jahren, 7 Monaten. 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.

Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9: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/Hong_Kong (GMT+08:00)

Dieses Thema enthält 5 Antworten, hat 2 Stimmen.

Zuletzt aktualisiert von OliverJ8211 vor 2 Jahren, 7 Monaten.

Assistiert von: Luo Yang.

Author
Artikel
#2339865

I'm trying to edit a content template on a dev site. I just installed toolset blocks, created a content template and when it went to edit I get this error:

Error Details
=============
An error of type E_ERROR was caused in line 753 of the file /home/ryanr63303/public_html/newsite-medicaremanstl/wp-content/plugins/types/vendor/toolset/toolset-common/user-editors/editor/screen/gutenberg/backend.php. Error message: Uncaught Error: Call to undefined method WPV_Settings::has_ct_assigned_to_cpt_archive() in /home/ryanr63303/public_html/newsite-medicaremanstl/wp-content/plugins/types/vendor/toolset/toolset-common/user-editors/editor/screen/gutenberg/backend.php:753
Stack trace:
#0 /home/ryanr63303/public_html/newsite-medicaremanstl/wp-content/plugins/types/vendor/toolset/toolset-common/user-editors/editor/screen/gutenberg/backend.php(380): Toolset_User_Editors_Editor_Screen_Gutenberg_Backend->has_cpt_usage()
#1 /home/ryanr63303/public_html/newsite-medicaremanstl/wp-content/plugins/types/vendor/toolset/toolset-common/user-editors/editor/screen/gutenberg/backend.php(280): Toolset_User_Editors_Editor_Screen_Gutenberg_Backend->add_metaboxes()
#2 /home/ryanr63303/public_html/newsite-medicaremanstl/wp-includes/class-wp-hook.php(307): Toolset_User_Editors_Editor_Screen_Gutenberg_Backend->register_metaboxes_for_gutenberg_compatibility('')
#3 /home/ryanr63303/public_html/newsite-medicaremanstl/wp-includes/class-wp-hook.php(331): WP_

#2340079

Hello,

I have searched it in our forum, found some related threads, for example:
https://toolset.com/forums/topic/cannot-create-content-template-for-woocommerce-product-page/
https://toolset.com/forums/topic/toolset-blocks-cause-critical-error/

Please check these in your website:
1) Make sure your website is using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) If you are using cache plugins in your website, clear your website cache and test again.

#2340645

This is a new site with up to date toolset plugins and no caching installed yet.

#2340869

The problem is abnormal, please try to duplicate the same problem in a fresh WP installation, and provide the test site copy in below private message box, you can put the package files in your own google drive disk, share the link only, also point out the problem page URL, I need to test and debug it in my localhost:
https://toolset.com/faq/provide-supporters-copy-site/

#2341609

I uninstalled and reinstalled all toolset plugins and the issue was resolved. Did that at the beginning as well, but it worked this time. Thank You for your help and time. I appreciate it.

#2341617

My issue is resolved now. Thank you!