Hello! I have a strange problem. Generally site works well, but when I'm installing any language extension and trying to switch on (or edit) it in System>Localization>Language the site shows 404 error. Please, help. I appreciate for any suggestions.
P.S.
Also 404 arises when I'm trying to add new language in System>Localization>Language
Adding and editing currencies are working fine.
If it helps: Site is whitelabeled and goes under SSL and redirected from http to https via htaccess
Hello.
Please check your error log just after you got an error
Hello!
Thank you for the quick respond, the matter is that no errors highlighted in the errors log, just when I press "+" button in "System>Localization>Language" I'm getting 404 error.
This page shows 404
/index.php?rt=localisation/language/insert&s=xxxxxxxx&token=xxxxxxxx
And this page is ok
/index.php?rt=localisation/currency/insert&s=xxxxxxxx&token=xxxxxxxx
Hello
Try http://docs.abantecart.com/pages/tips/troubleshooting.html#mod_security
Yes, I tried, but the result is the same.
Have you any idea why it happens? I tried to switch off the https, tried to disable mod_security. Seems this is a core bug or something else. Any way I'm very sad with the fact that I can't add a new language to the site.
Most of hosting do not allow you to disable mod_secure. Are you sure you disable it?
Did you check file permissions? Are the accessible?
index.php is 644, I tried 755 - the same result
I included the following directive in htaccess and nothing changed
<IfModule mod_security.c>
SecFilterInheritance Off
</IfModule>
If you add this does not mean it work. Most of hostings limit users with .htaccess and php.ini commands
So, you advise to ask hosting provider to disable mod_security? Ok, I'll try, not sure that this will help, but thank you.
Problem not in disable or enable mod_secure. Usually hosting administrator should configure it correctly ;)
Can you please write the correct configuration for mod_security, so I'll be able to ask provider to configure it properly. Thank you.
SOLVED, thank you! The matter was exactly in the apache's mod_security, it must be switched off via CPanel and not htaccess.