?
avatar PhilETaylor
PhilETaylor
2 Feb 2017

Steps to reproduce the issue

Create a field of type URL
Set the Scheme to be https only
Set a default value that is not http:// prefixed

Expected result

Validation error on save as the default value doesnt match the validation

Actual result

screen shot 2017-02-02 at 21 52 39

avatar PhilETaylor PhilETaylor - open - 2 Feb 2017
avatar joomla-cms-bot joomla-cms-bot - change - 2 Feb 2017
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 2 Feb 2017
avatar PhilETaylor PhilETaylor - edited - 2 Feb 2017
avatar PhilETaylor PhilETaylor - edited - 2 Feb 2017
avatar Bakual
Bakual - comment - 2 Feb 2017

Default values aren't sanitised for any custom field. That is true.
It's assumed that the admin knows what he does when he sets up a new field. Similar to the extension developer when they specify a default value in the XML file (which isn't sanitised as well).

Imho if we want to sanitise those values, it would have to be done in the respective formfields, not in the custom fields plugins.

avatar PhilETaylor PhilETaylor - change - 27 Mar 2017
The description was changed
Title
[3.7.0b1] [com_fields]
[3.7.0b1] [com_fields] URL Validation of default value not happening
Status New Closed
Closed_Date 0000-00-00 00:00:00 2017-03-27 16:03:30
Closed_By PhilETaylor
avatar PhilETaylor PhilETaylor - close - 27 Mar 2017
avatar PhilETaylor
PhilETaylor - comment - 27 Mar 2017

so a "wont fix" then?

Add a Comment

Login with GitHub to post a comment