Submitted by sgrayban on Wed, 01/04/2012 - 20:21Comment #10
I'm not sure... how long was that out before 3.3.1 did ? Was there even a 3.3.0 version ?
No version 3.3.0
$ wget http://wordpress.org/wordpress-3.3.0.zip
--2012-01-04 18:10:42-- http://wordpress.org/wordpress-3.3.0.zip
Resolving wordpress.org... 72.233.56.139, 72.233.56.138
Connecting to wordpress.org|72.233.56.139|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-01-04 18:10:42 ERROR 404: Not Found.
The last version was 3.2.1 which worked for everyone.. even the bug report for that one was small compared to what 3.3.1 has caused. Plugins that worked for years stopped working for no apparent reason.
I think I am going to force a down grade on all my clients that are using wordpress and disable the WP script until this is fixed. Going to take me hours to complete that as it is.
Submitted by sgrayban on Wed, 01/04/2012 - 20:27Comment #11
I know something is wrong with 3.3.1 -- I have 2 plugins for wordpress that have worked for years and is not restricted to admin only yet in 3.3.1 I get a error message that says "You do not have sufficient permissions to access this page." I know my code and I know that it should work for any wordpress version.
Comments
Submitted by JamieCameron on Tue, 01/03/2012 - 23:13 Comment #1
Thanks - this new version is now available for download.
Submitted by sgrayban on Wed, 01/04/2012 - 14:53 Comment #2
I would pull that. I am getting reports that a lot of my clients can't access there plugins after upgrading and I am trying to figure this out.
Some sites are ok while most of them are not working correctly.
Submitted by sgrayban on Wed, 01/04/2012 - 15:56 Comment #3
There is something terribly wrong with 3.3.1
I would stop any upgrading right now until I find out what is going on.
People are complaining that they can't upload and/or can't access there plugin settings and I have even found some that can't get into the admin side.
The wordpress support forum is full of issues.
Submitted by sgrayban on Wed, 01/04/2012 - 15:59 Comment #4
And now I finding a ton of people that are downgrading to 3.2.1 that does work for them.
Submitted by JamieCameron on Wed, 01/04/2012 - 16:14 Comment #5
Is wordpress planning on releasing a fix for this?
Submitted by sgrayban on Wed, 01/04/2012 - 16:16 Comment #6
To much is going to know yet. The bugs are coming faster then I can read and all the solutions given aren't 100% for everyone.
A lot are simply downgrading to 3.2.1
Submitted by sgrayban on Wed, 01/04/2012 - 16:18 Comment #7
I assume that the script installer can downgrade WP if needed ?
Submitted by sgrayban on Wed, 01/04/2012 - 16:20 Comment #8
If you want to see how bad this is just read http://wordpress.org/support/forum/installation
It's gotten to the point that some upgrades completely fail.
Submitted by JamieCameron on Wed, 01/04/2012 - 18:23 Comment #9
Does 3.3.0 have this same issue?
Submitted by sgrayban on Wed, 01/04/2012 - 20:21 Comment #10
I'm not sure... how long was that out before 3.3.1 did ? Was there even a 3.3.0 version ?
No version 3.3.0
$ wget http://wordpress.org/wordpress-3.3.0.zip
--2012-01-04 18:10:42-- http://wordpress.org/wordpress-3.3.0.zip
Resolving wordpress.org... 72.233.56.139, 72.233.56.138
Connecting to wordpress.org|72.233.56.139|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-01-04 18:10:42 ERROR 404: Not Found.
The last version was 3.2.1 which worked for everyone.. even the bug report for that one was small compared to what 3.3.1 has caused. Plugins that worked for years stopped working for no apparent reason.
I think I am going to force a down grade on all my clients that are using wordpress and disable the WP script until this is fixed. Going to take me hours to complete that as it is.
Submitted by sgrayban on Wed, 01/04/2012 - 20:27 Comment #11
I know something is wrong with 3.3.1 -- I have 2 plugins for wordpress that have worked for years and is not restricted to admin only yet in 3.3.1 I get a error message that says "You do not have sufficient permissions to access this page." I know my code and I know that it should work for any wordpress version.
http://profiles.wordpress.org/users/sgrayban/profile/public/
I am active with WP code so I know what should and shouldn't be working.
Submitted by JamieCameron on Wed, 01/04/2012 - 22:18 Comment #12
There was definitely a 3.3.0 release a week or two back.
Virtualmin unfortunately doesn't deal with downgrades very well, so all we can really do is wait for a fixed version to be released and offer that.
Submitted by sgrayban on Wed, 01/04/2012 - 23:07 Comment #13
There is a 3.3 in the repo.
http://wordpress.org/download/release-archive/
But I have no idea if that one had issues with plugins. All I know is that 3.2.1 worked with all plugins.
There still is no official word why 3.3.1 is breaking hundreds of addons plus the other hundred bugs posted.
Submitted by sgrayban on Thu, 01/05/2012 - 16:25 Comment #14
I have finally figured this out.
You need to make the cgi wrapper is
fcgi
and make sure thatcgi.fix_pathinfo = On
is set.Everything worked perfectly for me after making this change.
If anyone else has this problem let them know of the fix. I know that really old VM installs only used cgi as the wrapper default.