Thank you very much for the detective work and links for me to test with... that made it much easier to get to the bottom of it. The issue came from a code update that processed output; it seems it had issues with, I think, older content in our database.
It should be fixed now. BUT - Question for my curiosity -- when did you first see the issue show up? Just went you posted or earlier? I'm just trying to track exactly when the change got pushed out from my development server. It seems to me like it's been broken like this for close to a week? ... But the first post about it was yours yesterday... So I'm just trying to figure out what I'm missing in the timeline of the issue.
Copyright 2000 - 2026 21 x 20 Media All rights reserved. This site is property of 21 x 20 Media
All Writing.Com images are copyrighted and may not be copied / modified in any way. All other brand names & trademarks are owned by their respective companies.
Generated in 0.08 seconds at 4:08am on Jan 31, 2026 via server WEBX1.