Liste der autorisierten Erweiterungen mit nicht-standardisierten Erweiterungsnamen

I run a forum supporting open source software called KiCad. After a recent upgrade, some of the file extensions that users often upload are no longer working. There is a thread about it here:

The thing I am keying in on is that it’s only the extensions that have underscores in them. I hadn’t seen any file extensions like that before KiCad, but it’s a large part of the file extensions that are part of the software. The board files have an extension of “.kicad_pcb” and the footprint files are “kicad_mod”.

I have all of the files listed in the “authorized extensions”, as well as the asterisk, in hopes of getting this working. I tried searching through the git repo as well, but couldn’t find any restrictions on the extension type (though it doesn’t mean that’s not the case).

So only the ones with underscores are broken?

Yes, that’s correct.

I hadn’t thought to try it on another instance I have, just to make sure.

I just enabled the same extension (“kicad_mod”) and the upload works fine. However, it has the same behavior and when you click on the file link in the post, it goes to the default page that says “Oops! That page doesn’t exist or is private.”.

Is it possible this is more about the links that are created, rather than the actual upload? Are underscores allowed?

For instance, the link I just created was “/uploads/short-url/913bC7GjTf4cxyYtkr1Ej67ngER.kicad_mod”

For reference, I am using an S3 instance for storage Just double checked on the test instance and it’s using local storage.

Thanks for the report. I will check the issue next week.

This is another example by a forum user
https://forum.kicad.info/uploads/short-url/kkB1iEtT2JAEbNFZP4YclKPmgbC.kicad_pcb, who thought his upload had worked
An underscore again. The users are NOT trying to use Unicode characters.

Jetzt ist es durch den folgenden Commit behoben:

Gibt es eine Möglichkeit, benachrichtigt zu werden, wenn dies in einem Beta-Build enthalten ist?

Gerade auf unserer lokalen Installation getestet und es funktioniert einwandfrei. Vielen Dank für das Update!