It would be nice if we could set a "weight" for the footnotes section so that it did not necessarily go directly under the content of the node.

My main reason for this is that I am using the Diggthis module and want to place the Digg button below my article text but above the footnotes section. The Diggthis module has a weighting system in it that allows you to weight where it renders on the page; if the footnotes module used the same system it uses, then I could simply set the weight and all would be well :)

I am not sure how complex this is, but it seems like it adds a decent measure of flexibility to the module. Well, that is assuming other modules have a weighting system that interoperates with Diggthis' system - though I imagine it must be using some standard functionality or else even adding the weighting system to that module would have been pointless.

Thanks for the consideration,
Nick

Comments

beginner’s picture

beginner commented

It seems like a reasonable request.
If someone provides a patch, I'll review it thoroughly.

hingo’s picture

hingo commented

This is an interesting suggestion. (First time since the creation of Footnotes that I'm positive towards a request to add something that can be configured. As of yet Footnotes has no configuration page of itself :-)

However, there is a little problem. Footnotes is a filter module. This means it manipulates the main content - the text of a story/node. Diggthis however is not a filter, it is one of those modules that inserts "decorations" upon a node using nodeapi at the time the page is viewed. (The comments system, the "Read more" links and such are other examples of modules using nodeapi.) Footnotes must be a filter - ie work through the filter api - since it introduces it's own tags and manipulates the text of a node.

As I see it, unfortunately there is no easy way to make these interoperate nicely. It would require some serious hacking on Footnotes.

hingo’s picture

hingo commented
Status: Active » Closed (won't fix)

Closing. Suggested idea is not implementable for a filter.