Feature #5369
closedURL's - with or without protocol?
0%
Description
This is a general inconsistency issue throughout the backend.
Two examples when adding domain records
The "Domain" must not contain "http://" whereas the "Redirect to" record must have "http://". Leaving it in, or leaving it out in the wrong place, yields an error - and there's no help or label text that explains what I should do.
A third variant of entering URLs, is when creating a Page as an "External" URL. There I get a drop down box, where I select the protocol, but I will more than likely have the URL I wish to use in my clipboard, and I will then paste that complete URL into "URL" - and that will also give me erroneous behavior - most likely because of doubled http://http://mydomain.com
A fourth variant of the inconsistency is when adding a link to text (with RTE). Here the protocol is prewritten for me:
Files
Updated by Jens Hoffmann over 10 years ago
- Status changed from New to Accepted
- Target version set to TYPO3 6.2 LTS
Fine for me.
Updated by Jens Hoffmann over 10 years ago
We decided to drop the Protocol selector, as the "Auto" works fine for all given Protocols.
Updated by Benni Mack over 7 years ago
- Project changed from 78 to TYPO3 Core
- Category changed from Inconsistency to Backend User Interface
Updated by Riccardo De Contardi about 7 years ago
- Target version deleted (
TYPO3 6.2 LTS)
Updated by Riccardo De Contardi over 6 years ago
In 9.0.0-dev latest master the ""External" URL" pages have lost the protocol field; the remaining observations made here are still valid.
Updated by Benni Mack almost 6 years ago
- Status changed from Accepted to Closed
we're going with "always stick to the protocol". We resolved the External URL dropdown, we also have the protocol as a must-have, and we are going to kick out sys_domain in v10 (which will be the final straw).
Mainly due to consistency in APIs and UX, but also to have full transparency of any new protocols, ports etc.