1 to 16 of 16
I'm getting the same results whether I install with a manual upload, or by using the web installer. When I go to activate the OIOpublisher plugin from the WP admin interface, all I get is the following error:
Error 500 - Internal server error
An internal server error has occured!
Please try again later.
I saw the earlier post about conflicts with the WP automatic upgrade plugin, but I don't see any such plugin listed on my plugins page.
Any idea where I should start looking?
I'd say first point of call should be this thread. It may not be related, but certainly worth checking out.
The other common issue is that of folder permissions, particularly the "wp-content" and "plugins" folders. Make sure they have permissions set to 755. This tutorial on file permissions may also be of use.
If neither of those things help matters, I'd recommend disabling all plugins for a short period and then activating OIO by itself. If there is no 500 error at that point, then re-activate the other plugins one by one until the error occurs.
Let me know the outcome, and we'll continue from there.
PS. Are you using the first official release of WP 2.8, or one of the more recent betas?
Links: Tutorials | Troubleshooting | Bug Trackerindeed, the wp-content, plugins, and oiopub-direct directories all have 755 access.
I'll try out your suggestions
I'm using the official 2.8 release.
Update
Found the conflict -- it's with the 'Calendar' plugin
Unfortunately, that's a critical plugin for my site.
Looks like it doesn't like Twitme either
I'm downloading them both now to see if I can re-produce with 2.8.
Links: Tutorials | Troubleshooting | Bug TrackerNo joy so far. I've installed the latest version of each plugin on a clean WP 2.8 install. I activated OIO first, then the other 2 plugins, but no internal server errors were produced. It may well not be a direct conflict.
It's a bit of a needle in a haystack situation, but it should be possible to track down. There are a couple of ways to proceed from this point:
1.) I give you some suggestions to try as / when I think of them.
2.) You send me Wordpress admin / FTP details via the contact form and I can track it down for you.
Links: Tutorials | Troubleshooting | Bug TrackerWhy don't we start with your suggestion(s) -- I'd like to know a bit more about how these things fit together anyway. Then if that doesn't pan out, I'll get you the admin/FTP issues so you can debug directly.
A couple of initial suggestions:
1.) I still think it might be something to do with the amount of allocated memory available (see this thread for some examples). It might be worth checking to make sure that your web host lets you change the memory level.
If you create a blank php file and put the code below in it:
<?php
ini_set('memory_limit', '70M');
phpinfo();
?>
Then search for 70M on the page when calling that file from your browser. If it's there (which means the change has worked), then can you try increasing the level to 128M in your wp-config.php file to rule out the issue completely:
define('WP_MEMORY_LIMIT', '128M');
2.) Did you add anything in your blog's .htaccess file (if you have one setup) besides the default Wordpress rewrite rules? If so, can you try commenting out the extra lines (by putting # before each line) to see if the 500 error continues.
Links: Tutorials | Troubleshooting | Bug TrackerI verified as you described that I can change the memory limit, then tried both 128M & 256M settings, but with the same results. (I also verified using phpinfo() that the 256M setting was accepted)
I haven't made any manual changes to .htaccess, but the one I have looks like:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule># END WordPress
Back to the drawing board then. I'll see if I can come up with anything else tomorrow.
Links: Tutorials | Troubleshooting | Bug TrackerI've racked my brains but can't think of any other reasons for the error. Anything that has caused this kind of behaviour in the past seems to have been ruled out.
If you want to send your details across, I should be able to figure it out reasonably quickly.
Links: Tutorials | Troubleshooting | Bug TrackerI've sent you site/ftp access details -- please confirm that you've received them, either here or by email.
Details received, I'll check it out later today.
Links: Tutorials | Troubleshooting | Bug TrackerI believe I have resolved the issue by adding .htaccess rules to use PHP5 instead of PHP. I added the following to my .htaccess file:
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php
I undid your changes and now it seems to be loading fine.
Also, I notice that OIO is loading wp-config.php directly. I have wp-config located outside of the web root, which has caused problems with some other plugins, though I see that OIO has some config option for this. If you were to load wp-load.php instead, it knows how to find wp-config for you. (I've had to hack other plugins to do this)
Interesting, I'm glad the php5 switch fixed it. I'll have to check it out on php4 again in case something has gone wrong on that front (I'd have expected more reports if it had though).
EDIT: the new version that I've just put out on the site will use wp-load.php by default (if available), otherwise it will use wp-config.php
Links: Tutorials | Troubleshooting | Bug Tracker1 to 16 of 16