SeeJaneB

Thank you. I just created a ticket. Interestingly enough, the error actually includes this line after the 1st line I previously shared, which is why I came here (following directions).

“You can get support any time here:?https://www.ads-software.com/support/plugin/security-malware-firewall.”

Thanks for the response. I reported a page where this was happening in my report above, along with screenshots.

[ redundant link removed ]

• This reply was modified 1 year, 9 months ago by Jan Dembowski.

I discovered this problem when running one of my sites https://mytrinitychurch.com on page speed insights, so I believe there is still more work to do with this issue. See images here from page speed insights and the developer console:

https://www.awesomescreenshot.com/image/35943936?key=c4e970be889dfbf575d017298a211422

https://www.awesomescreenshot.com/image/35943952?key=f5f6c55d1268e487b619ec1275fe23b0

• This reply was modified 1 year, 10 months ago by SeeJaneB.
• This reply was modified 1 year, 10 months ago by SeeJaneB.
• This reply was modified 1 year, 10 months ago by SeeJaneB. Reason: added the site where I'm seeing the issue

@ijscobrand I am just getting this plugin setup and also just discovered I have the same issue as you. Repeating events are displayed fine, but there’s an error on any event pages that are not recurring.

There is a lot I like about this plugin, but pretty bummed to see very little support for the free version.

I see the last update should provide compatibility with Oxygen moving forward. Thanks for the update!

I am curious if there are any special settings needed for Oxygen users. In the past we had to specifically list ct_builder_shortcodes or add php code in the plugin file.

Do we still need to add anything like this, or is it supposed to work right out of the box for Oxygen content?

I think I finally got it fixed. It might have had to do with an optimization plugin’s settings.

I also just did a test using the classic editor without the page builder, and it’s still not working, so the builder isn’t the issue.

I did everything just as your instructional video shows for using the classic editor and still no lightbox.

Thank you so much. That seems to me my exact issue. I’m glad you all are aware of it and there is hope for a possible fix in the future.

I copied this post and have pasted over on github.

Great, glad I brought it to your attention! Thanks for the quick response!

Perfect! That worked! Thank you so much for the quick reply.

I contacted Oxygen Builder support as well, and here is what they said:
“The error is most likely occurring because a file isn’t being loaded by the builder, which means that the function mecGridView can’t be found. The error won’t prevent the builder itself from working correctly, so you can ignore it.
I’m very sorry, but unfortunately, it’s not an error that we can fix.”

I do have an event calendar widget in my mega menu, so the calendar assets do have to be set to load on every page. Here’s a screenshot of the settings for that widget shortcode: https://www.awesomescreenshot.com/image/11862463?key=0fc95866dd44a4e2954b375f882762ed

I think that is the one that is throwing the error. It’s perfectly fine on the front end, but giving an error since it’s not loaded in the builder when editing pages or templates. https://www.awesomescreenshot.com/image/11862792?key=c166262e286387ae4910d3ae9df4098b

Hi @webnus thanks for checking back in.
I just ran all of the plugin updates on my site, including the Oxygen one.

I went to edit a template in Oxygen and am still seeing this:

Uncaught TypeError: jQuery(…).mecGridView is not a function on line #2 in https://mytrinitychurch.com/?ct_template=369&ct_builder=true&ct_inner=true&oxygen_iframe=true

This seems to be working, as well. Thank you so much!

Do you want me to put the lib/indexing.php file back the way it was and then try this other method?

And where am I adding this? as a code snippet (given that I’m using Oxygen Builder)?

Sorry for the delay. Yes. That solves it. So should I go ahead and delete the other code snippets that didn’t work?

And also moving forward, when the plugin updates, will I need to go in and remove this code each time?