physalis

Hey @jkrill , good to hear back from you :). I just tried the latest version of your plugin, and finally failed to get any page to load there. Console tells me it tries to load something from localhost:3000 and fails due to a connection being refused:

GET https://localhost:3000/wp-admin/admin-ajax.php?action=wpjm_menu&post_id=0 net::ERR_CONNECTION_REFUSED (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery…:4)

I have this both on a local as well as an online site. Would you be able to take a look :)?

Thanks as usual ;)!

Hi Takis,

I strongly believe it must have to do with caching, as it is not enabled on the testing site.

It sounded as if there were issues (just read it in another thread), but happy to hear it is more connected to CDN than the plugin itself :).

All the best so far & thank you so much

Eno

Hi Takis,

unfortunately, as this is a live site, I am not able to go back to the faulty version, as the problem resided on the home page of the site. I tried to reproduce it on its testing site, but wasn’t able to. One difference is that the live site uses WP Rocket which, from what I read here, interferes with your plugin, but hadn’t read that it does in the way I experienced it.

All the best

Eno

Hi @jkrill , thanks for solving the problem. However, it seems the fix with caching isn’t working anymore. Our site had worked fine with the modified version by @seeekr , but at least with the latest version it is slowing down ~ 3 seconds in the frontend, even when users don’t display the admin bar. Are you sure the AJAX thing is implemented completely :)?

Thanks again ??

Any updates on this matter?

A similar problem with a site I am using your plugin on. The form setting can be opened, but it appears as empty. Console throws out the following errors with WordPress 4.5:

form-manager.min.js?ver=7.8.1:1 Uncaught TypeError: Cannot read property ‘extend’ of undefined
form-cpt-preview.min.js?ver=7.8.1:1 Uncaught TypeError: Cannot read property ‘findWhere’ of undefined

Could it be related to WordPress 4.5 using an updated version of jQuery?

Just a little update: I see the error throughout a lot of my sites, so it is nothing like a theme conflict. I guess others didn’t update yet, or didn’t realise the problems. It breaks a lot in the frontend since it’s initialised that early on the page.

Hi @jkrill, seems you incorporated the changes, thank you so much, hehe :). However, since 3.5 or 3.5.1 we get a JS error message in the console, breaking some things in our frontend.

wpjm-main.js?ver=3.5.1:42 Uncaught TypeError: Cannot read property ‘baseUrl’ of undefined

Can you take a look? Or is this up to us in any way?

All the best

physalis

I can confirm this. In my case the URLs normally would have a /en/ between domain and page URL, but instead I get double entries as well.

Hi Tom,

I already switched back to the latest working version and will stick with it so far. Was just on a site about to go live in minutes, so thank God I had the idea of reverting to a previous version.

Thanks again

physalis

It does, hooray :)! Thanks for fixing it :).

No, it doesn’t seem so. That is good, thank you :).
It’s actually 1.1.4 here.

I never had problems with Internet Explorer (11!) denying SVG images, so I suppose it is rather some CSS problem. Can see other SVG images on the very same sites I use your plugin on very well :).

Alright, now I understand. You asking for my browser version may just have shown me a different JS problem that derives from a gesture extension for Chrome.
Even so, the exact error given above does appear when I click a link in the navigation, but isn’t limited to it. I opened another sub page, clicked somewhere on an image, and got the same getRangeAt error, and it happens when you use your mouse to move the scrollbars on the right. Try https://www.testboks.com/vebu/fitness-gesundheit/ and click on the only image that is not a background image here, the VegMed logo. And scroll around ;).

Try https://www.testboks.com/vebu/ – it’s all over the place. Since these JS errors are JS errors, it’s hardly believable this has anything to do with my browser :). I use Google Chrome (latest) on Windows 10 x64.