Forums

Alberto,

I just posted using Firefox 12. I have found no issue with this.

Can you give any other details/settings possibly?

Can you post using other browsers?

I've had the same problem after the upgrade to the forum software. Before the upgrade, I was able to post with Firefox 3.0.19. After the upgrade, posting would result in the infinite spin or my reply would just disappear. I upgraded to Firefox 11. Same problem. Tried the just released Firefox 12. On occasion, a popup/over would display at the top of the page saying something to the effect, "error occurred, please contact your administrator".

I had to resort to Internet Explorer 9 to reply.

 

How did you post this question if you are unable to post questions?

Foe

Hi all,

naturally I'm using now IE to post here...

Adding details, I'm using Win XP OS and Firefox rev. 12.0.

Any possible advice?

Thanks and regards,

Alberto

@Norman & @Alberto,

If you could try clearing out your browser cache and let me know if that resolves any of the issues you are experiencing (details on doing here).

If you still experience any issues after that let me know. We have some additional fixes above and beyond that going into place next week which will hopefully fix this for those where clearing browser cache doesn't work.

Sorry for any inconvenience you are currently experiencing.

Blake 

I had the same problem this week.

After unchecking "remember me", cleaning my caché... everything, I realized the problem was having a "signature" with HTML code. Try chosing post with only "plain text", uncheck "display signatures" and change your signature to something like "--". Not empty.

Obviously, I have not narrowed down all the problem but one among these things helped me. It is NOT browser dependent, as far as I know.

I'm posting from this message from Firefox 11.0. So far, my success rate has been maybe 2 out of 4 with Firefox.  With Internet Explorer, 2 out of 2 are good. Might be that I have enountered a failure on IE yet. kazoola's statement of it being browser independent may be true. Clearing the browser cache is not a sure fix. Hit and miss as well.

@kazola and @Norman,

Sorry again to hear about any continued issues you are experiencing. As soon as we have additional fixes in place I will let you know and check back in to make sure we get all issues you are experiencing resolved.

Blake

Norman Wong

After the upgrade, posting would result in the infinite spin

I had also been getting that failure on every post attempt I have made in the last 4 days. Doesn't seem limited to one browser, since has happened with IE 8, Chrome, Opera 10 and Opera 11. Clearing the full browser history and cache didn't fix the problem.

Viewing the JavaScript Console in Chrome shows the _TrackSC call in ui.js failing with an unhandled JavaScript error.

Manually editing the ui.js to comment out the call to _TrackSC then allows the post button to work.

Hi all,

today, after cancelling completely cache, the issue is solved.

I'm now posting again from Firefox.

Did you changed configuration?

Thanks and regards,

Alberto

The solution given above works. I'm able to post THIS post. But the solution has to be repeated every post. What the h... is this. Please fix ASAP.

@Alberto Soattin - Thanks for letting us know

@kazola - We have some additional fixes going into place soon this week that we are hoping resolves all posting issues. I will update this thread once those fixes are in place.

Blake

I am also experiencing the "infinite spin" script bug - and it has prevented me from posting since the last update.

Both IE8 and FF6.0.2 are affected.

I can get around it (and, thus, post this) by using the IE "Developer Tools" in script debug mode so that it breaks at the error - then I just step over the offending line!

The error is that a method or property is being used which doesn't exist!

Now, a compiled language would give a compile-time error for that - surely, there must be tools to detect this for a scripting language...?!

 

Andy,

Thanks for the feedback and report. We should have this resolved here soon so you don't have to take those extra steps.

Blake