Plugin Author
AITpro
(@aitpro)
The only related forum topic I could find for this type of issue is this one: http://forum.ait-pro.com/forums/topic/yoast-wordpress-seo-and-xml-sitemaps/#post-11513
The cause of the problem was that person created personal custom .htaccess redirects that caused the problem. By default BPS standard .htaccess code does not cause any 404 issues/problems with Yoast. I think the root .htaccess lock issue that you are referring too was to protect the BPS root .htaccess code from being deleted by Yoast. That is an old problem that should no longer be occuring and it would not affect Yoast or cause a 404 error.
My hunch is that this has to do with a caching plugin and could be a chain reaction problem. Something like you are using a caching plugin that uses .htaccess code and that caching code is missing or not added to your root .htaccess file. Or you have created custom .htaccess code in BPS Custom Code that is causing the 404 errors or the problem is not related to BPS and is being caused by something else entirely. Do the troubleshooting steps in this link: http://forum.ait-pro.com/forums/topic/read-me-first-free/#bps-free-general-troubleshooting to confirm or eliminate BPS or to isolate where the problem is occurring. Be sure to do the Custom Code troubleshooting steps. Let me know the results of doing the troubleshooting steps.
Plugin Author
AITpro
(@aitpro)
Or if the error is actually a 403 error then go to the htaccess File Editor tab page and click the Turn Off AutoLock button and unlock your root htaccess file.
Plugin Author
AITpro
(@aitpro)
Did this answer all of your questions? If so, please resolve this thread. If not, please post any additional questions you may have. Thanks.
Thread Start Date: 5-21-2015 to 5-22-2015
Current Date: 5-25-2015
Plugin Author
AITpro
(@aitpro)
Assuming all questions have been answered – thread has been resolved. If the issue/problem is not resolved or you have additional questions about this specific thread topic then you can post them at any time. We still receive email notifications when threads have been resolved.
Thread Start Date: 5-21-2015 to 5-22-2015
Thread Resolved/Current Date: 5-28-2015