Incompatibility with ARVE (WP Interactivity API inside admin)

Yes, my website has also encountered the same problem.

There is compatibility issue with All In One SEO Pack effecting ARVE. With the AIO-SEO plugin active the “Embed Video (ARVE)” button will not work in Classic Editor. Please contact the AIO-SEO plugin support / support for pro users if they can fix this issue.

Hi @nico23 and @lvcz,

Thank you so much for reaching out and reporting the compatibility issue between AIOSEO and the ARVE plugin!

Our development team is now aware of this and has already opened an internal issue to investigate further.

We’ll keep you updated and get back to you as soon as we have more information or a fix for this.

Thanks for your patience, and feel free to reach out if you have any other questions in the meantime!

Hey @nico23,

Two of our developers have troubleshooted the issue on our end and found that it occurs due to an uncompiled script that is being loaded inside of your plugin, namely advanced-responsive-video-embedder/vendor/nextgenthemes/wp-shared/includes/WP/Admin/settings.js.

If you inspect that file, you’ll see that file imports dependencies from the WordPress interactivity library and is uncompiled. They tried compiling the file for testing purposes and that seemed to fix the issue where your settings page doesn’t load correctly.

Do you mind taking a look to see if you can reproduce this? If you have any questions, please let us know.

Hi @nico23 , I was also in touch with AIO SEO regarding this issue based on message in WP backend after last update and they referred me back to you:

“We have troubleshooted this issue and found that this is not in fact an issue on our end, but instead inside of the ARVE plugin. The error occurs due to an uncompiled script inside the ARVE plugin.”

So, I hope that this script will be fixed and that we will be able to use ARVE plugin Embed button again with the Classic Editor in WP.

Thank you!

@arnaudbroes your two developers have absolutely no clue what they are talking about and this seems like a cheap attempt to shift blame away.

I just wasted a lot of time compiling that script the proper way, and it solves absolutely nothing. Exactly what I expected when I read your claim that it’s supposedly “in fact” not an issue with your plugin. The script does not need to be compiled and was intentionally NOT compiled by me. All a proper compile with wp-scripts does is minimize the script and possibly make some code run on older browsers, but that was not the issue here.

Explain to me how compiling supposedly fixes this. Did your devs compile the script, I doubt it and if they did, they did compile it wrongly! wp-scripts does NOT compile the dependency into the script itself, but purposefully keeps the import in place because WordPress writes the import map into the HTML. And I strongly assume your plugins messes the import map up, that is what the error message suggests.

My plugin works perfectly fine with every single theme and plugin my users (40k) and me have tested, except this one. So this is in fact your plugin that is causing this. I have tried with WP_DEBUG=false yet that would suppress the errors if your plugin that may break the HTML. With wp-now when I try to set WP_DEBUG to false activating your plugin gives a lot of database errors.

Any new development on this issue, @arnaudbroes and @nico23 ?

Hey @dmarin, I responded here with a beta build that you can try out if you like.

Thank you for your reply, @arnaudbroes ! @nico23, have you possibly tested the beta AIOSEO build, yet?

@dmarin Yes, I have tested the beta now and it works. Please let me know when this landed on wp.org.

Thanks, @nico23 ! Looking forward to the final AIOSEO version with fix, @arnaudbroes !

We’re aiming for our 4.7.7 release with this one (December 12) since the next one is already undergoing QA at the moment.