Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Given:
1) It doesn't seem to matter where in the page the links to the microsummaries go
2) the content of the microsummary that is returned in the hook_footer is almost completely static
3) blocks can be cached (improving performance)
it would be better to implement the links to the summaries as a block instead of hook_footer.
This requires both code and documentation to explain about the install. Something like
1. Install the module in a modules/ directory
2. Enable the module
3. Enable the block in any region, but the footer might be best for browsers that use inline rendering it will slightly improve page load
4. Optionally create php formatted nodes with php that prints your own custom microsummary and then enter those node ID numbers into the box on the admin/settings/microsummary page.
Comments
Comment #1
gregglesNow fixed. Note that I didn't do it exactly like this but instead gave users the option between the default method and the block method so that it will work out of the box, but then they also have the abillity to use the block if necessary. On high traffic sites this reduces the hook_footer to a variable_get and an if.
Comment #2
gregglesComment #3
gregglesOMG - how many times can I screw this up?
Comment #4
(not verified) commented