Incompatibility with ARVE (WP Interactivity API inside admin) #2

  • https://www.ads-software.com/support/topic/incompatibility-with-arve-wp-interactivity-api-inside-admin/

    This was wrongly closed as “resolved” when still an issue your suggestion is not the cause at all. I did nothing wrong on my end, just using native WP APIs the correct way. Your plugin is the ONLY plugin that breaks this. This is in fact your plugin that causes this issue.

    Messages directing my users to this forum and your support site will remain in place until this is fixed by you, or you give me directions how I would solve this on my end.

    And do not prematurely close this again.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author arnaudbroes

    (@arnaudbroes)

    Hey @nico23,

    I’m not sure why the previous thread is already marked as resolved – in any case, my apologies.

    I personally took a closer look at the issue along with some of our other developers and we were able to identify the root cause of the issue and fix it.

    Because both of our plugins preload JavaScript modules in different places (we are doing this in the HEAD, your plugin in the footer through WordPress), the browser would throw an error because your preloaded module (WP Interactivity script as a dependency) is registered long after ours have already started loading, along with other non-preloaded modules.

    We have been preloading our modules for years in a custom way so we were unaware that WordPress recently added support for this through the wp_register_script_module method. As I already mentioned they load preloaded modules in the footer, so we’ve gone ahead and updated our plugin to load them there as well. That seems to resolve the issue.

    I’ve uploaded a beta build here. Do you mind trying it out to confirm the fix?

    Let me know if you have any questions!

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.