Cannot create categories in 2.3.3

Did you try disabling all the plugins and see?

yea still the same with all plugins disabled
its a server issue im 99% sure but I need to know what needs changed on the server setup to inform my host

okay its a server problem after all:

It was a mod_security issue
add the following code in your .htaccess file

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

Well hey it might work for YOU but I bet this doesn’t work for the majority of users.

This topic is NOT RESOLVED for me!

WP 2.3.3 is unusable for me.

Fresh install, NO plugins. I cannot:

delete posts
delete pages
add categories

I’m tearing my hair out here yet nobody seems to be addressing this issue with a fix.

Get this scenario.

I have a WP blog running 2.3.3. on https://www.mydomain.com It was installed under WP 2.1 it’s been upgraded to WP 2.3.3 – it runs multiple plugins.

It works fine

I create a new WP 2.3.3 install on subdomain.mydomain.com with no plugins and I get the cannot delete posts, pages and can’t add categories problem.

Same product but one install is on a subdomain. That’s all.

Is anybody from WP addressing this MAJOR PROBLEM???

Is anybody from WP addressing this MAJOR PROBLEM???

No, because from what you are saying, it does not appear to be a major problem with WordPress.

As you pointed out, it works fine on one setup of yours and does not work on another. Clearly, there is some difference between the two setups. Unless we know what that difference is, we cannot address it. If it is addressable by WordPress at all.

WordPress is a program to product website output and to manage a database. It is not a webserver, and it cannot control what your webserver does. Misconfigurations there must be addressed there.

Also, shouting and getting all upset doesn’t help. WordPress is free. The support is free. If you act like a jerk and such, you’ll probably get less help, because we don’t have to help you. You have not paid us anything to do so. Honey gets more bees than vinegar. Keep that in mind.

It’s a major problem for a lot of people out there who have lost categories and functionality.

It’s a major problem when you structure your websites around a piece of software that goes from working to not working in one release.

It’s a major problem when there are multiple threads on the same subject.

No? Are we all wrong?

I tell you, this is the last time I ever upgrade from a working version for a minor bugfix! I’ve learnt that lesson and no doubt so have a lot of others. Thankfully my main site is working so at 2.3.3 it shall stay – for the forseeable future.

If WP is unstable on a subdomain install then how about letting us know before we choose it as weapon of choice?

As you’ll appreciate a lot of time is invested in blogging and a lot of time equals a lot of money.

It would be nice if the WP developers would ensure that releases are bug free before moving onto the next set of “features”.

It’s a major problem for a lot of people out there who have lost categories and functionality.
It’s a major problem when you structure your websites around a piece of software that goes from working to not working in one release.
It’s a major problem when there are multiple threads on the same subject.
No? Are we all wrong?

Yes, you are all wrong.

WordPress 2.3.3 did not change how categories worked, and repeating the same tired arguments over and over doesn’t change that very simple fact.

Your site is now broken. I grasp that. I understand your pain. Really. But instantly blaming the upgrade just because you upgraded at around the same time you noticed the problem is not helpful. Stamping your feet and saying “WordPress is broken fixit fixit fixit!” is not useful information.

WordPress is not broken. Get it? Only when you accept that and are willing to accept that idea and accept that there is some other kind of problem going on will you be able to actually fix the problem.

Look, I’ll make it as plain as I possibly can:
WE CANNOT FIX YOUR PROBLEM.
We cannot fix anybody’s problem. All we can do is post messages to you on this forum. Text. Words. We can advise, we can listen, we can try to help, but ultimately, you’re going to have to fix your problem yourself.

For us to help you, you have to help us help you. You need to explain the problem. You need to be willing to listen to us. You need to debug your own site. You may have to talk to your host. I don’t know what you’ll have to do, but you’ll most certainly have to do something other than simply throw around blame.

I tell you, this is the last time I ever upgrade from a working version for a minor bugfix! I’ve learnt that lesson and no doubt so have a lot of others.

Then you learned the wrong lesson. WordPress 2.3.3 changed FIVE FILES. Just 5. That upgrade was a security bugfix and some other minor fixes. It did not cause your problem.

Thankfully my main site is working so at 2.3.3 it shall stay – for the forseeable future.

Which only proves my point.

If WP is unstable on a subdomain install…

WordPress has no problem with “subdomain installs”, and it is not “unstable” in any sense of the word. Don’t draw conclusions from YOUR SPECIFIC installation into a general idea.

It would be nice if the WP developers would ensure that releases are bug free before moving onto the next set of “features”.

No piece of software is ever bug free, but the problem you are describing IS NOT A BUG. Simple, really.