Martin

I didn’t want to set a domain key in this practical case, but resetting settings fix that issue for me.

I had that message in old tab, if needed

Plugin could not be activated because it triggered a?fatal error.

Fatal error: Uncaught Error: Call to undefined method WPCOM_REST_API_V2_Endpoint_Publicize_Share_Post::httpRequest() in /home/x/public_html/wp-content/plugins/cleantalk-spam-protect/inc/cleantalk-pluggable.php:1435 Stack trace: #0 /home/x/public_html/wp-content/plugins/cleantalk-spam-protect/lib/Cleantalk/ApbctWP/Activator.php(15): apbct_settings__get_ajax_type() #1 /home/x/public_html/wp-content/plugins/cleantalk-spam-protect/cleantalk.php(852): Cleantalk\ApbctWP\Activator::activation() #2 /home/x/public_html/wp-includes/class-wp-hook.php(324): apbct_activation() #3 /home/x/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #4 /home/x/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /home/x/public_html/wp-admin/plugins.php(196): do_action() #6 {main} thrown in /home/x/public_html/wp-content/plugins/cleantalk-spam-protect/inc/cleantalk-pluggable.php on line 1435

I did that after that error but at that time WordPress did not allow to activate plugin cuz of similiar error. But now it worked fine. So yea ??

Yeah that fix my issues ??, thanks! ??

On another website i also see:

Creation of dynamic property RankMathPro\Image_Seo_Pro::$title_change_case is deprecated in /home/x/public_html/wp-content/plugins/seo-by-rank-math-pro/includes/modules/image-seo/class-image-seo-pro.php on line 178

Creation of dynamic property RankMathPro\Image_Seo_Pro::$alt_change_case is deprecated in /home/x/public_html/wp-content/plugins/seo-by-rank-math-pro/includes/modules/image-seo/class-image-seo-pro.php on line 177

Sure, here is example:

<div wire:id="HzX2QOpnGrrlH6ByTfZu" ...> ...component... </div>

<!-- Livewire Component wire-end:HzX2QOpnGrrlH6ByTfZu -->

@niklasinpsyde could you show how that implementation should look like?

PS. 7.3.9 broke compatibility for me since we are using newer psr/container (from external dependency :F)

Yep, you right I didn’t update pro variant and that fix the issue ??