I suggested Brian get rid of the foreign key integrity checks in portal_table_page_map temporarily, as a hackaround, and that led him to another bug, a trigger that didn't return a value.
I fixed and commited that. The trigger's on a portal table but it's in the education module, grrr...I'm going to report that as a bug as it's a GENERAL trigger that affects all users of the portal tables. There are several of these. Classic aD snafu (though the specific trigger error was a PG port snafu).
They belong in the portals module, and I've got to wonder if they don't break the portals module in some way. Just wondering, since the perp was obviously myoptically focused on the education module at the time and there's no guarantee s/h/it thoroughly tested the portals module afterwards.
