dougjoseph

As mentioned, saving your PNG files in 24-bit mode instead of 8-bit mode will do the trick.

I also have this random “Internal Server Error” with WordPress on GoDaddy.

The issue is totally random. When it occurs, reloading the page immediately afterward will result in the page coming up with no problems. A few seconds later on a different page, the same error will appear, and again reloading the page immediately afterward will result in the page coming up with no problems. This error is happening about 30% of the time.

I have made sure I am not using FastCGI. That is not preventing the error. I have nothing in the .htaccess file that would cause the issue.

If it was being caused by either a file permission problem or an .htaccess file problem, it would not be random like it is. It seems that then (instead of being random) it would regularly occur. The most likely culprit proposed above is a communication issue with the MySQL database. That may not be it, but it definitely seems to be some kind of server issue. It is extremely frustrating. Sigh.

Thanks.

It looks like the plugin is an older, proprietary way of handling headers. WP3 has a built-in way of registering images as header images, and I want to use that method, but I am looking for a plugin to simplify the process. I know how to use the appropriate code in my functions.php file to access the WP3 header image registration process. I’m doing that. But it is not the easiest way. An easier way would be an easy-to-use plugin with code that registers your images.

Thanks. Will give it a try.

Update: The plugin’s author released an update that fixed the errors that show in the menu.

I read your post. Don’t know the answer. Just wanted to let you know it’s not being ignored. I just don’t know enough to help. Sorry.

Thanks for your help folks!

My first call to GoDaddy support got me a guy who claimed that renaming the php5.ini file would fix the problem. The file had only one command in it, the universal “cgi.fix_pathinfo = 1” command. Who can’t get along with that?

I read somewhere that the command has to do with helping WP to do permalinks. I deleted the file, and still did not have success.

I called GoDaddy back. My second call got me a guy who claimed having Fast CGI enabled (when it was not being used, he claimed) was causing a problem. I am not knowledgeable about CGI or Fast CGI, and I granted him permission to disable it. He said I have power in their online panel to enable or disable it myself, but I don’t know how to do that.

As soon as he disabled it, the problem seemed to go away.

Then my WP sites that were stored in subfolders on the hosting server seem to be able to do permalinks. However, I then upgraded an older WP blog (which was stored in the root folder of the hosting server) to 3.0. I tried to access pages that happen to require permalinks, and they would not function. I get 404 errors.

I tried putting the php5.ini file back, but that seems to re-cause the serious problems I was trying to get fixed. I am now moving the root folder WP blog into a subfolder to see if I can get it to work. Argh.

Sigh. ??

I have full FTP access to my server, and I have uploaded the WP3 gold version, but GD is still showing me either blank pages or nothing at all. Sigh.

Thanks! However, I am now certain my issue is not related to WP at all. I have studied the situation, and I think it is a Godaddy.com server problem.

The Godaddy.com Linux server can serve me any file type except a PHP file, and even a simple PHP page that doesn’t do much of anything (and which is not related to WP at all) cannot be served.

Ugh.

But… Did you say “Gold”? Does that mean version 3 is now public, not in RC status? Cool…

I get this from Apache on Godaddy.com server:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Apache/1.3.33 Server at wvupci.org Port 80

Wait. Now it’s not just blank page, but any part of WP shows Apache error messages. I’m able to get the server to serve up anything except a PHP page that is part of WP. Ugh.

I just upgraded to RC3, and I am now having random “blank page” problems. I am also using a child theme of Twenty Ten. Is there an easy way to revert RC2?

Fernandot:

Hello friend. ??

I have found another issue with regard to the “List Category Posts” plugin’s compatibility with WP 3.0 / Twenty Ten.

If the page (which is displaying category posts) has any photos attached to it, and any one of the displayed category posts has a gallery of photos set to display, then the page’s photos get displayed instead of the category post’s photos.

While I understand the problem, I confess I don’t know how to fix it.

Update:
I logged in as the member with the new capability (who has the role of “author”) and I published a new post in a category unrelated to the page he has permission to edit. I then browsed to view the new post. At that point, I saw the errors in the main menu again:

Warning: preg_split() expects parameter 2 to be string, array given in ~PATH~/wp-content/plugins/role-scoper/hardway/hardway-taxonomy_rs.php on line 235

Warning: Invalid argument supplied for foreach() in ~PATH~/wp-content/plugins/role-scoper/hardway/hardway-taxonomy_rs.php on line 237

I then browsed other areas of the site and saw no errors, and even when I went back to the new post that had just shown the error there were no errors shown there.

However, I then browsed to the category page containing the new post, and errors were shown there:

Warning: preg_split() expects parameter 2 to be string, array given in ~PATH~/wp-content/plugins/role-scoper/hardway/hardway-taxonomy_rs.php on line 235

Warning: Invalid argument supplied for foreach() in ~PATH~/wp-content/plugins/role-scoper/hardway/hardway-taxonomy_rs.php on line 237

Anyone have any ideas what code I could tweak to stop these errors from appearing? Thanks.