hakre

Please take a look here:
https://www.ads-software.com/support/topic/117993/page/2?replies=47#post-623051

The background is more discussed in this Thread, my Post gives you a better fix to the problem:
https://www.ads-software.com/support/topic/117993/page/2?replies=47#post-623051

Okay folks before trying yourself or even deactivating Mod_Security completely after all, please contact your admin or the person who is in charge for the Mod_Security setup. This is an fault in the default setup most often.

If you get 403 errors in the backend related to Ajax Requests while the requested files exist and are requestable with your browser, this looks like Mod_Security is handling the Ajax Request as a false-positive. This is often the case beacause a specific set of Mod_Security rules does not allow the request like it is done by the Ajax-Library of WordPress. You can fix this quite fast if you (or your admin) has access to the Mod_Security Setup.

There is a Pattern that must be extended. In a Post above it is shorted. Even this works as well, I would not recommend it, because it leaves a lot of other requests open – and this does not work well with whitelisting.

This was the Message I got:
mod_security-message: Access denied with code 403. Pattern match “!(^$|^application/x-www-form-urlencoded$|^multipart/form-data)” at HEADER

It contains a Regular Expression:
!(^$|^application/x-www-form-urlencoded$|^multipart/form-data)

Because the Ajax Library WordPress uses send it request with the header “application/x-www-form-urlencoded; charset=UTF-8” it is not matched against that regex.

FIX: Tell your admin to add that string to the regex:

|^application/x-www-form-urlencoded; charset=UTF-8$

Now the Header matches against that rule and everything is fine.

close all tabs and clear the cache. the visual editor works like a charm with ff 2.0. these problems mostly turn out to be caching issues, which means that your browser does not download all the new files you just upgraded (mainly the .js files).

okay found it: [email protected]

Okay, I logged in and it did not work out. Is there a mailaddy for important (e.g. security related) bugs?

You don’t need a fresh Install, you need a fresh, clean cache. Your browser fools you and sabotages Worpress 2.1 by loading an older javascript instead of the latest one. Continue reading in that thread.

Checkout this thread, I had the same behaviour and it was a cache issue. In that thread it’s written what you need to do.

The Solution is simple: After the Update, close all browser Tabs in Firefox, navigate with the last open one to google homepage or about:blank and then clear the cache. Restart the Browser and everything works fine as expected.

The Error is not Firefox related in general nor is it OS Releated. It occurs when the Browser uses an older javascript file that is incompatible with the one shipped with WordPress 2.1