billjoseph Posted April 25, 2017 Share Posted April 25, 2017 Weirdest thing just happened to me. I updated blank site from 3.0.42 to 3.0.61 then started adding fields. I have two instances of FieldsetOpen areas in the template, and a few CKEditor textareas (both inside those fieldsets and outside). I added an image field to the template and placed it near the top of the template fields. Once I did that I was unable to toggle either Fieldset, and the CKEditor stopped working. When I moved the image field to the bottom of the template fields, the CKEditor loaded, but the fieldsets still wouldn't toggle. When I deleted the image field, the editor and toggle return to normal. (Adding a new image field re-introduces the issues.) I've tried adjusting the settings on the image field but the result is the same - even with all default settings. I tried adding an image field to a different template - same result. What am I missing here? Link to comment Share on other sites More sharing options...
tpr Posted April 25, 2017 Share Posted April 25, 2017 Sounds like a JavaScript error, check the console (devtools). Link to comment Share on other sites More sharing options...
billjoseph Posted April 25, 2017 Author Share Posted April 25, 2017 Console is showing a javascript error: TypeError: u.cookie is not a function in /wire/modules/Inputfield/InputfieldImage/InputfieldImage.min.js:1:11297 Link to comment Share on other sites More sharing options...
tpr Posted April 25, 2017 Share Posted April 25, 2017 My best guess that it's a conflicting module, try disabling them one by one. You could also post your modules list, perhaps someone can identify the issue. Link to comment Share on other sites More sharing options...
billjoseph Posted April 25, 2017 Author Share Posted April 25, 2017 Disabling modules didn't make a difference. This is the list of modules: Site - modules I added Email Obfuscation (EMO) Menu Builder: Markup SEO Markup Simple Navigation 404 Logger Hanna Code Menu Builder: Process Hanna Code: Text Formatter Core - these are the modules I activated, the rest are in their default state as shipped Reno Select Options CKEditor Page Auto Complete Forgot Password Also realized that it's not just the fieldset toggles, but any field toggles that do not work. Link to comment Share on other sites More sharing options...
billjoseph Posted April 25, 2017 Author Share Posted April 25, 2017 Checked the source of the page to see if jquery.cookie.js is being called before InputfieldImage.min.js. It is, but it's returning a 406 Not Acceptable Error: An appropriate representation of the requested resource /~mysite/wire/modules/Jquery/JqueryCore/jquery.cookie.js could not be found on this server. Additionally, a 406 Not Acceptable error was encountered while trying to use an ErrorDocument to handle the request. I checked the server and the file is there and in the correct place, and has content. The actual line where the file is called is this: <script type='text/javascript' src='/~mysite/wire/modules/Jquery/JqueryCore/jquery.cookie.js?v=1493077229'></script> Link to comment Share on other sites More sharing options...
billjoseph Posted April 28, 2017 Author Share Posted April 28, 2017 Talked to my hosting company and the problem was apparently due to the temporary url structure for development: server.com/~myaccount They suggested editing my hosts file to bypass the DNS, which worked for me, but would be unwieldy for the client, so I created a subdomain that points to the IP: dev.myurl.com I had to add the new subdomain to my config.php file as one of the httpHosts, but it seems to be working just fine now. Link to comment Share on other sites More sharing options...
tpr Posted April 28, 2017 Share Posted April 28, 2017 Is that a cPanel preview URL? I noticed that but thought if other scripts are OK then that couldn't be an issue. Link to comment Share on other sites More sharing options...
billjoseph Posted April 28, 2017 Author Share Posted April 28, 2017 53 minutes ago, tpr said: Is that a cPanel preview URL? I noticed that but thought if other scripts are OK then that couldn't be an issue. It is, and it hasn't been an issue before. I don't know why just the one script was throwing the error, or why it started doing it now. I'm just glad to have a solid workaround for the future. And, tpr, thanks for your help in getting me pointed in the right direction so I could figure out where the problem was! 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