w3total Chache creates .htaccess in wrong location breaking site

  • Resolved saltyp

    (@saltyp)


    3 years, 9 months ago

    So I am on a bitnami install of wordpress. The .htaccess file is not in htdocs. It is in conf. So yesterday I was haveing problems with my site. noticed that w3 had made a htaccess file.

    Bottom line can I tell w3 to not just make the file? Or at least tell it where the correct one is?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @saltyp

    Thank you for your inquiry and I am happy to assist you with this.
    Bitnami moved the apache configuration due to security reasons. So for this, you need to check this article and video in which the procedure is explained, and also they used W3 Total Cache as an example.
    For more detailed instructions, please reach out to their support.
    Thanks!

    Thread Starter saltyp

    (@saltyp)

    Yes I know how to update their htaccess.conf
    The problem is that w3total cache keeps creating a new .htaccess in htdocs. It conflicts with the real one. Apache finds it and cases all types of problems.

    Update. So I created a blank .htaccess in htdocs and set the permissions to root only so w3 could not use it. Well that crashed everything.

    I am at the point of just ditching w3. It dose not let you configure the htaccess location. It just insists on creating rogue files and will not let you configure a different location for the htaccess file as far as I can tell.

    Is there anyway to do this? I like w3, it has many options but this is a critical flaw.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @saltyp

    Thank you for your question.
    This is not a critical flaw in W3 Total Cache. I’ve provided you the solution that bitnami suggested. They also recommend W3 Total Cache.
    Again, I suggest you reach out to their support for assistance with this and more details on how to solve this.
    One thing you may try to do is to change the file permission and therefore prevent W3TC to write/create .htaccess and add the rules manually from Performance>Install.
    Thanks!

    Thread Starter saltyp

    (@saltyp)

    So there is no way to instruct w3 total cache to not create a new .htaccess all the time?

    Like I said I made a blank .htaccess and set it to read only. It worked to block w3 but the entire site turned into a 404 ecept the homepage that was missing all its css because the w3 cache files failed to load…

    • This reply was modified 3 years, 9 months ago by saltyp.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘w3total Chache creates .htaccess in wrong location breaking site’ is closed to new replies.