Hello,
Updating my WP from 6.5 to 6.6.1 I get issues with patterns.
- with all plugins deactivated includint Toolset I get the correct Appearence/patterns screen with all patterns listed
- deactivating all Toolset plugins but Types in Appearence/patterns I get the patterns screen but empty, no patterns listed; same with Toolset Forms activated
- activating Toolset Blocks in Appearence/patterns I get the empty patterns screen for a while then a black page
- with all plugins activated when a page includes a pattern made with a Kadence Row layout that includes a Toolset View the page edit hangs unable to load the code
All Toolset plugins are updated to their latest versions.
Currently my site is updated to 6.6.1 for you to test, I can restore a snapshot with 6.5 if you need to.
Please let me know thanks
Nicola
Hello. Thank you for contacting the Toolset support.
If you get a white or empty screen there is a great possibility that you have PHP errors on the server, and you need to check you debug.log to find what they are.
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:
Hello Minesh,
I added the lines you suggested me to my wp-config like this
define( 'WP_DEBUG', true );
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DISABLE_FATAL_ERROR_HANDLER',true);
define( 'WP_MEMORY_LIMIT', '1024M' );
define( 'WP_SITEURL', 'hidden link' );
/* That's all, stop editing! Happy publishing. */
/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) ) {
define( 'ABSPATH', dirname(__FILE__) . '/' );
}
/** Sets up WordPress vars and included files. */
require_once ABSPATH . 'wp-settings.php';
define( 'TOOLSET_CODE_SNIPPETS_TEST_MODE', true );
define('WP_AUTO_UPDATE_CORE', false);
but no debug.log in wp-content is created.
I don't see a white screen, I see a BLACK screen when opening Appearance/Patterns, see picture
thanks
- with all plugins deactivated includint Toolset I get the correct Appearence/patterns screen with all patterns listed
===>
ok
- deactivating all Toolset plugins but Types in Appearence/patterns I get the patterns screen but empty, no patterns listed; same with Toolset Forms activated
===>
That is strange
- activating Toolset Blocks in Appearence/patterns I get the empty patterns screen for a while then a black page
===>
That is strange
- with all plugins activated when a page includes a pattern made with a Kadence Row layout that includes a Toolset View the page edit hangs unable to load the code
===>
That is strange. Can you please share the link of this page where I can see the issue?
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Hello Minesh,
I could replicate the issue in your sandbox. I have created a simple view, placed in the Sample Page and created a SYNCHED pattern with the view inside. After hitting SAVE the page hangs (see attachment) and in Appearence/Patterns the preview result isn't shown. The only difference with my site is that in my Appearence/Patterns I see a black page. I suppose there is some kind of conflict between Toolset Blocks and Patterns in WP 6.6.1, please ask developers to have a look
thanks
*** Please make a FULL BACKUP of your database and website.***
However - Can you please share duplicator package of your site and I will share with our next level support so that they can use it if required as you have issue on pattern listing page at:
=> Appearance => Patterns
Ok thanks,
due to this bug I had to remove patterns from all pages, the only one left with the banners is page called Banner Master (21627) that shows the issue, pls let developers know, thanks
I already escalated the issue what we found on sandbox and our Devs are working on that. Lets wait for the fix and see if the fix shared by Devs help fix all issues or we have another issue as well.
