Community Q&A:
Tim S requested this question: wp overwriting .htaaccess file
urls for blogs no longer work: weightlosswestchesterny.com/weightlossblog/ and scarsdaleaikido.com/aikidoblog/ ..htaaccess file is overwritten to allow only default urls and not postname. chaging urls is very bad for seo for obvious reasons.
I spoke with a developer and this is a common problem. your company tried all the basic approaches including testing plugins, checking errant code in wp-config file, looking into themes (twentyfourteen & iconic one). Nothing resolved the issue. There are internal server side problems that should be investigated as the source. Assuming you have other customers with this issue and they are as frustrated in resolving it, you may not hear about it so much in your department because they just leave your company as I would expect to do as well.
The developer explained the standard fixes: set permissions to read only for .htaaccess file which will break whatever is overwriting - then look at your company's logs to see what broke. That is the source of the problem. Your company said no to this fix. The second fix is to set permissions to the .htaaccess file as read only and leave it there so whatever is trying to over-write is blocked. Your company set it to 444 and the file was still over-written and the blogs broke. Currently I have deleted the local .htaaccess file and coded the ones in the folder above to handle the requests. From time to time this thing actually creates a new .htaaccess file locally which then breaks all the urls in my blogs. So the fix your company offered was to sit around and wait for the blogs to break and go in to fix them by hand every time. That doesn't work for obvious reasons.
I spoke with a developer and this is a common problem. your company tried all the basic approaches including testing plugins, checking errant code in wp-config file, looking into themes (twentyfourteen & iconic one). Nothing resolved the issue. There are internal server side problems that should be investigated as the source. Assuming you have other customers with this issue and they are as frustrated in resolving it, you may not hear about it so much in your department because they just leave your company as I would expect to do as well.
The developer explained the standard fixes: set permissions to read only for .htaaccess file which will break whatever is overwriting - then look at your company's logs to see what broke. That is the source of the problem. Your company said no to this fix. The second fix is to set permissions to the .htaaccess file as read only and leave it there so whatever is trying to over-write is blocked. Your company set it to 444 and the file was still over-written and the blogs broke. Currently I have deleted the local .htaaccess file and coded the ones in the folder above to handle the requests. From time to time this thing actually creates a new .htaaccess file locally which then breaks all the urls in my blogs. So the fix your company offered was to sit around and wait for the blogs to break and go in to fix them by hand every time. That doesn't work for obvious reasons.
ANSWERS
|
0
|
Hello, Apologies for the continued problems with your website. When we reviewed your site, it is apparent that your site has been hacked with the same code injection from 3 weeks before. I just went back into your site and found the same hack. Just to be clear, we did not set your .htaccess file to be read-only. We noticed BEFORE we made any changes that your files were all being set to 444 permissions. We noticed this because whenever we would try to make any changes, they wouldn't save. When I researched to see if anyone had every reported this type of issue before, I found this post that discussed the same thing happening. They described the issue as a hack and that malware should be removed. Due to the public nature of our forum, we can't discuss specifics of your account. However, you'll need to have a developer clean the hack, make sure your WordPress installation core, plugins and themes are up-to-date. Also, make sure to change your account passwords (cPanel, FTP, WordPress Admin, etc.) as this is standard protocol when you've been hacked. Apologies again for the continued problems, if you have any further questions or comments, please let us know. Regards, Arnel C.
|
Want to share this Question?
Tweet
Help Center Login
Related Articles
It looks like there are no related articles.
Would you like to ask a question about this page? If so, click the button below!
