Why are Pretty URLs so sticky when you migrate to a new server?
Permalink
I have so many issues with Pretty URLs over the years and I don't know why. I usually clear my cache and turn Pretty URLs off before I export the database and files. I do *not* transfer the .htaccess file or if I do, I make sure there are no rewrite rules on it.
But, for some reason, I frequently find myself in a situation where there is some PrettyURL stickiness problem happening and I play around for several hours before it magically starts working. I don't get it.
Today, I found this old solution for fixing /concrete/libraries/request.php so that your Pretty URLs aren't broken when you switch to a new server...
http://www.concrete5.org/community/forums/documentation_efforts/pre...
...but unfortunately the 'request.php' file has changed into a one-liner that merely says 'class Request extends Concrete5_Library_Request {}' so that solution will no longer work.
---
Is there something ELSE I have to do to disable Pretty URLs and make sure they are disabled 100%? If Pretty URLs are turned off and there is no .htaccess file, that is all I really need to do, right?
But, for some reason, I frequently find myself in a situation where there is some PrettyURL stickiness problem happening and I play around for several hours before it magically starts working. I don't get it.
Today, I found this old solution for fixing /concrete/libraries/request.php so that your Pretty URLs aren't broken when you switch to a new server...
http://www.concrete5.org/community/forums/documentation_efforts/pre...
...but unfortunately the 'request.php' file has changed into a one-liner that merely says 'class Request extends Concrete5_Library_Request {}' so that solution will no longer work.
---
Is there something ELSE I have to do to disable Pretty URLs and make sure they are disabled 100%? If Pretty URLs are turned off and there is no .htaccess file, that is all I really need to do, right?
