Feature #24766
closed
External Urls - Usability of the default protocol setting
Added by Henrik Ziegenhain over 13 years ago.
Updated almost 11 years ago.
Description
If you create a new Page "external link" the default protocol is always set to http://.
In my eyes this is not optimal for usability. Editors, and btw me to :), often simply copy and page an URL from browser to the URL field don`t caring about to remove the protocol from link.
This would result in a link like this "http:// http:// www.google. com".
As we all know this link wouldn`t work and is confusing the editors.
Solution: Set "Auto" as default.
I think this would be a great enhancement for LTS.
(issue imported from #M17259)
Sorry, but it's stupidness.
I think having the http:// in place makes it more clear, that www.example.com is not sufficient.
You also have to clear or mark the contents of a page title field, before pasting a new value.
You`re right, it`s pure stupidness :)
But most editors are "stupid".
For example pasting external links into RTE works fine with and without a protocol.
So there are 2 different ways to paste links.
- Target version changed from 4.6.0 to 4.6.1
- Target version changed from 4.6.1 to 4.6.2
- Target version deleted (
4.6.2)
This doesn't has anything to do with "stupidness", but with usability. In the current implementation it's just not really usable to a customer.
Also the default link creation behavior should be without any scheme (as in: //www.example.org) which is perfectly valid as of RFC 3986: Section 4.2 and is supported by any software, that have implemented the URI syntax (well, except Typo3). The protocol will get inherited from the current document. This allows a site being called via http and https without caring about the links.
For further discussion on taht topic see for example http://stackoverflow.com/questions/550038/is-it-valid-to-replace-http-with-in-a-script-src-http
- Tracker changed from Bug to Feature
- Subject changed from external Links - bad default protocol to External Urls - Usability of the default protocol setting
- Status changed from New to Needs Feedback
Like Steffen already said a ticket inside the usability tracker would be helpful and please relate it to this one. IMHO your proposed solution looks very interesting and I never saw such stuff in the wild. :-)
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Yeb, this is stall valid in my eyes.
I opened an issue insithe the usability tracker: #50315
Ok,
so I can close this issue?
- Status changed from Needs Feedback to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by