Web Address Field type - Undesired behaviour

Hello,

I'm using Joomla 3.4.1 and CB 2.0.8 and I'm seeing that when using a "Web Address" field type the following happens:

- 1) Even if I select "Any String (/.*/)" in Validation->Authorised Input, undercover validation is going on that spits "Please enter a valid URL" messages when this validation is not met. I think it should be clearer who is controlling the validation, the application (CB) or the administrator

- 2) This undercover validation accepts both strings starting with http:// and https://, however the value that is stored in the database does not include these prefixes. For example, if the user enter the value stored in the database is miweb.com. Alternatively, if the user enters the same value is stored in the database - miweb.com. Conclusion: looking at the database we don't know what the user entered and causes issues when using substitutions, using Cb Autoactions to import this value elsewhere or calling it from the Cb API

- 3) When displaying this field in the profile, CB assumes that http:// was used and builds the href link based on this assumption. Which might be wrong.

Do you see the same behaviour your end?

PS: I forgot to mention that I removed everything from "Forbidden words in user profile edits",

- 1) Even if I select "Any String (/.*/)" in Validation->Authorised Input, undercover validation is going on that spits "Please enter a valid URL" messages when this validation is not met. I think it should be clearer who is controlling the validation, the application (CB) or the administrator

Administrator validation parameters are in addition to the hardcoded validation. It still has to be a valid URL. There is no getting around that. If you want it to be whatever format you want then I recommend just using a text field.

Currently the schema is stripped and http is always used for user website urls. There's no changing this without altering the code or trying to replace the display using the layout parameters. I've added a feature ticket to change this behavior when we refactor the fieldtypes. There's not much reason to remove the schema anymore at this point.

forge.joomlapolis.com/issues/5279