Quote Originally Posted by mc12345678 View Post
Thanks for your patience, and my apologies for the mixup that I thought both $wo_last_page_url and $referer_url were being truncated, when it was only the first one that actually was and really the second one is the one more likely to be long. (internal links are not likely to be 254 characters, not to say that they can't be.)

Hopefully the "lost" data does not cause heartache, otherwise will have to implement a way to capture the entire string, probably in parts so that it can be formatted properly and then stored in the database. A thought is to split the URL up into parts short enough that if a majority of the characters needed to be escaped that the resulting string would still be parseable to add the slashes, then recombine the entire string to go into the table. Thing is at the moment, the table is setup with a finite length for the string, and therefore would either need the string length increased, or to split the referrer_url field off into it's own table so that the page load associated with referer_url can effectively have any length of string desired. (Remember, these things take up space on the server and each read/write to the database may also be counted by the host, so this all would be something of a concern, but doable.)
I wonder if changing from "varchar(256)" to "text" would work?
It would certainly sort out url length problems.
And as this is not accessed a lot, any slowdown on access would probably not be noticeable
Just thinking out loud here!