pun_user question/advice

Just thought to check the SQL logs. It's the new get_current_url function combined with the online table which is causing the problem. The URI is too long to go in the prev_url column. (The error message wasn't displaying).

Edit: Just whilst on the subject, would there be a better way to supply the id's to the script other than in the pagination links?

I backported the prev_url setup to 1.2*, but it is with the same function & column setup as 1.3, in that regard. (I'll just double check to make sure I haven't made any changes to the basic premise, though). The prev_url column is varchar(255). A pagination link or suchlike with more than that length fails to insert due to the 255 max setting.

Oh, I bet I know what happened: you have strict mode enabled so that query failed.
I'll look into it, thanks

Well, same idea

There isn't a way to remove the limit altogether, as far as I know: I don't know PostgreSQL well enough to say for certain. You could set it to a TEXT column (or the PostgreSQL equivalent), that would likely be more than enough. And snipping the URL has the potential to break things.
We'll have to see what the fix is for 1.3, since the online table in MySQL is a HEAP table and we can't just go around adding TEXT columns there.

Well, there sort of is. From that page:

In any case, you're simply setting it to text, as I said before
That likely won't be the solution those, since, as I said, we can't just do that in MySQL for various reasons.

No problem, don't worry about it

With regard to your suggestion, it's good but it then makes things more difficult for uses of the URL where you don't want & (I don't know what the numeric entity is offhand). For example, redirecting to that URL via a 301/302 header. Also, it means storing more characters in the database. It's simpler to encode it when necessary.