Post area inaccessible when using Analytify with Nelio Content plugin (conflict)

Hey!

I will get into it and see what’s possible and why It is not working currently.

Looking forward!

Hi @juryduty, @hiddenpearls.

Thanks for reporting this compatibility issue. I just installed analytify and, indeed, there’s a compatibility issue.

@hiddenpearls, the problem is with the momentjs library. This is an issue I’ve experimented a few times with other plugins and other libraries – and it really sucks.

I modified the library our plugin includes so that it’s now named ncmoment instead of moment. This will ensure that our plugin does no longer collide with yours… I’ll release a new version of our plugin next Monday. Let’s see how things work then, @juryduty.

:sigh: WordPress can be so complicated!

Regards,
David

@davilera

Thanks for quick reply. I noticed that too momentjs is the issue but changing the slug wouldn’t help. Keep the slug like sanitize_title e.g if it is moment.js It could be moment-js

We found that Conflict will be resolved if we change the momentjs version to 2.18 the latest release in our Analytify plugin.

So, we will release an update as well at next Monday to resolve this issue.

Thanks
Adnan

@hiddenpearls

Thanks for quick reply. I noticed that too momentjs is the issue but changing the slug wouldn’t help. Keep the slug like sanitize_title e.g if it is moment.js It could be moment-js

Yes and no. The slug one uses to register and enqueue a script can be an issue… but it’s not the one I was talking about.

If we use the same slug, two different plugins (yours and ours) would “define” the same script (momentjs), but only one JS file would be printed in the HTML, because the last plugin that (re-)defines the script would overwrite whatever plugin was added by the other.

If we don’t use the same slug, then we wouldn’t overwrite each other’s scripts… in PHP. But we would definitely overwrite them in the browser. Using different slugs means that you’d be able to enqueue your script and I’d be able to enqueue mine. Both scripts define the global variable moment, so whoever comes last, would be “overwriting” the other (or, if the script defines the global variable only if it doesn’t already exist, whoever comes first would have all the power).

We found that Conflict will be resolved if we change the momentjs version to 2.18 the latest release in our Analytify plugin.

The problem with momentjs is that there are multiple versions of the same script. With or without locales, with or without timezones. That’s when issues arise – if you use one version and I use the other.

As I said before, the only solution I could think of was to edit the script itself (the min.js file) and change all moment keywords to ncmoment, creating a new global variable that wouldn’t collide with any of yours (or other plugins).

I hope this makes sense… ??

Regards,
David

@davilera

Yeap makes sense.

@hiddenpearls @davilera,

First of all–WOW–I’ve been using WordPress for nearly a decade and usually when reporting an issue on a plugin, you never hear anything back…and you both not only responded within hours, but also found the issue and are updating the plugins! I’m SO impressed! Thank you so much. These are both top quality plugins and I can’t imagine not using both.

For the end user, here’s a workaround I found until the updates come out:

Both plugins allow you to choose what areas on the backend the analytics appear (in addition to the plugin’s comprehensive analytics page). The default for both is “posts” and “pages.”

By simply removing “posts” and “pages” from one of the plugins, everything works again. This of course isn’t ideal as one plugin reports social analytics, and the other page analytics for individual posts/pages, but it does resolve the conflict so that the plugins can stay active until the update comes out.

Much thanks again for the stellar support from both.

@davilera
@juryduty

Hi guys,

We have released this fix from our side. It should be Ok now.

@juryduty
Thank you for your feedback.

So did we, @hiddenpearls. Thanks for all your support.

And @juryduty, thanks for your heads up and working with us. Don’t forget to rate our plugins ??

Cheers @davilera keep up the great work with Nelio Content ??

@juryduty looking forward for a review ??

Thank you both! Everything works this morning. Leaving stellar reviews now!