Same. I’m glad it’s not just me, and I hope this gets sorted. I have a lot of work to do on my website.
I also encountered the same error.
I’m not sure if it’s a fundamental solution, adding the following code to the theme’s function.php made the error disappear.
function my_function_name() {
remove_action( 'admin_print_scripts', 'print_emoji_detection_script' );
}
add_action( 'pre_get_posts', 'my_function_name' );
I hope this can be of some help.
-
This reply was modified 3 years, 1 month ago by
kesasakisti.
I’m wary to edit my theme like this. I appreciate the input, hopefully this gives AIOSEO creators some insight into the problem so they can fix it faster.
This should’ve been avoid. I think all SEO plugins need to say up to date with at least PHP 8.0 and WordPress updates.
I’ve uninstalled the plugin this from clients website.
I’m going to try Yoast.
The irony is on the AIOSEO and parent company website they have articles about the new 6.2 WordPress update. I checked these articles for comments to see if others had similar experiences.
Same here. If I want to edit a page or post it loads endlessly. Rolling back to WP 6.1 until fix.
Question: Does uninstalling AIOSEO and installing another SEO plugin remove changes made to already done posts?
It’s very strange that developers don’t test their plugins for compatibility..
-
This reply was modified 3 years, 1 month ago by
rexru19.
BTW I advise everyone who wants this fixed as soon as possible to contact AIOSEO via their website contact form and tell them they are not alone in having this trouble.
I’m sure at this point they are aware of it and working on the solution, but the more people that contact the higher up the priority list the solution will go.
I’m having the same problem.. I couldn’t find a solution
in my case, the above solution in function.php seems to work and get rid of the problem for now.
function my_function_name() {
remove_action( 'admin_print_scripts', 'print_emoji_detection_script' );
}
add_action( 'pre_get_posts', 'my_function_name' );
https://wordpress.org/support/topic/wordpress-6-2-3/#post-16608684
Hey everyone,
Our development team is currently troubleshooting the issue and working on a fix. This our highest priority at the moment so I’ll be back with an update soon.
We thoroughly tested our plugin with WordPress 6.2 before it was released, but it looks like this specific issue only happens on Windows machines with Google Chrome, the Classic Editor and the latest version of WordPress.
@arnaudbroes I’m not using Windows. I’m on Ubuntu Linux Distro 20.04.6 and macOS 13.0.1.
Safari, FireFox, Chrome. All are current to the latest versions released to date.
Seems like Yoast should be avoided also. They’re having issues unrelated to the updates though.
