Essential Grid - Lightbox not loading (jquery problem i guess)

Hey, I’m trying to implement Essential grid and show the post content via Lightbox - right now I’m not able to move along because lightbox is not loading.

I managed to track down what’s causing the error:

I’m loading several scripts via the “Insert Header and Footers Wordpress Plugin”.
And for some of the Stuff I did on the website to work I have to load jquery this way and THAT’S what keeps lightbox from opening. The problem is that it doesn’t show me any error in the console…

Do you have any ideas how I can solve this problem?

Thx in advance,
Phil

Hey Phil,

There’s an error in the console. Regretfully, we can’t investigate this issue as this involves custom scripts which we do not have support for. Please consult with a third party developer for this.

Thank you for understanding.

I got rid of the error - it didn’t have anything to do with lightbox not showing. As I stated it has to do with jquery being loaded - since this is a pretty commonly used script maybe you can take some minutes time to look into this?

Sorry … but since you guys started Apex I really have the feeling you are trying to use every excuse possible to fire up the “out of the range of support” thing to not have to deal with us customers.

I’ve bought so many licences from you that at least I could expect to be treated like a customer you care about and not some dude you wanna get rid of really quick …

I’m sorry if you think I’m making an excuse but I’m not. Loading jQuery in a different way requires that you investigate the loading of the scripts running in your site so they will all play nicely or work. That might not just take a few minutes.

In our old forum, we did not realize the effects of giving too much customization and sometimes fixing third party plugins and scripts even if from the start, they weren’t really part of our support service. This is why some are angry because they were given the wrong expectation. Please see our Terms.

We thank you that you bought a lot of license. If the issue is really coming from the Essential Grid alone or if it is conflicting with our products including the bundled plugins, I would investigate the issue and post it to our issue tracker if found to be a bug. But as you described, the cause of the issue is the custom loading of jQuery.

jQuery is not a common script. It is really included in WordPress and it is loaded in the header out of the box. If you’ve added jQuery again whether in the header or footer, it will cause some JavaScript functions to break.

You can disable jQuery in WordPress and load your own and re-order it but again, this already is considered a custom setup.

Regarding treating customers, we treat all customers fairly regardless of license. My reply though was just short and straightforward but the context is the same. The issue came from a non-standard or custom setup.

I hope you understand our position on this matter.

Thank you.

It’s just about the way we’re getting treated here - the way the support reacts to many questions gives us the feeling that you don’t care and don’t want to be bothered. “There’s an error in the console - we can’t help you”.

No support in sense of just taking 5 minutes and thinking what the problem could be - It’s not about coding some custom solution but just about a bit of expertise from your side. I think one can expect that. With your second post I at least had a hint on where to look and I found a solution…

Just for everybody who’s experiencing similar problems:
I loaded the latest version of jQuery manually because of some effects I wanted to use. I didn’t think of wordpress loading another (older) Version also.

  • So either you unload the jQuery loaded by Wordpress via the functions.php or
  • install “jQeury updater”. It disables the Wordpress version of jQeury and loads the latest version.

Now my effects are loading and lightbox is also working.

I’m personally sorry about that but we do care for customers. I left a simple and straightforward message because of the rising open threads and the issue was caused by a customization.

I hope you’ll understand.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.