How can I change my RW File Path - to avoid manual changes on Bluehost from being overwritten on publisihing


(Doug Bennett) #21

@Nicko,
Just out of curiosity what are you trying to do with the htaccess file setup?

It looks like you’ve got a few strange directives in the file.

You have multiple RewriteEngine on Directives, only one is needed.

If the htaccess file listed above is in your document root directory then There’s no need for this option so I’d remove it.

If all you’re looking to do is force https try this as your .htaccess file;

RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

(Nicko) #22

Yes, it looks like things are coming together - your help was brilliant - thank you. I’m not out of the woods yet, but it looks like I’m getting close now and I’ve stopped freaking out. Really appreciate your time.

Regarding the fonts, I spent a quite a fews hours and many late nights trying to find out where insecure font was coming from and what stack it was, but in the end I gave up and just went to cloudflare. :slight_smile: Thanks for letting me know though - not sure what to do about it.


(Nicko) #23

Hi @teefers, Thanks for that. I have had help from Adrian at sitelok over the years and this may be some of his code. Are you saying I can delete the RewriteRule and is replace with the RewriteCond?

I’ll make the changes and have saved the original htaaccess, so i can check with Adrian to see if he had it a certain way for anything. This is well out of my league. Thanks for your help - very much appreciated!!


(Doug Bennett) #24

You may need one RewriteEngine On At the top so the entire ht access file would look like:

RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

This would redirect all non-https request to https.


(Nicko) #25

Thanks @DLH and @teefers, the above seems to have worked a treat. It looks like everything is working. I still have more to check everything, but looking great so far. Thanks for you guidance!

On a side note:

I am getting a note after publishing saying that I have more than one index.html. Is this an issue in all cases.
There in only one home page, but for example:
I have a page that has a folder called beneficiaries, with a file name index.php
another folder with transparency with file name as index.php
Contact page in contact page folder with a file name index.html

This seemed to be the only way i can display nice looking URL’s that looks like

www.example.com.au/foldername

not

www.example.com.au/foldername/filename.html

or

www.example.com.au/foldername/filename.php

Thanks - I appreciate your time.


(Doug Bennett) #26

You get that notification when you have both an index.html and an index.php in the same directory (folder) on the hosted site.

This usually happens when you have added something to a page(a stack) that requires PHP. RapidWeaver will automaticity change the file extension to PHP for you. RapidWeaver’s publishing will NOT delete anything (a good thing) so it’s up to you to manually delete one of the two index files.

This is called “tidy links” in RapidWeaver. Web servers can if given a URL to a directory without a complete file name will look for files in a specific order like index.html or index.php. The server will display the first “index” file it finds in the order it’s looking in so having multiple index files might appear that changes you have made aren’t getting applied.

If you get that warning message you should use your hosts file manager function or a stand-alone FTP client like Transmit or FileZilla to manually delete the index.html or index.php file that’s not being used anymore. You can look at the page inspector in RapidWeaver to determine what extension (PHP or html) is being used.


(system) #27

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.