Why don’t you just change the memory limit on your server? o_O
Sorry, I don’t have access to the server. I just use WP on boxes provided by hosting companies.
There are TONS of options for increasing these memory limits, and I haven’t been able to get the right combination.
Again, why not just ONE option?
There are several techniques to increase the PHP memory limit and you only need to use one of them. The right one for you depends on your system configuration.
Add: php.ini in the WordPress root folder.
Add the following line to a php.ini file in your WordPress root folder:
memory_limit = 64M
Note: This will only work if PHP is running as CGI/FastCGI.
The next two solutions are more restricted in scope and, in some cases, may be more appropriate choices than affecting all sites.
.htaccess file:
php_value memory_limit 64M
wp-config.php file:
define('WP_MEMORY_LIMIT', '64M');
Shared Hosting
In some shared hosting environments, access to the PHP memory limit setting is restricted. If you cannot make the change yourself, please ask your hosting provider to adjust it for you, or look for a new host that allows more flexibility.
For some hosts renaming php.ini to php5.ini may be necessary.
Some hosting services require the following line in .htaccess to enable a php.ini file.
suPHP_ConfigPath ~/public_html
For some hosts you may need to add the following lines to the php.ini file (if they are not there already):
extension=pdo.so
extension=pdo_sqlite.so
extension=sqlite.so
extension=pdo_mysql.so
Firstly, thanks for trying to help. I appreciate it. Unf, finding which one I need is still a challenge. I’ve tried several already with no luck.
Again, my question stands:
why the HELL is updating WP so complex?
Why don’t they just fix it? It would save thousands of people thousands of hours, not to mention those like you who try to help us.
If this was Microsoft, we’d laugh and laugh at their incompetence.
So who do I contact who can DO something about this?
There’s nothing to “fix”. It’s a server issue rather than a WordPress one. If you want to help out, try getting involved in beta-testing on as many different servers/hosts as you can. Then perhaps we can document more ways of correcting these server issues.
@love65ed – if you’ve tried all of the above, and no luck, then you really need to contact your host. Everything mentioned thus far is not a true fix; they are hacks meant to get around the issue. The ONE option that works is getting your host to change the settings on your box, or find a host who will.
Also, you might want to ease up on your approach. WordPress is community-supported (and not owned by a company) and we are all users just like you, who take a little time out of our day to help others. Please and thank you get you a lot further around here than SHOUTING IN ALL CAPS.
Cheers-
Sorry, I just get so amazingly pissed off with simple things like this. There’s heaps I love about WP, but if even the basics don’t work, people will go elsewhere.
You guys the first ones I’ve found to say it’s a hosting issue. So there’s all this misinformation out there to wade through. More waste.
Why doesn’t WP just address this up front? Why isn’t it a simple FAQ with a simple answer?
Then I could have read it in a minute & contacted my WHP instead of screaming in frustration here.
It would massively improve user satisfaction.
I think the core team is working very hard on trying to improve the new user experience, as well as improve documentation in the codex, but it’s a huge undertaking that won’t be fixed overnight.
Then again, I bet microsoft gets blamed all the time when Windows runs poorly on a bargain-basement no-name computer instead of something better. The issue with hosting is no different; there are a ton of them out there, with widely varying specifications and quality.
However, WordPress has addressed the issue here, by pointing out companies you might want to consider. There are other good hosts out there, but this is a great place to start.
Ok, thanks for the pointers, I’ll have a look. In the meantime, I might just export my WP data, remove & reinstall the new WP, then import again.
Madness, but at least it’s all under my control.
