The discussion revolves around improving the user experience when changing category image sizes in Discourse, which currently requires manual rebaking via advanced SQL commands. dylanh724 questions why a UI-friendly feature demands such technical knowledge and suggests auto-rebaking for affected images upon saving. codinghorror proposes a per-category rebake option, which techAPJ confirms is technically feasible via SQL, and agrees to consider implementing it as a low-priority feature. rishabh details SQL commands for selective rebaking (single post, topic, or category) using the PeriodicalUpdates job, which runs every 15 minutes. Later, dylanh724 reports that even after rebaking, category images remain oversized and stretched, suspecting a plugin or CSS issue. codinghorror suggests checking with the plugin author, while supermathie clarifies that category images aren’t thumbnails and recommends custom CSS adjustments, linking to a relevant thread for guidance. The core issue remains: users want automatic, targeted rebaking after UI changes — especially for category images — without needing SQL or deep technical knowledge.
What’s the point of having a friendly UI option if you have to spend 24~48 hours rebaking everything, unless you have advanced knowledge with rebake:match?
It seems like a pretty basic change to require pretty advanced knowledge to do. It doesn’t make much sense.
It’d be nice to just auto selective rebake specifically this image upon saving.
What are you suggesting? An option to rebake just a category?
A global rebake should go in order of newest posts, to oldest (I’ve lectured people about this for years, so hopefully that’s the case), thus you should see the effects on the topics you care about, e.g. the recent ones, immediately. cc @techAPJ
We have a site setting called rebake old posts count that auto rebakes ‘X’ number of un-baked posts every 15 minutes. You can set individual posts for a background rebake like this:
Running this command will simply mark the post(s) for a background rebake through the PeriodicalUpdates job that runs every 15 minutes. You could also increase the value in the site setting for a less resource-intensive periodic rebake process.
The only feature suggestion I can think of is to offer a per-category rebake. Based on the code you entered above it sounds like that is possible through SQL though?