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?