install 3.7.0b1
create Url(Url) custom field
Set scheme to be http://
edit content on FRONTEND
attempt to bypass validation
http:// this is & not & a VALID url
should not be saveable and should error
http:// this is & not & a VALID url
saves as a valid url and is hyperlinked on rendering
If there is no validation on the URL then this custom field type is nothing more than a text field with "validate the first few char" and not a URL field!!! Either name it correctly or implement correct validation of the input !
Labels |
Added:
?
|
Actually - if you are going to provide a URL field - it MUST validate as a url else whats the point. So it is related to com_fields in that respect.
The only thing that makes a URL field different to a TEXT field, is that is SHOULD only accept a URL, effectively it should be a TEXT field with validation.... At the moment that is not being done so a URL field is only as good as a TEXT field
So is the correct course of action to remove the URL field type completely - losing yet another new feature?
or fix the fact that validation has been broken for years?
Category | ⇒ | com_fields |
Category | com_fields | ⇒ | com_content com_fields |
Status | New | ⇒ | Needs Review |
set Staus on "Needs Review" on issue Tracker.
Title |
|
Labels |
Added:
J3 Issue
|
Title |
|
Status | Needs Review | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-02-10 21:35:06 |
Closed_By | ⇒ | PhilETaylor |
That is actually not related to com_fields as the same happens when you enter it into the link fields in an article. So I think the JFormFieldUrl itself would need to be fixed here.