Catchable Fatal Error

Some tickets that were still open were staying on page 2, despite the fact that many resolved tickets were ahead of them.

Of course, Quality Control sorts by date, as all posts do.

Considering myself clever, I “Quick Edited” the publishing dates for each of the three tickets that needed to move up to the top of page 1.

And that threw a spectacular catchable error in the loop.

But the back end was still going. I tried repairing database tables, etc., but I suspect this is some fun stuff that happens when you deal with custom post types.

The way I fixed this was to go into each ticket, and actually “edit” it, but just clicked on the “Update” button in the upper right (not changing anything else). The status was instantly changed to “Aborted,” and they were forced to the top of the list.

So, if you’re going to make a change to any ticket, do it from the main edit screen, rather than the “Quick Edit” interface.

And don’t get too freaked out about the Catchable Error – just update the post from the main edit screen.