If we don't want to use SEF urls to avoid 301 redirect to index.php, how should we change the rules for joomla to work fine ?
I am not sure what you are asking. If you don't want to use SEF URLs with Joomla! there is nothing you need to do.
It seems that the piece of block redirecting the index.php has some side effects on other components.
If you mean what I think you mean just set "Force index.php parsing before index.html" to No and "Disable directory listings" to No. Please note that this will BREAK the expected behaviour of seeing Joomla! when you type the URL to the root of the site or the administrator page, i.e.
http://www.example.com -- will NOT work (you will see the listing of files in the directory or a blank page)
http://www.example.com/index.php -- works
http://www.example.com/administrator -- will NOT work (you will see the listing of files in the directory or a blank page)
http://www.example.com/administrator/index.php -- works
For what it's worth the line added in the NginX config (index index.php index.html index.htm;) is the standard and recommended way to tell NginX to serve PHP applications.
Further, if we include a secret key word for access to administrator folder, the nginx maker does not seem to take it into account.
If you
REALLY mean the secret URL parameter, the NginX Maker has nothing to do with it. The administrator secret URL parameter is enforced by PHP code.
If you actually mean the Password Protect Administrator feature we explicitly state that it only works on Apache as it's based on .htaccess and .htpasswd files. We don't even show you this feature when you run under NginX for this reason. If you want, you can implement it manually following this guide: https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-nginx-on-ubuntu-14-04
No, we won't automate that because you would still need to edit your NginX configuration (and know
where to edit it), something which cannot be automated for several technical reasons. That would make such a feature completely useless. There's no point just creating a .htpasswd file for you and having you do the difficult part of the process by hand.
And finally, there is a glitch in the maker when selecting the symlinks option (a single carriage return ;-) )
Thank you! The missing carriage return will be present in the next version of Admin Tools scheduled for tomorrow or the day after.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!