Support

I am not sure why you had to edit the ticket. The attachment is not stored with its original filename on your site. We use a long, random filename without an extension for security reasons. The original filename of the attachment is stored in the database only to provide a hint to the browser when you're downloading the file. If the filename contains invalid characters for the operating system you are downloading it to either the browser offers an alternative or you get an error – but the browser in this case does let you change the location and name of the downloaded file.

That is to say, if I upload a file called "Foo$bar:13.png" (a valid filename on Linux and definitely invalid on Windows) most browsers on Windows would propose to download it as something similar to "Foo_bar_13.png" or ask me where and under what name to store the file.

In any case, the name of the file is NOT used on your server EVER. That would be a massive security issue.

Can you please explain your use case a bit better?

I can tell you with ABSOLUTE certainty that a random filename is being used. I was refactoring the attachments code ten days ago. The entire architecture of attachment is very solid in my working memory right now. You can verify it by looking in the media/com_ats/attachments folder. See all those funny looking filenames in there? Yup. These are your attachments, not garbage. The mapping between real files and these "mangled" filenames is in your database, in the #__ats_attachments table.

Also, the name of the file you are trying to attach is absolutely valid on Linux. Linux is very permissive with regards to filenames. You can use pretty much anything except a null byte! It's Windows that has a bazillion restrictions about filenames.

You misdiagnosed your problem. Your problem is very different and has actually nothing to do with Akeeba Ticket System itself. That's why I asked you to explain your use case.

All attachments are uploaded using Joomla's core API for file uploads. By default, Joomla applies various security checks against the uploaded files. One of the checks is "does the filename of the uploaded file, as reported by the browser, contain more than one dots?". If it does, it's automatically rejected. When Joomla rejects the upload for security reasons –for ANY of its security checks, not just the multiple dots– ATS does not attach the file.

Your filename is Groupe Pac air-eau ext..pdf See the two dots before pdf? That's what triggered Joomla's upload security and caused your file to be rejected.

When you renamed the file to shema.pdf you fixed the double dot issue and the upload worked.

Your problem, therefore, has nothing to do with ATS. It's just Joomla's file upload security being triggered :)

You can't add a file to an existing post. You send a new post with the attachment(s) you forgot to upload the first time around. This is not going to change anytime soon for complex technical reasons.