Rebaking for automatic header anchors?

[mcdanlj]

I was very excited to see this feature:

2.7.0.beta6: Automatic Group Avatar Flair, Improved User Education Content, Bookmark Pinning, and more

New features in 2.7.0.beta6 Move site updated modal into a less obtrusive prompt As those who read these notes can attest to, Discourse is constantly receiving updates. When a site admin updates the site, end-users need to refresh their browser to take advantage of the changes. If an end-user does not do so within 24 hours of an update, they’ll receive a message prompting them to refresh. This message previously appeared as a modal, blocking the user from taking any further actions. It now app…

I upgraded Maker Forums to 2.7.0.beta6 and it looks like the HTML needs to be rebuilt for the anchors to show up in old posts, which completely makes sense. I’m guessing that this is something that I should do manually if I want to enable this throughout the site. However, I have over 400,000 posts and would like to avoid unnecessary rebaking, so posts:rebake is not my friend. I see this thread:

My journey into a massive posts rebake job

I think there’s also a ‘version’ column on the posts table that you can null out to cause gradual rebaking, too. I think it does 100 posts every time the job triggers.

Is this a good idea?

Post.where("cooked LIKE '%<h%'").update_all('baked_version = NULL')

Also, the link at the top, where I linked to #automatic-header-anchor-links shows me that oneboxing doesn’t (yet?) know about the section for discourse-internal anchor links, though it does for wikipedia anchor oneboxing (which is awesome). So I’m hoping that oneboxing can grow that soon.

[Falco]

Yes, that is pretty much what Rebake all posts matching a pattern tells you to do.