The attached small patch outputs the TOC a a block which means that the info will be formatted consistently without any more css. yet all the classes and IDs are there to format more as needed.

CommentFileSizeAuthor
mw_1.patch916 bytesmoshe weitzman

Comments

moshe weitzman’s picture

moshe weitzman commented

I should mention that this patch is now running at http://groups.drupal.org/about (for example)

acp’s picture

acp commented

Hi there,

wow, from almost zero activity to 4, 5 issues in a day :). But that's nice, means that TOC is being used. Sorry for not replying earlier, and for not taking care of the previous (rather old now) issues.

I will take a look at them asap, that is either tonight, or in the next couple of days...

Thanks a lot for the feedback, and keep it coming ;).

Bye

acp’s picture

acp commented

Hi there,

ok so I checked your patch out but I am wondering what is the gain in doing so ? In the beginning I find that amazing because I thought it gave great liberty to the user to put the TOC wherever he wanted it to be. However while trying to implement that, I realized that:
1) I was starting to transform the filter to a block (although I admit that's not much of a problem)
2) unfortunately it's not possible, since the block hook doesn't allow to access the content of the current node.

The only gain I see is a somehow smoother integration in the output. Is this the only motivation or am I missing something ? It does however provide a way to completely configure the TOC by setting a unique ID to the block, so I will make the modification.

acp

moshe weitzman’s picture

moshe weitzman commented

yes, it is just a formatting consistency thing and initial experience improvement. this does not require hook_block at all

acp’s picture

acp commented
Status: Needs review » Fixed
Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)