simonsays Posted May 31, 2018 Share Posted May 31, 2018 I have installed the latest version of processwire, but for some reason, the Page Frontend Editor is now throwing an error. <edit page="<?=$page->id?>" fields="title,body">test modal</edit> So every time I initialize modal window 1) Jquery error appears in console (see attached screenshot) 2) data-autoclose does not close the modal 3) The ajax preloader does not disappea when the modal is opened 4) When edited in modal, the fields are not updated without reloading the page (should they?) I am pretty sure this comes from processwire itself rather than the module. Has anyone come across this? Has anyone reported it? Where should I report it, if not? Link to comment Share on other sites More sharing options...
theo Posted May 31, 2018 Share Posted May 31, 2018 Looks like a JQuery issue. A conflict with other parts of JS? What is "latest version"? 3.0.98 or 3.0.104 or2.8.62 ? Issue reports go here https://github.com/processwire/processwire-issues/issues But you should probably wait for some more opinions, it might be as well a problem at your side. Link to comment Share on other sites More sharing options...
simonsays Posted May 31, 2018 Author Share Posted May 31, 2018 9 minutes ago, theo said: Looks like a JQuery issue. A conflict with other parts of JS? What is "latest version"? 3.0.98 or 3.0.104 or2.8.62 ? Issue reports go here https://github.com/processwire/processwire-issues/issues But you should probably wait for some more opinions, it might be as well a problem at your side. It's a clean install, so don't think that this is something local. The browser is Firefox. Asked my colleague to do clean install and test in Safari, also got an error (also Type error, but with a different stack). Also autoclose and ajax preloader problems on his computer. Jquery Core module is 1.8.3 and jquery itself is 1.11.1. Did not change anything after performing install. Link to comment Share on other sites More sharing options...
matjazp Posted May 31, 2018 Share Posted May 31, 2018 In dev tools, network, check if all assets (javasript) are loaded and what are the responses. Link to comment Share on other sites More sharing options...
simonsays Posted May 31, 2018 Author Share Posted May 31, 2018 Reported a bug on github. Link to comment Share on other sites More sharing options...
simonsays Posted May 31, 2018 Author Share Posted May 31, 2018 3 minutes ago, matjazp said: In dev tools, network, check if all assets (javasript) are loaded and what are the responses. All good. 200 and 304 statuses only. Link to comment Share on other sites More sharing options...
matjazp Posted May 31, 2018 Share Posted May 31, 2018 Check response, not just status. Link to comment Share on other sites More sharing options...
simonsays Posted May 31, 2018 Author Share Posted May 31, 2018 1 hour ago, matjazp said: Check response, not just status. I am not sure, what I should look for. Link to comment Share on other sites More sharing options...
matjazp Posted May 31, 2018 Share Posted May 31, 2018 Screenshot from Chrome. You'll most likely find js script that fails for some reason. Link to comment Share on other sites More sharing options...
simonsays Posted June 4, 2018 Author Share Posted June 4, 2018 (edited) On 5/31/2018 at 5:25 PM, matjazp said: Screenshot from Chrome. You'll most likely find js script that fails for some reason. Found quite a few bugs in modal.js, reported them under the same issue. Thanks for your help by the way! Your quick fix worked. @matjazp Edited June 4, 2018 by simonsays 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now