Rewrite (or prettify) URLs shows broken link error
Permalink
Upgraded to 5.4 last night. Built my first page and it works without a problem.
Added a page and checked it after publishing. Got the Google broken link page!
Turned off "pretty" URLs and the page works - albeit with index.php present.
Currently the only scripting in .htaccess is that that appears in the Pretty URLs box in Sitewide Settings.
My host passed all the prerequisites listed in setup. I got a warning in the optional area for... was it PHP safe mode?
What could be going on now?
Bob
Added a page and checked it after publishing. Got the Google broken link page!
Turned off "pretty" URLs and the page works - albeit with index.php present.
Currently the only scripting in .htaccess is that that appears in the Pretty URLs box in Sitewide Settings.
My host passed all the prerequisites listed in setup. I got a warning in the optional area for... was it PHP safe mode?
What could be going on now?
Bob
safe mode can do some pretty funky things, i would make sure that is disabled, and what is a google broken link page?
I guess it is a custom 404 that Google throws up. Safari says "No input file specified."
BTW Safe Mode is off. Not on.
i think its having problems parsing the calls made by c5
Make sure your host actually had .htaccess enabled. I just spent a while debugging a problem where the default Fedora 12 install has "AllowOverride None" by default in /etc/httpd/conf/httpd.conf. That effectively tells Apache to ignore .htaccess files. I could access my site using "index.php" URLs but not pretty URLs.
Hmmm. Interesting; so I turned into a bloodhound for this one. At the Apache site, (http://httpd.apache.org/docs/2.0/howto/htaccess.html) is:
"Make sure that you don't have a AllowOverride None in effect for the file scope in question. A good test for this is to put garbage in your .htaccess file and reload. If a server error is not generated, then you almost certainly have AllowOverride None in effect."
A server error was generated. Standard 500 Internal Error.
"If, on the other hand, you are getting server errors when trying to access documents, check your Apache error log. It will likely tell you that the directive used in your .htaccess file is not permitted. Alternately, it may tell you that you had a syntax error, which you will then need to fix."
I don't have error logs, just access logs; I see the 500 error reference, but no details. The code in the file is identical to that supplied by Concrete5 in Sitewide settings. No syntax problems that I see. I have also had Mod_rewrite configured on this host with other CMSs in the past, as late as last week, in fact.
I am going to try to repo this on an Ubuntu LAMPP sandbox I have here. Keep those cards and letters coming
"Make sure that you don't have a AllowOverride None in effect for the file scope in question. A good test for this is to put garbage in your .htaccess file and reload. If a server error is not generated, then you almost certainly have AllowOverride None in effect."
A server error was generated. Standard 500 Internal Error.
"If, on the other hand, you are getting server errors when trying to access documents, check your Apache error log. It will likely tell you that the directive used in your .htaccess file is not permitted. Alternately, it may tell you that you had a syntax error, which you will then need to fix."
I don't have error logs, just access logs; I see the 500 error reference, but no details. The code in the file is identical to that supplied by Concrete5 in Sitewide settings. No syntax problems that I see. I have also had Mod_rewrite configured on this host with other CMSs in the past, as late as last week, in fact.
I am going to try to repo this on an Ubuntu LAMPP sandbox I have here. Keep those cards and letters coming
