Support

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

Apologies if someone has already reported this.

There is a new option in Admin Tools but the language string is not loaded. Neither are any of the language strings in the dropdown next to it.
COM_ADMINTOOLS_LBL_HTACCESSMAKER_REFERRERPOLICY

Also I found that these files were blocked by admin tools:
https://www.ivelgroup.com/android-icon-192x192.png
https://www.ivelgroup.com/favicon-16x16.png
https://www.ivelgroup.com/favicon-32x32.png
https://www.ivelgroup.com/favicon-96x96.png
https://www.ivelgroup.com/favicon.ico

I have unblocked them but I was a bit confused as to why they would be blocked in the first place. I know png could possibly be a security threat but these files all came from the site https://www.favicon-generator.org/ and I dare say they are fairly common.

I was not able to find an answer on the language string. I'll ask Nicholas for his assistance in the morning.

Recent versions of Admin Tools take a much stricter stance concerning individual files than previous versions did. If the png files had been in /images or /media (and png was an allowed file type), they would have been fine. You needed to do the exception because they were in the root of the site.

Hmm interesting, but there are several pngs in the root of the site and they weren't all banned for some reason. Could it be x96 is some sort of a code which could be used in hackery somewhere?

E.g. this one wasn't blocked ms-icon-70x70.png

I'm pretty sure I've seen some scripts where they have lots of repeating x's and numbers. I can't for the life of me remember what they are called but they obfuscate the code nicely. I'm not sure that was the original point but that's how it comes across to me.

And Nicholas told me separately that the language string should have been "COM_ADMINTOOLS_LBL_HTACCESSMAKER_REFERERPOLICY" (one R). While that is incorrect in terms of proper English spelling, it is correct in terms of the RFC that defines the language strings. In this case, the dictionary loses. Nicholas has fixed the affected code and you will see the correction in the next release.

Thank you.

And yes Nicholas, I think it is for Progressive Web Apps or saving shortcuts on your phone. But possibly also the reason you suggested too. It seems odd that one was blocked and not the other, but I can handle that with a simple exception in my .htaccess maker.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.