You are not logged in.
I was just about to post a question to zem regarding the problems you have already addressed. Thanks for fixing a great plugin and making it even better!
[url=http://mesothelioma-cancer-info.us]Mesothelioma Information[/url] | [url=http://weddings-r-us.com]Weddings-R-Us[/url] | [url=http://offshore-service.us]Offshore Services[/url]
I’ve installed wet’s fork of the plugin and found out that it mangles non-ASCII charachters in the
title attribute, because of the
htmlentities() function. From 4.0.2 and on,
htmlentities() should be replaced with the
escape_title() function found in the current SVN version.
Last edited by Etz Haim (2005-10-06 13:18:56)
just wanted to say thanks for this update :-)
Many, many thanks for it, i used txp for a lot of sites, but with 4.0.2 I got duplicated title permlinks all the time, and for days couldn’t solve the problem. :)) Thanks again!
Could you please add support for the
accesskey HTML attribute? Or, send me a mail to send you my modified version of zem_link that supports it?
I’ve also added the pending list mode attributes
author. Though no-one ever really requested them I enjoy to have one single authority of link creation for sites I build. zem_link to rule them all, until the final release of either txp:// or txp-Textile.
I’m having a lingering problem with zem_link. When I try to create a a link relative to the Textpattern root using
<txp:zem_link href="foo/">bar</txp:zem_link>, I end up getting a link that’s relative to the current page instead. This was a problem with Zem’s v0.3 as well. A fix for this would help me a lot, since it would fix this problem.
Also, is it possible for you to update the listing for zem_link on Textpattern Resources? If not, how about releasing it as wet_link or zem_link_reborn?
Last edited by Logoleptic (2006-05-07 22:35:31)
“Never attribute to malice that which can be adequately explained by stupidity.”
— Hanlon’s Razor
When I try to create a a link relative to the Textpattern root using
<txp:zem_link href="foo/">bar</txp:zem_link>, I end up getting a link that’s relative to the current page instead.
I will look into it and amend it when possible. At least according to the documentation, it should work as you expect.