Patterns Requiring a Save Before They can Be Inserted or Page Unresponsive

  • Pcosta88

    (@pcosta88)


    3 months ago

    Hey all,

    I have a client who had an issue when adding a pattern built in Kadence blocks. When trying to add it the page would kickout an “Unresponsive” warning. This happened in Chrome v127.0.6533.120  (no browser plugins active) and FireFox v129.0.1 (64-bit).

    See image: https://ibb.co/WktHRGv.

    I did a conflict check and it happened with a basic theme like 2024 v1.2 and Kadence Blocks v3.2.50 being the only one active on WordPress Core v6.6.1. I also rolled Kadence Blocks back to earlier versions going all the way down to 3.2.40 and the issue persisted.

    It was only after going to the pattern and re-saving it was I finally able to insert it.

    It’s not clear to me if this is something with your plugin or some goofy hiccup on the WordPress site.

    However, I wanted to ask if you’ve seen this issue before on your end?

    Also the error logs have the following errors, are you able to elaborate more on what these are?

    [19-Aug-2024 19:29:32 UTC] PHP Fatal error: Uncaught Error: Class ‘ComposerAutoloaderInit50d497dc9e859851f26e9cd8f38243ca’ not found in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/autoload.php:25
    Stack trace: 0 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/kadence-blocks.php(26): require_once() 1 /home/nginx/domains/domain_name_here.host_name_here/public/wp-settings.php(522): include_once(‘/home/nginx/dom…’) 2 /home/nginx/domains/domain_name_here.host_name_here/public/wp-config.php(114): require_once(‘/home/nginx/dom…’) 3 /home/nginx/domains/domain_name_here.host_name_here/public/wp-load.php(50): require_once(‘/home/nginx/dom…’) 4 /home/nginx/domains/domain_name_here.host_name_here/public/wp-admin/admin-ajax.php(22): require_once(‘/home/nginx/dom…’) 5 {main}

    thrown in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/autoload.php on line 25
    [19-Aug-2024 19:29:33 UTC] PHP Fatal error: Uncaught Error: Class ‘ComposerAutoloaderInit50d497dc9e859851f26e9cd8f38243ca’ not found in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/autoload.php:25
    Stack trace: 0 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/kadence-blocks.php(26): require_once() 1 /home/nginx/domains/domain_name_here.host_name_here/public/wp-settings.php(522): include_once(‘/home/nginx/dom…’) 2 /home/nginx/domains/domain_name_here.host_name_here/public/wp-config.php(114): require_once(‘/home/nginx/dom…’) 3 /home/nginx/domains/domain_name_here.host_name_here/public/wp-load.php(50): require_once(‘/home/nginx/dom…’) 4 /home/nginx/domains/domain_name_here.host_name_here/public/wp-admin/admin.php(34): require_once(‘/home/nginx/dom…’) 5 /home/nginx/domains/domain_name_here.host_name_here/public/wp-admin/post.php(12): require_once(‘/home/nginx/dom…’) 6 {main}

    thrown in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/autoload.php on line 25
    [19-Aug-2024 19:38:40 UTC] PHP Fatal error: Uncaught Error: Class ‘KadenceWP\KadenceBlocks\StellarWP\Uplink\Resources\Resource’ not found in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Resources/Plugin.php:13
    Stack trace: 0 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/autoload.php(10): require_once() 1 [internal function]: {closure}() 2 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Register.php(29): spl_autoload_call() 3 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/kadence-blocks.php(142): KadenceWP\KadenceBlocks\StellarWP\Uplink\Register::plugin() 4 /home/nginx/domains/domain_name_here.host_name_here/public/wp-includes/class-wp-hook.php(324): kadence_blocks_init() 5 /home/nginx/domains/domain_name_here in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Resources/Plugin.php on line 13

    [19-Aug-2024 19:45:01 UTC] PHP Fatal error: Uncaught LogicException: You cannot use the “KadenceWP\KadenceBlocks\Symfony\Component\String\Slugger\AsciiSlugger” as the “symfony/translation-contracts” package is not installed. Try running “composer require symfony/translation-contracts”. in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/symfony/string/Slugger/AsciiSlugger.php:21
    Stack trace: 0 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/autoload.php(10): require_once() 1 [internal function]: {closure}() 2 [internal function]: spl_autoload_call() 3 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/lucatume/di52/src/Builders/Factory.php(68): class_exists() 4 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/lucatume/di52/src/Container.php(540): Kadence in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/symfony/string/Slugger/AsciiSlugger.php on line 21

    [19-Aug-2024 19:46:05 UTC] PHP Fatal error: Uncaught Error: Class ‘KadenceWP\KadenceBlocks\StellarWP\Uplink\View\WordPress_View’ not found in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/View/Provider.php:21
    Stack trace: 0 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Uplink.php(45): KadenceWP\KadenceBlocks\StellarWP\Uplink\View\Provider->register() 1 /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/kadence-blocks.php(135): KadenceWP\KadenceBlocks\StellarWP\Uplink\Uplink::init() 2 /home/nginx/domains/domain_name_here.host_name_here/public/wp-includes/class-wp-hook.php(324): kadence_blocks_init() 3 /home/nginx/domains/domain_name_here.host_name_here/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 4 /home/nginx/domains/domain_name_here.host_name_here in /home/nginx/domains/domain_name_here.host_name_here/public/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/View/Provider.php on line 21

    • This topic was modified 3 months ago by Pcosta88.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support karlalevelup

    (@karlalevelup)

    Hi there!

    I’d be happy to assist you with this.

    The fatal errors are due to missing classes and files from our Kadence Blocks plugin. This folder and its files should be present, but the errors states otherwise – https://share.zight.com/P8uOjyN6

    If you have access to the website’s cPanel or File Transfer Protocol(FTP), I suggest verifying whether these are missing. If they are, reach out to the website’s hosting provider so they can check why some of the plugin files are missing. They might also be able to help you upload the complete plugin files manually.

    Patterns issue
    We have some users having issues with editing page freezing issue if there are Synched patterns are present in the content. However, it seem to be different from your issue. Also, there is an ongoing thread about it here – https://www.ads-software.com/support/topic/wp-6-6-hangs-on-synced-pattern/

    If you revert to WordPress 6.5, will the issue persist?

    Thread Starter Pcosta88

    (@pcosta88)

    @karlalevelup

    Thanks for the reply! I checked and the site does not have some of those files. See: https://i.imgur.com/n0Xr9Pu.png

    Additionally, the blocks/patterns in question are synched so it seems to be somewhat related to the issues other folks have mentioned.

    I’m unable to rollback WP Core.

    Plugin Support michael-levelup

    (@michaeltarongoy)

    Hi there,

    Thanks for confirming that.

    I suggest you reach out to your hosting provider.

    They can help you in reinstalling Kadence Blocks and root out why you seem to have an incomplete copy of the plugin installed. They can also assist you on doing a rollback to WordPress 6.5 as well.

    Let us know how we could help you further.

    Kind Regards,
    Michael Taro

    Thread Starter Pcosta88

    (@pcosta88)

    @michaeltarongoy

    I looked and the only thing missing is the vender prefix file and the autoload.php. I’m not sure these do or if they’re even relevant?

    For example, the lack of these files doesn’t seem to explain why I need to re-save the patterns before they can work. I would expect that if the files were important that re-saving wouldn’t fix the issue.

    Also, I downgraded to v6.5.5 of WordPress Core and the issue resolves.

    There seems to be bug probably related to this: https://www.ads-software.com/support/topic/wp-6-6-hangs-on-synced-pattern/.

    Let me know your thoughts or if there’s any additional actions you might recommend I take.

    kraisor

    (@kraisor)

    Having the same issue on our site as well. We also have Kadence installed and are unable to edit posts that have a synced reusable block/pattern.

    Rolling back to WordPress 6.5.5 fixed the issue for us.

    Plugin Support karlalevelup

    (@karlalevelup)

    Hi there!

    The fix wasn’t included in WordPress 6.6.2 yet. You can see the task for it here:?<u>Reusable blocks: fix performance of __experimentalGetAllowedPatterns #64871</u>
    ?

    I’ll keep track of this issue and send an update here once we checked further from our end or if a WordPress update fixes this issue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.