Hi

Just finished creating my first extension based on this thread.

The latest version including a short documentation can be found here:

URL Field Extension for Expressionengine

I really love EE, don’t get me wrong, but one thing i have to rant about is the missing API for developers. Hooks and all are nice, but if you have use preg_replace so many parts of HTML code to build-in your functionality the happyness stops. I just hope EE 2.0 will correct this and provide a better API for developers.

Peter,

Let me be the first to say a very big well done on this one. A fantastic little extension that does exactly what it says on the tin and then some!!

Brilliant addition to ExpressionEngine. Thanks again!

Best wishes,

Mark

Peter,

Great work.  I just posted a request for this last week, and here it is!  Bravo.

Ben

This might be totally missing the point of your extension, but would it be possible to add an option to remove the formatting that is produced through this field type? I wanted to do something like this:

I know this can be done with a standard text field, but I think the validation check is a good idea. I’ll be having some more novice computer users updating the site, so it would be great if the validation check can give them a sense of pattern for publishing.

Cheers!

Hi

I’m not aware of any formatting issues? You can chose the url_field (as any other field type) not to have any formatting.

If I type “http://www.example.com” in the url_field, the url is returned exactly as is.

That’s odd.. I’m not getting the same results. When I try and edit the formatting for the URL Field, it basically says that “Text formatting is not available for your chosen field type”.

When I plug in {source} into a template, which is the name of my URL field, I get this outputted:

Seems formatting is done automatically, so I can’t specify a name for the link. Ideas are appreciated.

Try going to :

Admin->Weblog Administration->Weblog Management->Edit Preferences (Your Weblog Name)->Weblog Posting Preferences->

You should see an option that says :

Automatically turn URLs and email addresses into links?

Change that to No and see if that fixes it?

Best wishes,

Mark

Thanks Mark, faster as usual

That should chang the behaviour indeed mr_dimsum, please report back if not.

one question/bug/feature request… it seems that it only validates the field when you click the little icon. I was assuming that it would check it on a submission. I can’t assume that my users will actually remember to push the link button every time. I want to be sure they have a correctly formed url even if they don’t remember to push the icon button.

Also, I noticed that it doesn’t see https:// as a valid url link.

Hi

Thanks for getting back to us, we’re aware of the fact that this functionality is not included in the current release, but we’ll incorporate it for the next one.

Currently, we’ve our hands pretty full with client work, as soon as it gets better, we’re release a new version along with an entire new extension (something cool for freeform .

Regards
Peter.

can’t wait for the new updates! right now i can’t really use the extension, because I need the https:// support.

Hi James

You can update to the latest version which fixed the https:// issue as well as the formatting issue, read the comments on our blog on how to fix the formatting.

We also have plans to add CURL checking of URLs so that upon entry submission, the extension would check using CURL is the header response returned from the URL is valid and thus the url itself. This should be more effective than using just a regular expression. Hopefully we’ll be able to release another update addressing this issue.

peschehimself - 31 October 2008 03:07 PM

We also have plans to add CURL checking of URLs so that upon entry submission, the extension would check using CURL is the header response returned from the URL is valid and thus the url itself.

Hi Peschehimself—thanks for all your work on this. Would it be possible to make curl checking optional (a settings checkbox or something…)?

Thanks,
Matt

Hi Matt

Yes, of course, the CURL will a have a separate settings value, but it will most probably be a global settings instead of a per weblog setting.