#5603 - Allow full stops in codename field

By Adam Edington
Added 9th Feb 2024, 8:51 PM
1 view

Identifier	#5603
Issue type	Feature request or suggestion
Title	Allow full stops in codename field
Status	Closed (rejected)
Handling member	Deleted
Version	10.0.45
Addon	General / Uncategorised
Description	Currently we are limited to underscores and perhaps hyphens I have created pages such as "numento.fi.txt" which work as intended on the frontend but they cannot be edited via Composr due to the period (as you Americans like to call it).
Steps to reproduce
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 9th Feb 2024, 9:07 PM

It is highly unlikely I will implement this.

There are reasons why Composr normally would not allow full stops. There could be confusions with file extensions. It could confuse URLs / permalinks as well. And there are several ways this could end up getting abused on the security front (such as creating pages with a double full stop to try a directory traversal attack).

By Guest posted 10th Feb 2024, 2:38 PM

Patrick is correct. Codenames are intentionally limited to not contain anything that is likely to be syntax in some other 'language'.
Comcode pages can have monikers, so arbitrary URLs can be achieved. For actual filenames, dashes could be used (for example) rather than dots.

By Guest posted 10th Feb 2024, 2:49 PM

Fair enough. I don't plan to use monikers, meta tags or anything else that is available via edit on these pages I just found it strange I couldn't edit them via Composr due to the . being present. They are inlet/landing pages and I wanted to include the country 2 letter ISO code in case bands share the same name. numento-fi.txt would work if I wanted to edit them but I think I will just hand edit these pages as they do seem to work fine. Thanks :)