sinnyo

It turns out my problems arose because WordPress was using the wrong PHP extensions. I was asked to add a line to .htaccess:
AddType x-mapp-php5 .php .php4
.. and the problem went away. I have also installed MediaWiki on the same domain – its installer told me it had to use .php5 extensions in order to work too, and MediaWiki fixed the .htaccess to compensate. I wonder, might such a feature be added to WordPress’ installer in future..?

Brilliant! Exactly what I needed. Thank you very much.

I wouldn’t know how to be sure, but I’ll contact my host, 1&1, to see if that is the case. Thanks. ??

I’m afraid this issue has reared its head again post-3.0.

I see these errors too, running the latest WordPress 3.0 installation. I managed to upload a good dozen or so images before this problem crept in, and now it’s quite prevalent. My files are JPGs, just like all the other images I uploaded without issue. I’ve tried renaming the files, tweaking “.jpg” to “jpeg”, and checking that the colours were RGB, not CMYK. Short of having to change all my file types to .PNG, I can’t seem to find a way around this.

I officially have ZERO idea what’s going on with my changeover here. I’ve forgotten which version of b2e I had running, but when running this script on the most recent version of WordPress (in the b2e’s old directory, ‘/blog’) I hit submit on the first page and am routed to my site’s index page. Not only that, but it takes me to the index.php, not index.html which has frames. When I delete my index from the site I get a server 500 error, but still no matter what I try I cannot get past that index! Where on earth is the submit sending me to?

EDIT: Waitaminute… import-b2evolution-wp2.php has an error on line 193. Surely it should read

“<form method=”post” action=”import-b2evolution-wp2.php?step=1″>”?

Could that be why I’m being fed errors? Unfortunately, the faffing so far has crashed my web server so I’m not in a position to test it yet.

EDIT 2: Freaking YES, it worked. I actually debugged something, which is a first! So, um, yeah, if anyone gets a similar problem, that’s why. I reckon my transfer to my site’s index must have been because the 404 direct’s playing up.