Just upgraded to 5.40, why I can edit a block with IE but not Firefox?
Permalink
Every time I edit a block and click on update in FIREFOX, will have this error message
{"aID":"11","arHandle":"Main","cID":"1","error":false,"bID":"249"}
But I can successfully update it with IE..
Could someone help me?
Thanks!
{"aID":"11","arHandle":"Main","cID":"1","error":false,"bID":"249"}
But I can successfully update it with IE..
Could someone help me?
Thanks!
clear your cache in firefox
I have just run into this issue today. I have cleared cache, restarted FF twice now (just to make sure). I am still getting the errors.
Thought it might be an upgraded browser, but an earlier install is working just fine.
Thought it might be an upgraded browser, but an earlier install is working just fine.
By any chance did you install any funky addons to firefox? I know for a fact that one addon actually caused a few problems on my mac (browser related).
Hope that helps...
Hope that helps...
The issue I'm having appears to be Windows specific.
I have multiple installations running locally on my Windows (Vista) machine for development.
2 are working fine, but the one I just installed is giving me the errors. All 3 are the same version, so I really don't understand what is going on with this latest one.
I did a test install, no additions, default everything, and it is still occurring. The 'error' doesn't tell me what the error is.
I installed on a production system last night, and did not encounter any problems.
I will be trying to troubleshoot this issue today, and will post my findings when I have some.
I have multiple installations running locally on my Windows (Vista) machine for development.
2 are working fine, but the one I just installed is giving me the errors. All 3 are the same version, so I really don't understand what is going on with this latest one.
I did a test install, no additions, default everything, and it is still occurring. The 'error' doesn't tell me what the error is.
I installed on a production system last night, and did not encounter any problems.
I will be trying to troubleshoot this issue today, and will post my findings when I have some.
I hate it when I do stupid things...
Problem was a GreaseMonkey script that I didn't realize was failing in the background. (That shouldn't have been running in the first place.)
Problem was a GreaseMonkey script that I didn't realize was failing in the background. (That shouldn't have been running in the first place.)
Probably a javascript error, not a cache issue. Seehttp://www.concrete5.org/index.php?cID=102783#104756...
It sounds like a caching issue.
This thread is old so I'm sure the OP has moved on. But just for the sake of posterity -- I have run into a few of these errors recently, and while it's possible that it's a cache issue, every instance I've run into has turned out to be a javascript error (unfortunately an error that isn't outputted to the Firebug console for some reason).
In one instance it was that a block was including the jquery.form.js file, which was also included by Concrete5 so there was a conflict there. In another instance, I had an error in my auto.js validation code -- referencing a variable that hadn't been declared. In the latter case, it's entirely possible that it would work in one browser but not another, because each browser's javascript interpreter is *slightly* different, and it makes sense that some browsers would outright fail on an undeclared variable while other browsers would just move along and continue executing code.
BTW, the way I tracked down this variable reference error was by stepping through the submit code in Firebug and seeing what line it failed on. Then I stepped through again, and just before it called the function it was failing on, I copied that function call and pasted it into the Firebug console -- calling it there then showed me what the error was (not sure why it didn't show me otherwise, but there you go).
-Jordan
In one instance it was that a block was including the jquery.form.js file, which was also included by Concrete5 so there was a conflict there. In another instance, I had an error in my auto.js validation code -- referencing a variable that hadn't been declared. In the latter case, it's entirely possible that it would work in one browser but not another, because each browser's javascript interpreter is *slightly* different, and it makes sense that some browsers would outright fail on an undeclared variable while other browsers would just move along and continue executing code.
BTW, the way I tracked down this variable reference error was by stepping through the submit code in Firebug and seeing what line it failed on. Then I stepped through again, and just before it called the function it was failing on, I copied that function call and pasted it into the Firebug console -- calling it there then showed me what the error was (not sure why it didn't show me otherwise, but there you go).
-Jordan
