WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Updating from 3.0.6 to 3.0.8 gives HTTP-error 500 (Internal Server Error)

[Resolved] Updating from 3.0.6 to 3.0.8 gives HTTP-error 500 (Internal Server Error)

  • I’ve just updated BackWPup to 3.0.8, but then I get HTTP-error 500 (Internal Server Error) when going to the BackWPup admin page. It’s a multisite installation if it makes any difference. Deleting the plugin files and restoring the ones from a backup (3.0.6) makes it work again.

    Any suggestions?

    http://wordpress.org/extend/plugins/backwpup/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Daniel Hüsken

    @danielhuesken

    The change is that wp-cron.php will used for start jobs instead of a front end call.

    Did you have any restrictions for wp-cron ?

    Not that I’m aware of.

    Trying to access other BackWPup pages (like logs) returns a WordPress message of permissions issue. I’m using User Role Editor, so I suppose it could be a capability issue?

    *Edit*
    It seems to still keep backing up fine.

    Plugin Author Daniel Hüsken

    @danielhuesken

    The backup job not depends on permissions that is why the backup works.

    With permission Prlugin did yue use? Please check that your user hase all backwpup captiblitys.

    I’m using “User Role Editor” (http://wordpress.org/extend/plugins/user-role-editor/) and all BackWPup capabilities are checked.

    • Backwpup
    • Backwpup backups
    • Backwpup backups delete
    • Backwpup backups download
    • Backwpup jobs
    • Backwpup jobs edit
    • Backwpup jobs start
    • Backwpup logs
    • Backwpup logs delete
    • Backwpup settings
    Plugin Author Daniel Hüsken

    @danielhuesken

    So i have improved the Roles in the Plugin. In next version you can setup with Role for BackWPup will used in the user settings. I hope that resolves the Problem.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Resolved] Updating from 3.0.6 to 3.0.8 gives HTTP-error 500 (Internal Server Error)’ is closed to new replies.