Thread

Running the latest build of EE 1.7, no clue what just happened, as everything was fine in the afternoon, and then later, not fine in the evening.

Basically, once I am in the CP for an entry, the navigation doesn’t work. None of the tabs are clickable, and when I hover over them in Chrome the status bar says [removed]void(0) - in Safari the status bar shows Run Script: void(0)

I opened up the Chrome Javascript console and basically anytime I hover over a tab, or try to open/collapse a field, a new error is generated. I am including a screenshot of that.

Any ideas what might cause something like this?

Edit - Uh, the Chrome status bar says

[removed] void(0)

Dammit. It says [removed] void(0)

OMG is there no way to specify it…trying to get creative here. It says java+script:void(0) but without the plus sign…

Okay, I tried a third browser, Firefox, and got something that may be helpful. So in Firefox, I CAN use the tabs on the Publish screen, however I still can’t open/collpase the fields. Oh, and this HUGE block of code appears above the Publish form tabs!!!

Any clues what this might be?

I’m not sure what’s causing that but what is mattkruse.com which is linked to in the error there? Does that have anything to do with it? Perhaps a path is incorrect somewhere?

Best wishes,

Mark

I am assuming all that is part of some sort of code in a module I’m using or something…I was hoping someone smarter than me might look at that and say, oh, are you using such and such add-on?

I am assuming all that is part of some sort of code in a module I’m using or something…I was hoping someone smarter than me might look at that and say, oh, are you using such and such add-on?

😉

Well, what extra (not 1st party) add-ons do you have installed? Maybe (if it’s safe to do so) turn them all off (extensions included) and then see if that fixes the problem. If it does then turn them back on again one by one and see when the problem occurs again.

That way you can then at least narrow it down to what is causing the problem and then contact the author about it.

Best wishes,

Mark

I’m pretty sure that the Matt Kruse javascript is built in to the Control Panel. I *think* it does the spell check facility or similar.

Andrew

I’m pretty sure that the Matt Kruse javascript is built in to the Control Panel. I *think* it does the spell check facility or similar.

Andrew

You’re quite right there do seem to be a few items in the core files written by him. I wasn’t aware of them as I haven’t been through every core file.

Andru in that case please (for now at least) ignore what I was originally saying as it may well not be a module or extension after all.

First question then would be is this a brand new install of ExpressionEngine or an existing site? Also you said that it was working fine but then stopped working?

Something must be afoot there. Did you change anything or install anything between it working and it not working?

Best wishes,

Mark

Actually do you have javascript enabled on your browser? I know it may seem like a silly question but that void(0) is what shows up normally. I only ask because if I turn off javascript in the browser then I get the same errors and the same behaviour too.

Yeah, and I actually disabled and re-enabled javascript to see if that would kickstart things, but the problem remains.

This is the same EE install that I have been using for 6 years.

The only things I did yesterday as far as changes to EE are:

1) I disabled Gzip output for a few minutes, then turned it back on
2) I upgraded Wygwam to the latest version

I triple-checked the Wygwam update to make sure it went smoothly, and all signs point to yes. Totally confused, and now I can’t add any new entries until this is fixed, since I can’t get to any of the necessary tabs, or even into the Extended field.

Hopefully someone from Tech Support will drop in to this thread at some point but me personally the next thing I’d do is try it out on another browser and then if that doesn’t work I’d disable extensions until it all starts working again.

That way you can then add them back in again one by one to see what is causing the problem. Quickest thing to do is to disable all extensions using the big green button on the extensions page that way then you don’t lose any settings or what not. I’d backup the site anyway before this stage just in case of course but if you turn off all the extensions and everything starts working in the publish page again then you at least know you’ve narrowed it down to an extension problem and you can add them all back on again and then disable one by one until you find out which is causing the problem.

Best wishes,

Mark

I’m hoping for someone from techs support to pop in here as well, it usually doesn’t take this long!

Mark, are you positive that if I use the Disable Extensions button that I WON’T lose any of the settings in those extensions? I have a couple (like NSM Publish Plus for example) that take at least 30-45 minutes to set up properly, and I’d hate to disable it, and then re-enable it and find those all those settings were lost and then have to re-set them up for each MSM site! 😉

At Andrew’s suggestion, I grabbed teh HTML View Source of my publish page to see if this might help in narrowing this down. Attaching just in case it leads to something that someone might see!

Okay, maybe not…it won’t let me attach the text file because it is 600kb in size. Here is a link to download it as a text file:

http://dl.dropbox.com/u/8456879/CPHTML.txt

One more piece of info:

I clicked on the error in the Javascript console in Chrome (didn’t know I could do that) and it gave me this…screenshot attached.

Andrew Weaver solved it! Looks like the Cloudflare (CDN) email address obfuscation (which is supposed to hide email addresses from being plain text) was breaking something in the code of the page itself - an email address that is within a block of Javascript, causing a Javascript error and the issue I described above!

I turned that off, and everything is back to normal!

I’m hoping for someone from techs support to pop in here as well, it usually doesn’t take this long!

You’re right, but you keep on bumping this thread to the bottom of the queue 😊

Mark, are you positive that if I use the Disable Extensions button that I WON’T lose any of the settings in those extensions?

Yes, disabling extensions globally will keep the settings. Be sure to make a db backup regardless, just in case.

Also, what version and build are you using? You might want to try uploading a fresh set of files.