Support

Hello Peter,

As you can see in administrator/components/com_admintools/models/htmaker.php we do not use \r\n anywhere, just \n. Also if you take a minute to extract our package you will see that the line termination is \n, not \r\n\. I checked with a hex editor to be extra sure, even though I know I am using Mac OS X (with the default line terminator being \n), an IDE that is set up to use the \n line terminator and Git settings which force the line terminator to be \n. However, if you do upload the files via FTP from a Windows machine in ASCII mode then \n is converted to \r\n. That's the difference between ASCII and BINARY transfer modes, actually. Remember that the .htaccess sections are assembled from heredoc blocks in the model, ergo the line termination of the model file is transferred to these lines in .htaccess. Since you are using Windows I can guess how you ended up having \r\n line terminators and, frankly, this has nothing to do with our code.

Read what I wrote again. Slowly. Let me write the same thing again, in smaller chunks. Follow me.

The file is generated by the AdmintoolsModelHtmaker Model which lives in administrator/components/com_admintools/models/htmaker.php.

The Model is using the heredoc syntax (the <<<SOMETHING syntax).

The line endings in the heredoc block (ergo: the Model file generating the .htaccess) will of course be reflected in the .htaccess file.

I checked the model file, the path of which I already mentioned, for line endings. Its line endings are \n, NOT \r\n. As I said, I checked with a hex editor. On the very computer used to build the releases you can download from our site.

When you upload (UPload, TO the server – you thought I was talking about DOWNload even though I stated the opposite) a file (I am talking about the htmaker.php Model file) by FTP in ASCII mode from a Windows computer (like yours) the line endings do change from \n to \r\n.

Problem: You have a generated .htaccess file containing \r\n.

The only way this can happen is the Model issuing \r\n line endings in the generated file.

The only way this can happen is the Model containing \r\n line endings.

Our Model, as shipped, does NOT contain \r\n line endings, as I explained.

The only rational explanation is that you uploaded the Model file via FTP in ASCII (or AUTO) mode from your Windows computer.

This means that the Model file now contains \r\n line endings, the opposite of what we ship.

These modified (but NOT by us!) line endings end up in your .htaccess.

Therefore the issue you are reporting is not caused by our software as we ship it.