Hallo Beda,
Look at my conversation with someone o Slack.
guy_b [12:48 PM]
What version of cred are you using? Did you try rolling back to the previous version?
[12:49]
Also, does the form use Ajax? Is there an option to turn off Ajax?
josvermeulen [12:59 PM]
It doesn’t use Ajax. I’ll try rolling back to the previous version, although also that cannot really make sense as many can’t use and quite a few can. But I’ll give it a try. Thanks for your help.
guy_b [1:40 PM]
did you change it already? it is now working for me.
josvermeulen [1:40 PM]
No, I did not change it. Did it not work for yoou before?
guy_b [1:41 PM]
no, and now it is not working again.. but I think I can see where the problem is coming from.. hang, let me try what I did perviously
josvermeulen [1:44 PM]
I have to run but am very curious if you can find out something. Will be back in an hour or so.
guy_b [1:45 PM]
and now it works again.. So what I have done to make it display, is open Chrome dev tools then open the Event Listeners tab, expanded the "click" listener, scrolled down to document > date.js, clicked to open the date.js script in the sources panel, refreshed the page, and the calendar works
[1:46]
so it looks to be some kind of cache error, and the script is not loading initially. It does load with Ajax, so if the script is triggered manually, it allows the functions to fire.
[1:50]
yeah, disabling the browser cache allows it to work. Try disabling the Powerpack addon temporarily to see if that solves it. The cred script is right at the very bottom of the source, and there are a absolutely tons of other scripts above it so it could well be that one of those is blocking it
guy_b [1:59 PM]
also, are you using the Beaver Themer alpha? Are you using the latest alpha? if you are not then try updating that.
If it is the latest, then I can see an error in one of the script uri:
/wp-content/plugins/bb-theme-builder//js/jquery.throttle.min.js?ver=1.0-alpha.6
Notice the double slash?
Also, Jos, this conversation would have been far better done as a thread in the public channel rather than via direct message, so that the conversation could be see and contributed to by others if needed.
I can't really spend much more time on this now, but I think you have a few clues now
guy_b [2:06 PM]
and actually you don't need to do all the Event Listener stuff above, just disable the browser cache while dev tools is open and refresh the page, and it should work
josvermeulen [2:59 PM]
Thanks a lot Guy. I’ll wrap this up and send it to the Toolset supporters. I use the latest Themer alpha. The Powerpack addon is probably not causing anything as the result without all the non-toolset plugins was the same. I’ll let you know what happens.
josvermeulen [3:27 PM]
It’s a pity I am not smart enough to really get what you are saying, but I’ll send it to the Toolset guys and hope thay can brew something out of it. :blush:
guy_b [3:46 PM]
Sure, you're welcome, although I have a feeling that the problem is actually on the Beaver Builder side..
josvermeulen [4:42 PM]
I don’t think so. I have tried three times with Twenty-seventeen and only 4 Toolset plugins on a fresh browser and that did not work also.
guy_b [5:07 PM]
oh really? that's interesting to know.. Did you disable Beaver Builder also though? so just plain twenty seventeen + toolset, no other plugins active at all? none? and no custom scripts of your own?
josvermeulen [9:34 PM]
Yes, exactly as you say it. And tested on a fresh browser. I told the Toolset supporter but he did not read my post carefully I think.
