Plugin Author
AITpro
(@aitpro)
Are you asking how and where to create whitelist rules/modified BPS htaccess code? If so, BPS Custom Code allows you to add/create/modify any/all BPS htaccess code and add your own personal custom code that will be combined into your htaccess files. See the Custom Code video tutorial here: http://forum.ait-pro.com/video-tutorials/
i meant warning that happen when you try to edit secure htaccess. its a 403 error asking you if you want to add this action to a whitelist. where is that list?
Plugin Author
AITpro
(@aitpro)
Post the error and/or message so I can see what you are talking about.
Plugin Author
AITpro
(@aitpro)
Adding timestamp for thread tracking purposes.
Thread Start Date: 4-30-2016
Current Date: 5-2-2016
Plugin Author
AITpro
(@aitpro)
Is the issue/problem still occurring or is it resolved? If the issue/problem is not resolved post the error and/or message so I can see what you are talking about.
Thread Start Date: 4-30-2016
Current Date: 5-3-2016
ok, I tried to do the same in two test sites and the 403 warning when you edit secure bps htaccess is not happening… i dont know what was that.
Plugin Author
AITpro
(@aitpro)
So are you saying the issue/problem is no longer occurring anymore?
yep, not happening anymore… very weird.
Plugin Author
AITpro
(@aitpro)
What exactly were you doing? I will try to test using exactly what you were using/doing. Example: I was using this BPS feature/option/setting and typing X or doing Y or clicking Z and the error message I saw was X when doing Y.
Plugin Author
AITpro
(@aitpro)
Since the issue/problem is no longer occurring anymore can this thread be resolved?
Thread Start Date: 4-30-2016
Current Date: 5-5-2016
Plugin Author
AITpro
(@aitpro)
Assuming all questions have been answered – the 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: 4-30-2016
Thread Resolved/Current Date: 5-6-2016
