Bug #95525
closed
Field label "DB mounts" is unclear
0%
Description
The field DB mounts in users/groups is used to grant access to pages and page trees.
Thus the field should actually be named Page mounts / Web mounts or similar to actually tell what this is about. The term "DB" does not make sense for any user.
Updated by Lina Wolf over 3 years ago
I also think the name is missleading. The db mounts can however also be used for sysfolders, not just for pages to be displayed in the frontend. So maybe "page tree mounts"?
Updated by Mathias Brodala over 3 years ago
Lina Wolf wrote in #note-2:
I also think the name is missleading. The db mounts can however also be used for sysfolders, not just for pages to be displayed in the frontend.
What do you mean exactly? By default said field only allows "pages", any 3rd party customizations are up to the implementer
So maybe "page tree mounts"?
That's why I also mentioned web mounts. ;-)
Updated by Benni Mack over 3 years ago
I think we should
a) come up with proper names / proposals
b) create a list of places where the names are used (Labels, TSconfig options etc).
As for a)
I know that we have- Web mounts / DB mounts
- File mounts
And now we also have "category mounts" btw, which was added some time in 4.x.
So, I think "Page mounts" is a good naming, however "mounts" intself can be confusing with "Mount points" in terms of naming. I'm open to anything,
Updated by Riccardo De Contardi 11 months ago
ยท Edited
I think I would use "Page mounts" - it is true that also sysfolders are permitted but... sysfolders are still "pages" of a specific type - I mean that "page" is somehow a "technical term" inside TYPO3 so IMHO it "Page mounts" would be correct.
It is true that you should avoid tech jargon but...still, when you want to use a product, a bit of training about about the terminology used inside the product is always necessary IMHO
I hope I made myself clear.
Updated by Benni Mack 4 days ago
- Related to Task #106124: Change DB mount label added
Updated by Benni Mack 4 days ago
- Status changed from New to Closed
I will close this issue in favor of #106124 which is close to being merged for v14, and extends all the discussions in here.
If you feel this is the wrong decision, let me know and I will re-open the issue.