Skip to content

Latest .htaccess file causes redirect loop on install #60

Closed

Description

@mcheck

Using evolution 1.0.15, the latest additions to the .htaccess file is causing a redirect loop on a fresh install at wp-admin/install.php

I didn't check into where it is happening, but removing the added RewriteConds allows it to work as normal.

Happy to help track it down if you like.

Activity

  1. mcheck commented on Jun 9, 2015

    @mcheck
    ContributorAuthor

    Actually I don't know what might be causing it. I removed the .htaccess rules, reset the permissions and I get the same thing. Since this is a staging system, I simply pushed out my local data to it: cap staging evolve:up and it all works. But I would like to know why the install no longer works.

  2. ericrasch commented on Jun 19, 2015

    @ericrasch
    Contributor

    @mcheck This issue is coming from the <files install.php>

    A workaround that worked for Genesis is this which allows for the install.php to be executed on local environments:

    SetEnvIf Host ^local\. allow_wp_install
    <files install.php>
      Order deny,allow
      Deny from all
      Allow from env=allow_wp_install
    </files>
    
  3. mcheck commented on Jun 19, 2015

    @mcheck
    ContributorAuthor

    Thanks, odd that this worked fine on staging for me.
    What is the general workflow in setting up a new site - is the wb db already set from a deploy?

  4. EvanK commented on Jun 19, 2015

    @EvanK
    Contributor

    That's right, as of 1.0.15, we are denying access to the install.php for non-local environments (as a security measure).

    The intention being that an installation should be handled on the local stage, and then a deploy + db:up would get the db initialized for staging or production. Note: we need to get this documented

    We are doing this as part of the virtualhost template, so it should only occur on a machine that was provisioned with .15 or later

  5. added a commit that references this issue on Jul 19, 2015
  6. EvanK commented on Jul 29, 2015

    @EvanK
    Contributor

    Closing out, as this should be addressed by the workflow documentation in #70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions