link list-plugin and exit-tracking

stm999999999 · Post by **stm999999999** » Thu Jul 27, 2006 11:40 pm

The links in the plugin "link list" are not infected by the Serendipity Exit-Tracking Routine

It would be nice to track these links, too.

mgroeninger · Post by **mgroeninger** » Fri Jul 28, 2006 3:17 am

This might be simple or difficult. If Garvin can recommend a simple way to call the track exits plugin on the finished html data from linklist (like an event hook or even a function) before it is output, that would be simple (though it will slow down the page).

If there is no way to do that, I think it would be pretty difficult to apply the markup to the linklist plugin.

I'd like to see if Garvin weighs in before I look any further into this.

Post by **garvinhicking** » Fri Jul 28, 2006 1:30 pm

Hi!

Yes, you would need to call the 'Frontend_display' hook on the data which you previously need to wrap in en $entry['body'] function.

The question would be how to treat those links. As "entry body", "extended body", "comment body", "staticpage" or "html nugget". As you know, each markup plugin would then be executed here and depending on which plugin is enabled for which "block", this would produce different output.

I think "html nugget" comes closest to this. So if Track Exits is enabled for HTML Nuggets, this should work then.

Thoughts?

Best regards,
Garvin

stm999999999 · Post by **stm999999999** » Fri Jul 28, 2006 1:59 pm

Sounds good.

But, then there should be a config option in the link-list-plugin like in the page_entrylinks DO_MARKUP_DESCRIPTION

mgroeninger · Post by **mgroeninger** » Sat Jul 29, 2006 3:52 am

Cool... I should have a chance to play with this this weekend. I agree that the "HTML Nugget" type makes the most sense for the linklist processing...

And I will add an option to linklist so that the processing is optional.

mgroeninger · Post by **mgroeninger** » Mon Jul 31, 2006 6:46 pm

Ok, version 1.13 of the plugin has a configuration option (when you are output with either CSS List or Plain CSS) to enable markup. All the markup which is enabled for HTML Nugget will be applied. It seemd to work on my beta install, but please let me know if you have any problems with it.