Thread

What I don’t understand is that these errors are not consistant. I’ll send you login details, if you wouldn’t mind taking a look. Feel free to do as you wish.

PM sent.

Hi Dominic,

Please don’t send site login details unless we specifically request them. Did you try disabling your accessories?

Cheers

Greg

YES. It is still not working.

Local copy - Unusable in all FF (15 sec page loads. Menus don’t work in Chrome.
Staging copy - Works find in FF. Menus don’t work in Chrome.

More clues - Firefox Error Console displays this message when loading the admin in the FF (local). It’s only done this one time…

Error: useless setTimeout call (missing quotes around argument?)
Source File: <a href="http://domain.com/system/index.php?S=c07c5256d0969625dade5f57b9a7cde4b8027850&D=cp&C=javascript&M=combo_load&ui=core,widget,mouse,position,sortable,dialog&plugin=ee_focus,ee_notice,ee_txtarea,tablesorter,ee_navigation&file=cp/global&effect=core&v=1305717369">http://domain.com/system/index.php?S=c07c5256d0969625dade5f57b9a7cde4b8027850&D=cp&C=javascript&M=combo_load&ui=core,widget,mouse,position,sortable,dialog&plugin=ee_focus,ee_notice,ee_txtarea,tablesorter,ee_navigation&file=cp/global&effect=core&v=1305717369</a>
Line: 1123

Hi Dominic,

I’m sorry to see you’re still having issues with this. Sue’s suggestion was an attempt at troubleshooting, not an attempt at upgrading the site. Troubleshooting software like EE is all about slicing up the problem into testable areas to narrow down the problem scope until we find the problem itself.

Let me suggest trying her suggestion, and do so progressively until you come across the problem. It’s mostly likely something that you’ve added to EE (an accessory, extension, etc…), so we need to narrow it down and see what that is. Installing a fresh copy of 2.1.3 and making sure that runs smoothly is the first step. Then go about building up *that* install (which is a throwaway install once we’re done troubleshooting) with the exact same stuff that’s in your problematic install until you come across the troublesome add-on. It could be that something with an add-on is conflicting with something on your local dev server that’s not on your staging server.

If a fresh install of 2.1.3 causes you issues as well, then we’ve ruled out add-ons entirely and we can look to find the problem in 2.1.3.

Kevin

I hear what you’re saying, but after a month’s worth of development, going back to the beginning and reintegrating everything in source control is an absolute and utter nightmare, especially when I’m hoping for sign-off today.

Besides, I do not believe I will ever hit the problem doing it this way since the copy installed on my staging server is almost totally fine. This indicates to me a freak combination of events rather than anything repeatable. I *could* go back and start all over again, copy and pasting for half a day, but I was expecting a EllisLabs developer to be able to pinpoint a possible error based on the line of code that errors (presumably the one which combines and minifies JS). I appreciate the help here, but suggestions of removing plugins, extensions and reinstalling the system are pretty high level stuff in my opinion.

I understand the frustration in rebuilding everything, but like I said, that’s how we have to go about troubleshooting. Several of us have already tried everything off the top of our heads to solve it, so just like I would do personally, the next step is to slice the problem up into testable pieces, testing each piece, and repeating the steps until we come across the problem again.

If the problem isn’t repeating itself on a staging server, perhaps you could try to re-deploy it locally and see if the problems persist.

If classic troubleshooting techniques aren’t possible in this situation, I’m afraid we might have hit a wall.

Kevin

I am running into the exact same problem.
I tried all the steps mentioned in this thread but nothing helps.

Problem only occurs on our VPS production server.
Everything runs fine locally.

CP loads fast, but takes another 10 sec. before javascript functions.
Version 2.1.3 Build 20101220

Firebug and Chrome show same results as mentioned in earlier messages.

Hi humanique,

Can you confirm that you local servers are setup in the exactly same way as your production one? Are you using external caching functions or .htaccess caching on the VPS?

Cheers

Greg

No. Local server and production server are not exactly the same.

However, both servers are configured simularly and are running the same PHP version.
They don’t use any external caching or .htaccess caching.

The problem seems to be caused by this call:

/system/index.php?S=f33822f8326b25428b3e3916ef29dca6e6eb070e&D=cp&C=javascript&M=combo_load&ui=core,widget,mouse,position,sortable,dialog&plugin=ee_focus,ee_notice,ee_txtarea,tablesorter,ee_navigation&file=cp/global&effect=core&v=1307721642

If we tweak the parameters a little bit, everything works fine again:

/system/index.php?S=f33822f8326b25428b3e3916ef29dca6e6eb070e&D=cp&C=javascript&M=combo_load&ui=core&plugin=ee_focus,ee_notice,ee_txtarea,ee_navigation&file=cp/global&effect=core&v=1307721642

Jeroen

Hi Jeroen,

What is your $config[‘uri_protocol’] setting in system/expressionengine/config/config.php? We are fast approaching the 2.2 release so if you can wait a little bit it might be helpful to upgrade at that point and then test this again.

Cheers

Greg

It’s ‘PATH_INFO’.

humanique,

Can you try changing the uri_protocol to AUTO and see if that works for you.
Note EE2.2 is scheduled for release tomorrow

No, doesn’t make any difference.