I've work a lot with the book module since D5 and have many book related projects. In doing some profiling of said projects, I came across a few obnoxiously bloated functions in the book module which could serve cached output (basically the prev, up, next links are killer). Project page says it all as to why: https://www.drupal.org/project/book_cache
module in D7 adds: - a cache bin - hijacks a template preprocess functions to use book_cache's instead of core - triggers cache bin to clear at logical points in time (node save, insert, delete w/ ->book property set, etc) - has admin_menu support to clear via that UI if requested
It being so late int he D7 cycle I probably won't even bother trying to submit a patch for core for it but if this would be something that'd receive eyes / testing / consideration for inclusion in backdrop I'll throw it directly into Backdrop's book module and issue a PR.
Recent comments
Start with clean URLs, add Pathauto and Metatag modules, submit your XML sitemap to Google Search Console, and keep your content original and well-structured.
How to Improve SEO Performance in Backdrop CMS
Check out this post re: tempstore: https://forum.backdropcms.org/forum/tempstore-table
Which database tables can I saftely empty before DB backup
Hi. I use the "[node:title] | [site:name]" tokens for the main image of news articles, blog posts, and similar publications. It's a quick and practical automatic ALT.
How to Improve SEO Performance in Backdrop CMS