Incomplete vs complete URLs

[ccaputoParticipant]

Looking for some assistance in how the complete vs incomplete URLs work. We have many incomplete URLs which are converting properly with our custom prefix (https://www.)

We also have some URLs that are complete and the script is adding the custom prefix before those, rendering them useless.
Ex. http://www.P65Warnings.ca.gov converts to https://www.www.P65Warnings.ca.gov. How can I get it to not add the custom prefix it if is already complete? The box I am checking is to add prefix for INCOMPLETE urls.

[~~Ariel~~Participant]

Hi,

So, the question is how does Hyperlink Pro define an “incomplete” URL.
It’s a bit simplistic. Any valid path (i.e., the bit after the http:// or https://) that is not preceded by a forward slash / is considered incomplete.
So, for example, both http://www.p65warnings.ca.gov and p65warnings.ca.gov are considered incomplete.
Since you’re adding “https://www.” you get the double www bit.
As a workaround, before running Hyperlink Pro, search for all “www” and change it “/www”. That should ensure that those URLs are left alone by the script.
Afterwards, remove the / before the www. (Of course, taking care that you don’t turn http://www into http:/www).

Ariel

[Author]

Posts