I have a website that's only active during the summer each year. Every page after the home page is recognized by a string uuid=23ebb******1a3e
This year, however, it strangely stopped working, and pages with uuid= are being flagged as HTTP Error 404.0 - Not Found.
I don't understand why this year is causing problems, given that I haven't changed anything.
It's been years, and I don't remember how I configured this uuid to work.
Perhaps something changed with the updates.
How can I reactivate it without causing a disaster?
If you have not changed anything, my bet is that the host updated Apache or changed the vhost config causing .htaccess to be ignored. That would instantly break UUID routing while leaving the home page intact.
Nothing has changed, but the strange thing is that the use of multiple pages linked together with UUID in the project is used twice in separate contexts.
Everything works in one of the two procedures, but not in the other.
Thanks Ben
After several attempts, I discovered that the problem isn't a UUID, but rather simply an incorrect page address.
A part of the correct address is missing.
I don't understand why, since nothing has changed since last year. I'm trying to figure it out.
1 Like