Issue with persist.js "ActiveX Not Defined"

@karks88 – Thanks for the report, does the error persist if those other plugins are not active? Have you made mention of this to those plugin authors as well?

– Cais.

Thanks! I did mention it to the folks at Soliloquy.

In fact, the error appears to happen with or without those other plugins. Doesn’t appear to interfere with everything, but those two were the ones I noticed so far.

@karks88 – Thanks for letting the other authors know about this (we’re always happy to work together to sort these things out).

You mentioned “debugging”, would you also happen to have WP_DEBUG set to true? … and where exactly are you seeing the error message as well?

– Cais.

I do apologize, wish I had debugging info. I was actually using Firebug and that’s how I caught the error and then backed up to an older version of NextGen.

And, it turns out after further testing that the Soliloquy problem arose from a conflict with a Lazy Load plugin. However, the JS error was still there with NextGen Gallery even after that conflict was solved.

@karks88 – It’s good to read you are making progress on this … can you offer any more details related to this JS error?

Also, we have seen some issues in the past with “lazy load” plugins, did you notice anything when testing if there may be something between that plugin and NextGEN Gallery too?

– Cais.

I’ve noticed it happening both with and without the Lazy Load plugin. And, I found another site it’s currently happening on:

https://www.karks.com/

The error appears to be on line 115 of persist.js:

ActiveXObject is not defined

Line 115

@karks88 – I just looked at that site with Firefox (with and without Firebug) and I am not seeing any errors in the console … is there a specific page/post perhaps?

– Cais.

I’m getting it on the home page, but now I’m wondering if something is goofy with my browser setup?

https://www.karks.com/karks-error.jpg

@karks88 – I’m not seeing that, and it is possible although extremely rare that a browser add-on/extension will cause a problem.

Also, that particular bit of code is for some functionality that has not been (fully) implemented yet so it does have me asking why it is being triggered for you as well.

– Cais.

This gets stranger by the second, lol. I just turned off everything except Firebug but I still get the error. Leave it to me to be in that 0.01% that would have an issue!

@karks88 – Have you cleared your browser caches and/or tried with a “New Private Window” instance of Firefox?

– Cais.

Thanks for all of your help with this, I do appreciate your time! Just tried clearing cache & the new private window, error is still there.

@karks88 – I wish I had more ideas that might help … if you find anything else by all means let us know. It may be best via a Bug Report (https://www.nextgen-gallery.com/report-bug/ … please reference this topic) with the specifics so we don’t lose this conversation and what we have already tried.

Thanks!

– Cais.