Options All -Indexes
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

Alas, no joy.

Second, I’ve never had problems with this until WordPress 3.2.1 came out. I’m running three sites out of the same account (each site has its own domain name). Two of the sites upgraded without incident. The third site, which is hands-down the “biggest” site, keeps getting “fatal error: out of memory” whenever I try to use the automatic upgrade, so I’m still using 3.1.4.

Honestly, I hated the manual FTP upgrade from the older versions and I refuse to go back to doing things that way. There’s been no problem with 3.1.4 other than the annoying reminder at the top of the admin screens, which won’t go away until I finally do upgrade. But that’s neither here nor there.

More recently, I’ve noticed problems with uploading images — a seemingly routine task that should never be a problem. Same “fatal error” about being out of memory. Sometimes, I even hit the limit just trying to view Site Stats (with Jetpack).

I’ll try to see if manually setting the limit to 30M does any good, but I’m guessing it won’t… so I’m just asking to see if any other 1and1 users out there decided to pull the trigger and become former 1and1 users. If so, where did you take your business? How satisfied have you been? How does the pricing compare?

I had neglected to share this one on my previous comment — on many of 1and1 servers (the shared ones), the default parser for .php files is PHP 4, *NOT* PHP 5. This caused me no end of headaches, because none of my sites needed PHP4, but rather several of my sites (WordPress 3.x, Drupal 6, Joomla 1.5) either didn’t work at all with PHP4 or would have crazy weirdness.

So, to fix that. you should put the following in your .htaccess file. You can either put in in your root (htdocs) folder or in any subfolder that contains .php files that you want to be processed as php5 instead of php4

(uiserver):account-num:~ > cat .htaccess
# Begin tips I saw on Internet about 1and1 and wordpress export/xml and upgrades
Options All -Indexes
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

I still can’t figure out a straight answer on 1and1 and actual PHP limits. What I see from phpinfo() is that PHP4 has a memory_limit of 8M and PHP5 has a memory_limit of 128M. I’ve tried setting php.ini settings of

(uiserver):account-num:~ > cat php.ini
memory=16MB

and changing that memory from 20, 30, 32, 48, 64, etc… with varying non-conclusive results. Some posts say 1and1 limits to 20m, some say 40m, and 1and1′s own FAQ says 30M on one post and 10M on another.

http://faq.1and1.com/scripting_languages_supported/php/13.html says 10M
http://faq.1and1.com/scripting_languages_supported/php/12.html says 30M

http://faq.1and1.com/scripting_languages_supported/php/6.html says the defaults for php5 (through another link) are 40M, but my server says 128M.

I’ll be opening a ticket with them to find out the real deal… I need to stop my server 500 errors, or at least find the culprit or major reason so I can change some other settings to mitigate the problems.

One of these issues is the PHP memory limit. I do use php.ini to set memory to 20m and when I started doing that, it fixed many issues on most of my blogs. I can confirm that without that setting, many of my blog admin pages crash with 500 error or other timeouts. So it’s at least doing something, and I make it the default on all my sites — a php.ini in root and a copy of it in wp-admin. Every time I do a WP upgrade, I make sure I put this file in both places.