No native URL form validation option and fails on custom regex

durangod2

Hi, I have reviewed many search results and the ones i found that offered any resolve do not work.

i have been working on adding a weburl custom field with a custom regex, the regex is good as i used it on other sites for php preg_match but i cannot get it to work for this custom field.

For the field i chose shortanswer which in the db a text field is 255 so there is plenty of room. I also checked and found that the input type (new TextboxField) is limted to 100 in class.forms.php on line 1482 so that is not an issue as this regex is well short of that.

'configuration'=>array('size'=>40, 'length'=>100),

I have tried without the beginning and ending \ , with only the beginning \ and no ^, with only the beginning \ and ^, and without any beginning or ending slash or ^ and it will not accept anything.

I have tried the following:
/^https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$/ /https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$ /^https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$ /https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$/ ^https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$

I have not been able to find anything in search to help me.. It is not giving me an error on the page, it just fails with a message in the console that says

POST https://example.com/my_tickets/scp/ajax.php/form/field-config/37 403 (Forbidden)
jquery-3.7.0.min.js?0375576:2

XHR failed loading: POST "https://example.com/my_tickets/scp/ajax.php/form/field-config/37".

However it accepts this regex no problem without error...

[\p{Lu}\p{Ll}][\p{Lu}\p{Ll}0-9.,\-_]+

but this is not what i want as it is not the right regex for this url field (it accepts too many character variations)

KevinTheJedi

durangod2

I was able to add and save the regex ^https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$ just fine in a plain-old Short Answer custom Field.

The error code/message is a bit suspicious as it's giving you 403 Forbidden. The request path regex for this specific request is here and that will match so that's not coming from the dispatcher. The dispatcher should be forwarding it to this function. You can add debug statements within that function to see if it's even being called or if the request is being denied at the webserver level. If being denied at the webserver level you'd have to contact your server administrator or hosting provider to see what's blocking it.

Update:
I was able to save all the other regex statements you provided above.

Cheers.

durangod2

I replaced the ajax.php file with one from the original download files and now i get this...

Im not sure what is going on, i have not changed any server settings or updated anything serverwise. Is there some kind of key associated with the files that is created during install?

I will try the version of the file from a backup yesterday.

ok the backup ajax.php file from yesterday got me back to the previous 403 error. If it accepts one regex with no 403 it should accept the other one with no 403 is my thinking.

Anyway thanks for all the help, i was really hoping to get this going the way i wanted but it seems it is much more difficult to mod than it was many years ago. No sure why replacing a file would cause 500, i assume there is some kind of key in the file that gets recorded during instal.

That is too much for my brain. Im gonna leave this install but im jumping over to jira to see how that is. I am not going to try bugzilla because its in perl and i hate perl. And mantis is too risky for me. So if jira does not work out ill be back. If i come back ill do a brand new install and be sure not to touch the ajax file at all...

Well that didnt take long, jira is not open source and its web based. So i guess ill do a new osticket install

durangod2

do i need the yaml ext for php? Its not on the list but i thought i would check..

Ok so everything is green...

durangod2

How about the same issue on a brand new install. My first time in the scp i added the field and used the regex
^https?:\/\/[a-z0-9-]{2,63}(\.[a-z0-9-]{2,})*(:[0-9]{0,5})?(\/|$)\S*$

and same error, that file is 0644 and so is the config file 0644

im lost 🙂

ok i added some code in that saveFieldConfiguration function like so right after the function opening

echo "<pre>"; echo $field_id; exit;

and with no regex option it gave me 36 for the field_id, however when i tried the regex as before it did not even
make it that far, so it is failing before it ever gets to that function.

I need to see what the $_POST value is, do you know what file i can do a print_r for the POST value to see it? Is it
include/class.forms.php

KevinTheJedi

durangod2

Simply inspect the request in the browser and see the request values there.

Cheers.

durangod2

Ok great thanks

Also found a different version of the regex which it did accept.

/^(https?:\/\/)?([\da-z\.-]+)\.([a-z\.]{2,6})([\/\w \.-]*)*\/?$/

so that tells me that there is some character in the other regex that the system does not like, at least that is my
best guess. Maybe during construction of the configuration field in the form field table.
Here is one that works, the one above.

{"size":"16","length":"80","validator":"regex","regex":"\/^(https?:\\\/\\\/)?([\\da-z\\.-]+)\\.([a-z\\.]{2,6})([\\\/\\w \\.-]*)*\\\/?$\/","validator-error":"URL failed validation - please enter a valid URL","placeholder":"Webpage URL"}

so there may be some char in the other regex that causes the field value construction to crash.

Anyway that is for others to figure out, im happy with calling this resolved for now... 🙂

Oh FYI, here is the source for that regex that works....

https://gist.github.com/atmason90/0bafb2aed1302f65ba507b0846023c71

KevinTheJedi

durangod2

I was able to save all of your example regex above so must be something with your server/setup.

Cheers.

KevinTheJedi

durangod2

I did notice that a couple of your examples above are incomplete (missing the trailing / character). I had to add that to the end of the ones missing it for it to compile properly.

Cheers.