Linking Additional Pages to the Home Page
Permalink 3 users found helpful
I am a first time website builder. I cannot figure out how to add the links to each of my additional pages to my home page. What am I missing here?
I have also been trying to add pages, using the method presented in the video, and the name and URL appears as expected on the parent page menu, but when I click on it I get only "No input file specified" on a white screen. The only way I can get back to the new page from the home page is by hitting the back button on the browser. Obviously, the menu link should not be producing the error, so what is going wrong, and how do I fix it?
I might also add that the "pretty" URLs do not appear in the browser URL field, only the /index.php?cID= format.
My site ishttp://pynthan.org and the new page is named "questorming".
My site ishttp://pynthan.org and the new page is named "questorming".
Hi,
I just looked at the site and it would appear that apache is not following a rewrite directive.
Did you write the changes to your .htaccess?
I just looked at the site and it would appear that apache is not following a rewrite directive.
Did you write the changes to your .htaccess?
Yes. Just to make sure I hit "Save" again and it appended all the same lines it had done before, so I had to remove the duplicates.
What else is to be done? I don't control the server.
What else is to be done? I don't control the server.
If you can't create an htacess with the relevant rewrite rules then you will have to switch pretty Urls off for the site to work.
Do you have no facility to upload files?
Do you have no facility to upload files?
I just wrote that the .htaccess file with the Dashboard-generated content was already in place. It has rw-r--r-- (644) permissions. I have ssh access.
By the way, I was attempting, perhaps too subtly, to suggest that the Dashboard Save function should test to make sure there is not already an .htaccess file before appending more lines to it.
I should add that the About, Blog, and Search buttons also yield "No input file specified", so the problem does not lie only in what I did with the new page.
If I change the name (mv) the .htaccess file the result changes to a 404 error for all of those buttons, so they didn't work on the initial installation.
If I change the name (mv) the .htaccess file the result changes to a 404 error for all of those buttons, so they didn't work on the initial installation.
oh - maybe there's some difference in versions. I'm using Concrete 5.4.1 and I've had to manually insert the lines it shows into my .htaccess file.
Which is a much better idea as I frequently have other customisations in my .htaccess.
I would check mod_rewrite is enabled and working on your server as the fact remains that concrete5 is writing the pretty urls but your webserver is not interpreting them.
Which is a much better idea as I frequently have other customisations in my .htaccess.
I would check mod_rewrite is enabled and working on your server as the fact remains that concrete5 is writing the pretty urls but your webserver is not interpreting them.
now I think about it - some years ago I did have problems with Expression Engine which wrote similar urls and that was due to PHP running as CGI...
The no file found comes from Firefox instead of the 404 error that other browsers produce on the same pages. This is due to the file not existing and CGI PHP not returning an error file.
If you look at the headers in Firefox it should correctly show you a 404.
The no file found comes from Firefox instead of the 404 error that other browsers produce on the same pages. This is due to the file not existing and CGI PHP not returning an error file.
If you look at the headers in Firefox it should correctly show you a 404.
I am running 5.4.1.1 . I have done everything suggested that seems relevant. How do I verify whether mod_rewrite is enabled? What lines have you added to .hraccess and why? How would I check to find out whether php is running as CGI?
I've run
and saved the output. It is not obvious how to interpret most of it, although it does reference cgi. Would it help to examine that file, and if so, how could I submit it for review?
<?php phpinfo(); ?>
and saved the output. It is not obvious how to interpret most of it, although it does reference cgi. Would it help to examine that file, and if so, how could I submit it for review?
Okay, I found http://www.concrete5.org/community/forums/documentation_efforts/sol... and took its advice to change
.htaccess:
concrete/libraries/request.php:
.htaccess:
# -- concrete5 urls start -- <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d #RewriteRule ^(.*)$ index.php/$1 [L] RewriteRule .* index.php/$1 [L] </IfModule> # -- concrete5 urls end --
concrete/libraries/request.php:
if (!$path) { //$path = Request::parsePathFromRequest('ORIG_PATH_INFO'); $path = Request::parsePathFromRequest('REDIRECT_URL'); }
congrats - I can see the pages are working now.
As regards your other question. I'll generally use the htaccess to do a canonical redirect from non-www domain to the www domain, (sometimes) to redirect index.php or default file back to the domain root, to set filetypes for compression, to set different filetypes for cacheing in Apache (not sure how valid this is for Conrete5 until I've tested and worked through) and redirect file location changes etc.
As regards your other question. I'll generally use the htaccess to do a canonical redirect from non-www domain to the www domain, (sometimes) to redirect index.php or default file back to the domain root, to set filetypes for compression, to set different filetypes for cacheing in Apache (not sure how valid this is for Conrete5 until I've tested and worked through) and redirect file location changes etc.
This solution worked for me too. Thanks!
Cheers,
Axel
Cheers,
Axel
http://www.concrete5.org/documentation/general-topics/add-a-page/...
-best
frz