Excitement

Solution: include code that writes/unwrites these values into the config file on the fly as needed. This still involves core-editing, but the right code in the theme (or plugin) easily ensures that the config file is fixed up immediately after updating the core, so at least the end-user isn’t mucking around with core files.

Correction: this was the thread I saw you on. 🙂

http://wordpress.org/support/topic/wordpress-34-broke-my-paginaton-setup?replies=4

Thanks for the heads up, aljuk. I’ve found a handful of posts on this as well and, to follow up with esmi, my server logs showed nothing out of the ordinary. So yea, this thread isn’t actually resolved after all.

My guess regarding the non-existent flood of posts here is that nobody is going to notice the problem until/unless they go back and look at a paginated post of a custom post type (and carefully) — if they even updated to 3.4.1. I don’t use any pagination on the front page, so I haven’t seen the problem there myself.

For some reason, the first <–nextpage–> tag found in a post is being converted into entities. Resaving the post seems to work, but that’s only a viable solution for sites with very few posts. Wish I had more time to sort it out, but my schedule calls the shots, so I’m just going to revert versions; 3.4 didn’t seem to have any issues with CPT paging.

I don’t dare get too distracted by it at the moment, but I’ll be curious to take a look.

Thanks. I suspect you’re right about that, though it’s only been out for a very short time. Since I’ve been using the same theme and plugins all along, and the error only occurred after updating to 3.4.1 minutes ago, I suspect it’s in there somewhere.

It’s definitely a weird behavior… when I now re-edit the post, it’s showing all the nextpage tags as intended (in the source editor), but when it’s rendered as a post, the first tag is rendered onscreen while the subsequent nextpage tags (in the same post) work. Because the others are working and it’s just the first tag affected, I copy and pasted one of the ones from below in the post, to ensure it wasn’t a typo I was glazing over. 😉