Plugin Author
AITpro
(@aitpro)
Yep some Hosts do now create cloudflare .htaccess code in your root .htaccess file and in the case of BlueHost hosting you now have to make a choice since the cloudflare .htaccess does not work with other .htaccess code like BPS or W3 Total Cache and maybe WP Super Cache as well. See this Forum post: http://forum.ait-pro.com/forums/topic/cloudflare-cloudflare-htaccess-code/
What I suspect regarding seeing the actual current .htaccess code is that you did not refresh your Browser to see the actual current contents of the root .htaccess file. In coding there is a delay in code processing. You will see the last function that was processed until you refresh your browser to see the actual current status. So if you were modifying the root .htaccess file using FTP then the only way you would see the actual current contents of the root .htaccess would be if you refreshed your Browser.
Plugin Author
AITpro
(@aitpro)
Thread Starter
wp.Man
(@wpman-1)
i thought this might be related to the HotLink bug – however, i don’t think you correctly understood the part about the .htaccess…
1) opened BPS editor to look at current and secure files to compare them – the editor for the current .htaccess displayed a version very near the secure version, but not exactly (i assumed activating CF changed a little something)
2) copied the secure file form BPS editor to the current file in BPS editor and saved it
3) tested website – still broken (all 404’s below root domain)
4) repeat 1 & 2, test again, still broken. as i later discovered, the file was apparently never saved by BPS it seems
5) ftp’d the .htaccess file to a local editor and better than 1/2 of the code displayed in BPS was not actually present in the file, thus indicating that the copy/paste from secure to current in BPS failed twice
6) copied code from BPS secure .htaccess, pasted into local copy and uploaded and the problem was solved – no 404’s
so in other words i wasn’t editing the file locally while i was checking it on the server
this never happened before and may only be some weird thing that involved CloudFlare, browser cache and WP Super Cache – who knows – but i wanted to let you know
i’ll run another test at some point and see if i can duplicate the problem
thx!!!
Plugin Author
AITpro
(@aitpro)
Oh ok yep I misunderstood what you said.
Yeah you should be able to copy the secure.htaccess code from the text window to the Your Current Root htaccess file text window and be able to save/update the file. So not really sure why that did not work correctly?
Also just an FYI – you can use the BPS Custom Code feature to “roll your own” and make your own custom Master .htaccess file with all of your code combined. The Blue Read Me help button on the Custom Code page explains how this works. Thanks.
Plugin Author
AITpro
(@aitpro)
Once you have had a chance to test this some more then post your findings back here. Resolving this Thread so that I do not keep checking it. 😉 I will still receive an email notifications from you so when you do get a chance to post your findings then I will get an email. Thanks.
Thread Starter
wp.Man
(@wpman-1)
checked cPanel and the goofy code was there
i disabled hotlink checking … i know … and the code changed to match my domain/sub domains
still, i can’t edit with the BPS editor – it seems to be either eliminating a bunch of the code or changing something that results in everything below the root domain to fail (404)
seems strange, as the built-in editor used to work
the way i tested today was to add a comment to the end of the .htaccess and save it, then i downloaded it with an external editor and the comment was not there
so in short, BPS isn’t displaying or saving correctly
currently i just keep it locked
that fact that the fellas at cPanel have apparently been aware of this for YEARS is ridicules :/
so you can mark this as resolved, or i’ll wait to hear from you
thx
Plugin Author
AITpro
(@aitpro)
You cannot disable the HotLink Protection Tool – the disable button is also broken.
The only way I have found to block the HotLink Protection Tool is by locking the root .htaccess file.
I just thought of something obvious. Are you unlocking your root .htaccess file before trying to edit it? This is a Catch 22 situation though because the HotLink Protection Tool will wipe out the root .htaccess file. 😉
Here is a neat way to get around that – add some testing code to the BPS Custom Code top text box. Add this one line for testing: # Testing and click the save button. Go to Security Modes and click the AutoMagic buttons and then activate root BulletProof Mode. You should see that # Testing has been successfully added to your root .htaccess file. 😉
Yeah the HotLink Protection Tool problem has been going on for over 10 years. I posted in their Forum and they informed me to submit a bug report. I did that and nothig happened, but in all fairness let’s say they did fix the tool in the most current version of cPanel, but if Host’s are still using an older version of cPanel then it would not have the new fix. cPanel is huge and worldwide so maybe it will just take time to get this fixed or maybe it never will get fixed. 😉
Thread Starter
wp.Man
(@wpman-1)
yeah, i know it can’t be disabled – that’s why i said “i disabled hotlink checking … i know … “
my host is pretty good at updating … matter of fact, the recently updated cPanel – maybe that’s when the trouble started 🙂
well, good luck with the work-a-round you’re working on 🙂
