sh404SEF 4 technical requirements
sh404SEF will generally have the same technical requirements as those recommended for Joomla! itself.
Officially, we only support the current version of Joomla! in each branch that has not been yet declared "End-of-life", as per this page
Practically speaking, we haven't found any issue yet with sh404SEF running on Joomla! version
version 3.9.0 or more recent.
Please note that the full set of sh404SEF features is only supported when used on the current stable Joomla! version.
End of life notice: As Joomla! 2.5 has been "end-of-lifed" by the Joomla! project about a year ago, we stopped supporting it entirely on
December 31, 2015. We will keep the last Joomla! 2.5 version of sh404SEF available for download for an as-of-now undetermined period, but will not update it any longer nor provide any technical support for it.
In the case of multilingual sites, sh404SEF is only supported with native multilingual Joomla! website. Compatibility with 3rd-party multilingual extensions, while being seeked, cannot be guaranteed.
sh404SEF backend is tested using Isis backend template, with the following browsers:
- Chrome version 45+
- Firefox version 41+
- Microsoft Internet Explorer version 10+ (minor visual issues on IE 9+)
Latest features such as Analytics reports graph will not support Internet Explorer at all.
php_curl extension required for remote operations such as new version check, all Analytics features and some security features. GD library with Freetype font compiled for all graphic displays. This should be available by default with most hosts.
- Web Server:
nginxas per Joomla! specifications. IIS untested.
sh404SEF doesn't have any specific requirements with respect to the web server, so whatever is good for Joomla! is good for sh404SEF. Apache and Nginx are used daily, while we haven't ever tested IIS, and thus cannot provide any help with it.
You will need to setup an Apache .htaccess file or configure nginx for URL rewriting if you whish to have the simplest possible URLs on your site. However that is not a requirement for sh404SEF. It will operate nearly the same with or without URL rewriting in place.