Forums

[Plugin: Wordpress Automatic upgrade] 500 Internal Server Error anyone??? (11 posts)

  1. leighangela
    Member
    Posted 8 months ago #

    I loved the plugin, but now I cannot auto update any other plugins. Any time I try I get a 500 error. I can't even get plugin update info from my plugins page.

    I tried deactivating and deleting the Auto Update plugin, still not fixed.

  2. leighangela
    Member
    Posted 8 months ago #

    I can't use the Tools link either, to control some of my plugins! Same 500 Error. HELP!

  3. leighangela
    Member
    Posted 8 months ago #

    It's something in wp-admin because I cant use any link in there.

  4. musnake
    Member
    Posted 8 months ago #

    If you have the use of ftp or some file manager, go into the plugins folder and rename the auto update plugin's folder which will render it 'uninstalled'.

    Tu uninstall all the plugins easily you simple rename the wp-content/plugins folder itself!

    I stopped using the auto plugin after 2.7.1 for similar reasons.

  5. leighangela
    Member
    Posted 8 months ago #

    musnake, I already completely removed the auto update plugin via ftp. It didn't help.

  6. musnake
    Member
    Posted 8 months ago #

    Hmm, well 500 error will generate server error log entries (usally ;) )

    What does your hosting account's error log say? If you can't find it on your hosting account's cPanel (or whatever) you should ask your tech support people to check on it...

    Let's see what the machine is thinking...

  7. leighangela
    Member
    Posted 8 months ago #

    Is this it? I was able to open a php_errorlog in Dreamweaver and here's what I get:

    [03-Mar-2009 11:31:10] PHP Warning: require_once(lib/ftp_class.php) [function.require-once]: failed to open stream: No such file or directory in /home/jerrybru/public_html/wp-content/plugins/wordpress-automatic-upgrade/wpau_helper.class.php on line 19

    [03-Mar-2009 11:31:10] PHP Fatal error: require_once() [function.require]: Failed opening required 'lib/ftp_class.php' (include_path='.:/usr/local/php52/pear') in /home/jerrybru/public_html/wp-content/plugins/wordpress-automatic-upgrade/wpau_helper.class.php on line 19

    There is another error log that is empty.

  8. musnake
    Member
    Posted 8 months ago #

    Yeah, it's definitely that plugin.

    The author says this...

  9. nexview
    Member
    Posted 2 months ago #

    Plug seemed like it would be very helpful. I tried to use this plug with intent upgrade from 2.7.1 to 2.8.4. It has brought down my entire site, when trying to access my wp admin page or hitting the site externally, I get the same 500 Internal Server error. I'm locked out completely.

    I uploaded a backup index.php file via FTP, and changed the name of the plugin directory name (effectively deactivating it), but to no avail. I did back up all, could restore the db using phpMyAdmin (not sure how to do that, assume I "import" the sql bkup file and it'll over write the one currently on the server).

    The auto update in the wp admin panel to update wp version or any plugins never worked - I'm in the the "You don't have permission to access" crowd on this one. Sounds like a server access error, but not sure, and not sure how to get back in. I've put in a request to my ISP, but waiting. I know they don't really support wp. Any thoughts appreciated.

  10. davydyuk
    Member
    Posted 2 months ago #

    I think the problem with permissions of your files/folders.
    You should set 755 for all your folder and 644 for files.

    or not correct rule in .htaccess file.

    [signature moderated Please read the Forum Rules]

  11. nexview
    Member
    Posted 2 months ago #

    davydyuk was correct, it turned out to be files that had settings higher than 755. After his advice, I used my ftp client to set all file permissions as he describes on the "wordpress" directory and ensured settings cascaded through all subdirectories, but I must have missed the permissions on the critical file(s), I guess they weren't in the wordpress directory. My host ran a script that fixed it. Problem is, it took them a week to do it.

    Thanks davydyuk for you advice and offer to help!

Reply

You must log in to post.

About this Topic