WP autolink problem on wpdevel

[Denis-de-Bernardy]

As seen here:

​http://wpdevel.wordpress.com/2011/05/05/dev-chat-summary-may-4-2011/#comment-18781

The ticket number provided within the parentheses was not auto linked to trac.

[sivel]

I'll take this. I have the plugin that is in use on wpdevel for doing this. If I can't get to it, or need help, I'll post the plugin here to get it fixed.

[Denis-de-Bernardy]

Is the plugin downloadable anywhere?

[sivel]

Replying to Denis-de-Bernardy:

Is the plugin downloadable anywhere?

As of this moment it is not.

[sivel]

Updated regex, passes all of my tests. Needs deployed to wpdevel.

[Viper007Bond]

Committed and deployed.

[Viper007Bond]

And reverted. It's linking HTML entities and needs more testing it seems. :)

[Viper007Bond]

The raw text:

I opened a ticket for the out of date browser nag (#17323).  There's a patch there, but you can't test it since the API it's supposed to work with doesn't exist yet.

That becomes this due to wptexturize and such:

I opened a ticket for the out of date browser nag (#17323).  There’s a patch there, but you can’t test it since the API it’s supposed to work with doesn’t exist yet.

The plugin is then turning those HTML entities into Trac links:

I opened a ticket for the out of date browser nag (<a href="http://core.trac.wordpress.org/ticket/17323">#17323</a>).  There&<a href="http://core.trac.wordpress.org/ticket/8217">#8217</a>;s a patch there, but you can&<a href="http://core.trac.wordpress.org/ticket/8217">#8217</a>;t test it since the API it&<a href="http://core.trac.wordpress.org/ticket/8217">#8217</a>;s supposed to work with doesn&<a href="http://core.trac.wordpress.org/ticket/8217">#8217</a>;t exist yet.

This is why it required spaces, heh.

[sivel]

I'll update the regexes to include a negative look behind later.

[sivel]

Sorry, I don't have this in version control so I cannot submit updates as patches as easily. Anyway, probably easier to post the whole thing anyway for the time being.

New version just does a negative look behind for the '&' symbol as well as 'amp;' and '38;'

I'm sure there are hundreds of other variations that could just cause more issues, but this should resolve the issues that you were seeing.

[Viper007Bond]

Tested (I forgot this step last time :P), committed, and deployed. :)