Roman Axelrod

@harthur90 , is there a way for us to edit or change the classification of pages?

In our case, the plugin classified our created custom post types as “blog-post”.
How can we change it to “landing-page” ?

Same here, subscribing to the issue.

@kurudrive Thank you so much!
It’s working now ??

Just like you mentioned in changelog, looks like the issue is related to removed post-types.

Thank you for your help!

Sorry for the mess,

I think I got the error on old version (v1.30.0) and this is why error was related to line 143. Then, I updated to latest, it didn’t help and I added my patch here:
https://github.com/vektor-inc/vk-block-patterns/blob/7ee1e203838d62f640a72df531f066fe6fdd4b52/inc/vk-block-patterns/package/class-vk-block-patterns.php#L193

Thank you for providing the github link – this is useful!

Hey @kurudrive , yes – this is latest version 1.30.2.

I ended up with adding the next peace of code after line 142:

if(empty($post_type_object)){ continue; }

Before usage of $post_type_object->template.

I got the same issue.
Simple “get_posts()” or “get_field()” inside the filter (elementor/query/filter) will crash the editor. From my I see, it puts the PHP code in loop.

Code example:

add_action( 'elementor/query/suggested', function ( $query ) {
	get_posts(); //  Fatal error: Uncaught Error: Xdebug has detected a possible infinite loop, and aborted your script with a stack depth of '256' frames
} );

• This reply was modified 1 year, 9 months ago by Roman Axelrod.

Same issue here.

I am going to downgrade the plugin on our website.
Please update us once the issue is fixed or if you need any additional info.

Thank you!

• This reply was modified 1 year, 12 months ago by Roman Axelrod.

Hey All,

Just letting you that you’re not alone – I experience the same issue with “stuck” tabs on each refresh in Chrome v105. Tested the issue on multiple websites and the result is the same, even on very basic WordPress installation.

So the development work is painful in these conditions. As a temporary solution I disable the QueryMonitor plugin and activate only when I really need it.

I believe the issue will be solved in next Chrome releases.

The function wp_is_block_theme introduced in WordPress v5.9 and was used in Yoast v18.3:
https://github.com/Yoast/wordpress-seo/commit/26d29e8c0cb19b0825d89f0fc1d861c75b27e556

Means the Yoast v18.3 is not compatible with 5.8.3 that we are still using.

Obviously, the best solution is to update the WordPress core to latest version.

• This reply was modified 2 years, 8 months ago by Roman Axelrod.

Same here.
Rollback to v18.2 fixed the issue.

Hey @munirkamal ,

Thank you for letting me know and thank you for your hard work.
I will test the new update and will let you know if I face any issues.

Have a great day!

Hey @dannyfoo ,

Thank you for your quick response!
I am happy that you found a “workaround”.

I guess, I will use “shortcode” as a solution.
Leaving here details for other users who might struggle with the issue.

# Shortcode Solution:
Here is the setting on Elementor’s sidebar:
https://i.ibb.co/JqCfhLR/Screenshot-2021-01-05-T153240-166.png

And here is the simple shortcode that returns Archive URL of current post:

add_shortcode( 'get_archive_url', function () {
   return get_post_type_archive_link( get_post_type() );
} );

• This reply was modified 3 years, 10 months ago by Roman Axelrod.

Hey @dannyfoo,

We have exactly the same issue with Elementor & Pods.

Have you found solution to this case?