Hi @dmarin,
Thanks for reaching out and letting us know about this issue.
I completely understand how frustrating this must be, and I want to reassure you that our team is already aware of the problem and actively working on a solution.
I’ve flagged this internally, and our Development team is fully focused on resolving it as quickly as possible.
I appreciate your patience and understanding, and I’ll keep you updated with any progress or changes.
Thank you again for your patience.
Hey @dmarin,
Thank you for your patience.
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.
We’ll reach out to the author of ARVE here and relay our findings. I would suggest that you follow up on this issue with him there as he’ll need to work on a fix for this.
If you have any questions, please let us know!
Thread Starter
dmarin
(@dmarin)
Thank you for checking it out and replying. I will definitely follow up with ARVE regarding this issue.
Regards, Danijel
Hi @dmarin,
I wanted to let you know that we released All in One SEO version 4.7.7 today, which improves compatibility with the ARVE plugin to fix the issue you reported.
Please update to this latest version of All in One SEO to get this and other improvements.
Thread Starter
dmarin
(@dmarin)
Hi there @alhanrahman, @arnaudbroes and @wpsmort !
I have updated both ARVE and AIOSEO to latest versions (10.5.3 and 4.7.7.2 respecitvely), but I still get the same warning message about incompatibility from ARVE and still not able to use the ARVE button within posts in Classic Editor to enter ARVE code if AIOSEO is enabled. However, if I rollback the ARVE plugin back to 10.1.1 it works just fine with AIOSEO enabled.
So, it says RESOLVED on top of this post, but clearly this issue is NOT resolved, yet!
Any updates on the issue and when it will be resolved for good (on both ends)?
Please let me know. Thanks!
Danijel
-
This reply was modified 1 year, 3 months ago by
dmarin.
Hey @dmarin,
I just had a look at this with the latest versions of both plugins + the Classic Editor and I’m not seeing any issues. It’s working perfectly fine for me.
@nico23 are you aware of any issues currently?
Thanks!
Thread Starter
dmarin
(@dmarin)
Well, I checked again on several websites … on some ARVE works fine and I am able to insert the shortcode using the ARVE button while on other sites I have to Rollback to ver 10.1.1 to get ARVE button to work in the Classic Post Editor. Not sure why, but maybe it’s also related to the Theme?
Regards, Danijel
@dmarin
I missed that the stable update was out. I can not confirm it not working. I checked with AIOSEO 4.7.7 and 4.7.7.2 and they both work with the latest ARVE version. I will remove the notice from ARVE in the next version as this seems to be fixed.
Are some of your sites hosted on WP Engine? I have a report that the button supposedly does not work on WPE but its just one report and I have no confirmed this or know if its maybe because of a incompatibly with another plugin. If this is the case please contact WPE for a fix. I do not host with them so I can not test it myself.
They might be messing with importmap or JS modules the way this plugin did. The JavaScript modules and WP Interactivity APIs are quite recent and there might be other plugins / theme code that are doing it the wrong way.
And btw: Awesomemotive, the owner of this and many other plugins is a shady company who ADMIT they mark topics as “resolved” as soon as they respond here. They do it so they can FAKE the number of “resolved topics” on their plugins pages. Please leave a negative review for this shady practice. You can also change it to “not resolved” as a thread starter and watch them just rudely mark it as resolved again! This one seems to be actually resolved now from what I can tell.
Hey @nico23,
I believe your personal thread was previously prematurely closed by myself, which I apologized for.
While it indeed seems that EDD has a policy to resolve tickets as soon as they’ve replied, this is not the case at AIOSEO. You can verify this by looking at our resolved threads. We close threads when they are resolved or when the user did not reply in a timely manner. If they reply after a period of inactivity, we also typically reopen the thread.
Awesome Motive does indeed have multiple plugins under its umbrella but all of our teams operate independently from one another and we do not necessarily share the same policies. Whilst everyone is entitled to their own opinion on Awesome Motive or any of its products, please refrain from asking people to leave a negative review based on assumptions. I’d rather that we simply work together to help @dmarin resolve the issue he is experiencing.
@dmarin in addition it may be worthwhile to try deactivating all of your other plugins/theme temporarily to see if you still experience the issue with just ARVE and AIOSEO activated. I recommend doing this on a staging site if you have one available.
If you do not experience the issue with just those two activated, then you can reactivate your other plugins one-by-one to figure out which one is causing the conflict.
Thread Starter
dmarin
(@dmarin)
Thank you both for your replies, @nico23 and @arnaudbroes ,
The strange thing is that on some of my client’s sites ARVE works just fine, but on some the button still does nothing as described above. I have tried to see if it’s server-related, but I have several sites on the same server for a client (GoDaddy) and on most of these sites ARVE works just fine, but on one site it does not. So, I think the problem might be Theme-related rather than server-related (outdated themes that might have some internal problem that still prevent ARVE button to work in Classic Editor).
So, thanks again to both of you for your support and for fixing AIOSEO-related issue. As for those sites with older Themes, I will just use ARVE 10.1.1 for now and will see what happens later.
Regards, Danijel
Hi @dmarin,
Thanks very much for the update. I hope you’re able to find the issue if it’s theme related.
Do you need any further help from us with this issue? If not, can we go ahead and resolve this thread?
Hi @dmarin,
I’ve not heard back from you, so if you don’t mind, I’ll go ahead and close this forum thread. We can reopen it if you still need help from us.
Please let us know if you need anything.
