Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • I tracked the issue back to a bunch of blocks, which all use the post selector. Since the last plugin update (June 30th) I cannot use them any more like I could before. I see an error in the editor as well, when I try to add them. When I update the plugin to the latest version (July 6th), I get a plugin has no header issue and also a plugin error I posted in my reply here and wordpress changes to recovery mode.

    I followed you suggested options and switched the blocks to php code in functions.php instead of the admin interface ony my staging environment, but this only solved the plugin error in the plugin list. I cannot add the blocks anymore, like I could in the versions before.

    Regarding the blocks, I have a post selector, where users can choose the posts they want to display in this block. In the combined code for FE & BE I go through that selected post objects via foreach like your documentation shows, I check for post_thumbnail and build a post grid with the selected posts and print them out via echo post by post.

    <?php 
    foreach( $attributes['post-obj-select'] as $post_selects ):
    
    /** Check Post_Thumbnail **/
     if (has_post_thumbnail( $post_selects->ID ) ) {
       $img = get_the_post_thumbnail_url( $post_selects->ID, "post-teaser" );
     } else {
       $img = 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==';
     }
     
    echo '<a href="'.get_the_permalink($post_selects->ID).'"><img class="img-responsive wp-image-'.$post_selects->ID.'" src="'.$img.'" /><h4>'.esc_html($post_selects->post_title).'</h4></a>';
     
    endforeach; 
    ?> 

    When I use the code without the block environment as vanilla php, I don’t get any errors or warnings. Why is this causing troubles? The Log file only tells me about the eval()’d issue. All I changed is the version of the plugin.

    Thank you for any advice, how I can solve this issue.
    BR M

    Okay, thank you. I think I can track that back to one of the custom blocks, where we used a different output method for the editor view.

    Best regards,
    Markus

    We use php 8.1., so that is not the issue. My error message is a bit different, but it’s caused by the same file:

    Error Type E_ERROR in line 7 of the file xxxx/wp-content/plugins/lazy-blocks-pro/core-plugin/classes/class-blocks.php(1359) : eval()’d code causes error: Uncaught TypeError: Cannot access offset of type string on string in xxx/wp-content/plugins/lazy-blocks-pro/core-plugin/classes/class-blocks.php(1359) : eval()’d code:7 Stack trace:

    #0 xxxx/wp-content/plugins/lazy-blocks-pro/core-plugin/classes/class-blocks.php(1359): eval()

    #1 xxxx/wp-content/plugins/lazy-blocks-pro/core-plugin/classes/class-blocks.php(1519): LazyBlocks_Blocks->php_eval()

    #2 xxxx/wp-content/plugins/lazy-blocks-pro/core-plugin/classes/class-blocks.php(1391): LazyBlocks_Blocks->render_callback()

    Same here in Pro Version. Hope, this is getting fixed soon as it also happened in production environment.

    I did update the plugin via Update Admin Interface in the WP Backend and the same problem occured. I tried first via ManageWP Interface but received and error while downloading zip file as a response.

    So I downgraded with the 3.3. Version .zip directly on both the servers, as the error did not disappear.

    Any idea why this could happen?

    There is an advanced view on every plugin page, where you can download previous releases by version number e.g. here:

    https://ww.wp.xz.cn/plugins/polylang/advanced/

    Same here. Had to downgrade to 3.3. Version. Waiting for a fix of this bug.

    Update crashed all my setups. Moved back to last stable version. That’s 13.5. and 14.3. for me. Had an comparable issue by migrating from 13.x to 14.0

    WordPress 5.4.2
    All other plugins up to date
    PHP version 7.3.14-1

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    Error Details
    =============

    An error of type E_ERROR was caused in line 1441 of the file /srv/wordpress/wp-content/plugins/wordpress-seo/src/generated/container.php. Error message: Uncaught Error: Class ‘Yoast\WP\Lib\Migrations\Adapter’ not found in /srv/wordpress/wp-content/plugins/wordpress-seo/src/generated/container.php:1441
    Stack trace:
    #0 /srv/wordpress/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php(271): Yoast\WP\SEO\Generated\Cached_Container->getMigrationRunnerService()
    #1 /srv/wordpress/wp-content/plugins/wordpress-seo/src/loader.php(191): YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container->get(‘Yoast\\WP\\SEO\\In…’)
    #2 /srv/wordpress/wp-content/plugins/wordpress-seo/src/loader.php(136): Yoast\WP\SEO\Loader->load_initializers()
    #3 /srv/wordpress/wp-content/plugins/wordpress-seo/src/main.php(81): Yoast\WP\SEO\Loader->load()
    #4 /srv/wordpress/wp-content/plugins/wordpress-seo/src/functions.php(26): Yoast\WP\SEO\Main->load()
    #5 /srv/wordpress/wp-content/plugins/wordpress-seo/wp-seo-main.php(341): YoastSEO()
    #6 /srv/wordpress/5.4.2/wp-includes/class-wp-hook.php(287): wpseo_init(”)
    #7 /srv/wordpress/5.4.2/wp-includes/class

Viewing 8 replies - 1 through 8 (of 8 total)