Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author AITpro

    (@aitpro)

    To get the site back up use FTP and delete the BPS root htaccess file in your WordPress root installation folder.

    Maybe your host does not allow you to lock your root htaccess file or you have added some custom htaccess code to BPS Custom Code that your host does not allow or is bad/invalid custom htaccess code.

    Do these steps:
    1. Go to the BPS htaccess Core page > click on the htaccess File Editor tab page > click the Unlock htaccess File button and the Turn Off AutoLock button.
    2. Go to BPS Custom Code and click the Delete button to delete all custom htaccess code that you have added to BPS Custom Code. If you want to save your custom htaccess code before you delete it then click the Export button to save a backup of your custom htaccess code.
    3. Run the Setup Wizard again.

    A new possible cause for a 500 error in BPS .53.1 is the new 405 HEAD Request htaccess code. See this forum thread for the solution: https://ww.wp.xz.cn/support/topic/500-error-when-updating-to-531?replies=10#post-7783030

    If the problem is still occurring after doing the steps above then delete your root htaccess file again to get the site back up and then go to the BPS System Info page and copy and paste this information in your reply post:

    Server Type:
    Operating System:
    WP Filesystem API Method:
    Server API:

    Plugin Author AITpro

    (@aitpro)

    [dupe info]

    Thread Starter George Sexton

    (@gsexton)

    1. The buttons you describe don’t seem to exist.

    http://www.mhsoftware.com/~gsexton/bps-1.png

    2) Did that.
    3) Did that. Crashes site.

    [Wed Jan 20 12:20:17.497974 2016] [core:alert] [pid 7742] [client 192.168.1.19:52009] /home/gsexton/public_html/.htaccess: Options not allowed here, referer: http://reddwarf.private.mhsoftware.com/~gsexton/wp-admin/options-general.php

    I edited /etc/apache2/mod_userdir.conf and set “AllowOverride All” and now this appears:

    [Wed Jan 20 12:23:20.288982 2016] [core:alert] [pid 8490] [client 192.168.1.120:64496] /home/gsexton/public_html/.htaccess: Invalid command ‘RewriteEngine’, perhaps misspelled or defined by a module not included in the server configuration

    I added rewrite to /etc/sysconfig/apaceh2/modules and re-started.

    Then I got errors about Order.

    I added access_compat to /etc/sysconfig/apache2/modules and re-started.

    The instance of wordpress now runs.

    I think requiring access_compat is a bad idea personally. It also seems like you could test for mod_rewrite and mod_access_compat and not activate or run your wizard if they’re not present.

    Plugin Author AITpro

    (@aitpro)

    Glad you got it sorted out. Yeah it is a totally different ballgame when you have a personal self-hosted server vs a hosted server on a web host. Hosted servers are typically configured with all the standard conf stuff already. ie mod_rewrite, AllowOverride, Options, etc.

    The Lock and AutoLock buttons are only displayed for CGI server types so that means you have a DSO server type and are not allowed to lock htaccess files on a DSO server type so the buttons are not displayed for DSO server types.

    The Setup Wizard does test for and create either mod_access_compat or mod_authz_core htaccess code based on the actual test results using both variants of the htaccess code when running the Setup Wizard. Unfortunately, it is not possible to check for loaded Modules on the server from the website. So the only way to test which htaccess code your server supports is to get the HTTP Status Response code from testing the htaccess code variants and then processing/creating the correct htaccess code in the Wizard based on the HTTP Status Response. We attempted to do this same type of testing for mod_rewrite and you cannot do anything with the results because they are inconclusive/meaningless when a 500 error occurs.

    Personal Notes: 192.168.x.x is a Private Network IP address. So that would mean that this server is a Local Hosted server or is behind/on a Private Network.
    https://en.wikipedia.org/wiki/Private_network

    Thread Starter George Sexton

    (@gsexton)

    >> Unfortunately, it is not possible to check for loaded Modules on the server from the website.

    It looks like you actually can:

    http://php.net/manual/en/function.apache-get-modules.php

    I tested this on my machine and it works as expected.

    Plugin Author AITpro

    (@aitpro)

    Yeah that function only works for DSO server types and not CGI server types. If the ratio of DSO to CGI were higher we would add additional conditions for that, but I believe DSO server types make up around 5% vs 95% CGI server types. 😉

    Plugin Author AITpro

    (@aitpro)

    http://stackoverflow.com/questions/3178173/alternatives-to-apache-get-modules-to-get-list-of-loaded-apache-modules

    this only works when PHP is installed as an Apache module. This will not function when using PHP as CGI (ex: suPHP)

    Plugin Author AITpro

    (@aitpro)

    And then of course the total number of people who have their own self-hosted server is going to be extremely low. I can count the total number of BPS forum thread questions regarding a self-hosted DSO server type in the last 5 years on one hand. 😉

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Crashes WordPress Installation’ is closed to new replies.