WordPress.org

1. wolfgrrl
   Member
   Posted 4 years ago #

   I have searched high and low - I have done all suggestions I have found online including the ajax plug in and changing pluggable.php. This was on both a 2.3.2 installation and a fresh 2.3.3 upgrade with all plugins disabled.

   How can I fix this? I find it ludicrous for WP to ignore this issue for so long. None of the fixes I have tried have worked.

   Please, someone shed some light on this!

   I also so not know who has deleted this the first time, but I do not appreciate it! This has been an issue since 2006. I have tried ALL the fixes that I could find on Google. Why can't we get help with this!?

2. whooami
   Member
   Posted 4 years ago #

   the devil's advocate in me speaks:

   why is an error that affects one browser, and pockets of users, an issue with for WP to fix?

   and why are you crossposting???

   http://wordpress.org/support/topic/159144?replies=2

3. wolfgrrl
   Member
   Posted 4 years ago #

   A pocket of users? I beg to differ.

   Take a look at the Trac site. This issue goes back to 2006 - that's two years old! In two years this should be fixed, no matter how many people it affects......if it was you that it was affecting, I'm quite sure that you would want it fixed. I also see that this will be fixed in version 2.5 - so why does anyone have to wait that long for the fix to be issued?

   There are many, many people that use WP that run Firefox. And more and more hosting companies are starting to the use the Suhosin patch for PHP that directly conflicts with WP and throws this error.

   So yes, it is a WP issue to fix, no matter how small the userbase.

   Double posting? I posted here as directed to in my WP dashboard as this is FEEDBACK I have left. I've posted elsewhere to actually try to get any resolution to this issue.

4. thelazygeisha
   Member
   Posted 4 years ago #

   wolfgrrl: Since this issue on some level is being addressed in future releases of WordPress, you must realize that this isn't going to get fixed today. As I responded to you in your duplicate thread, use a different browser for the time being. I suggest Opera.

   But please allow me to turn this around, why isn't this a Firefox problem? Why does WordPress have to program around something Firefox should resolve automatically? Especially considering IE, Safari, and Opera don't have this issue?

   - nina

5. wolfgrrl
   Member
   Posted 4 years ago #

   Because IE, Safari and Opera are known not to handle code correctly or securely. I choose not to use them because of that.

   If I was submitting this just today for the first time, I wouldn't expect it to get solved today. But as it's been reported for two years, yes it should be resolved by now.

6. thelazygeisha
   Member
   Posted 4 years ago #

   Because IE, Safari and Opera are known not to handle code correctly or securely. I choose not to use them because of that.

   wolfgrrl: Well, I don't want to debate the semantics of that statement, but I would defer back to whooami's remarks that this does affect a very small portion of users, and it is being addressed.

   BrowseHappy doesn't seem to have an issue with Opera, Mozilla, Firefox or Safari. So, there are options, however inconvenient that may be for you.

Topic Closed

This topic has been closed to new replies.