I have just installed Get Simple and I love it. However, I have one problem.
After having deleted all pages in the pages-folder because I wanted to get rid of the default homepage with the advertisement (maybe not the smartest move, i know), i created a new homepage.
its url is /index, of course, this i figured out.
now i wanted to create another page for my blog. however, no matter which content i create for the blog-page, only the content of the homepage is displayed.
how can i solve this? i already tried deactivating all plugins and restarting apache.
Welcome here!
Why you do not go on like this:
delete the complete GS-installation from your Server (or is it locally?)
then install it again
these steps will take you let's say 5 or 10 minutes
then do not delete the home page but edit it! you can delete the content of that site and write anew.
If you have no success, go to administration backend / support / website health check
and tell us what you read there
also an URL would be nice
good luck!
Connie Wrote:Why you do not go on like this:
delete the complete GS-installation from your Server (or is it locally?)
then install it again
This solved the problem, thanks a lot! I edited the homepage and now it's all working properly. Should the problem occur again, I will come back here.
dej Wrote:This solved the problem, thanks a lot! I edited the homepage and now it's all working properly. Should the problem occur again, I will come back here.
That's why there is a support forum ;=)
I am glad it is working for you now!
Cheers, Connie
I've got this problem again now. The setup is default, I enabled Fancy URLs.
I left the home page as it is now, and added two other pages with a different content. When I click on them, the URL changes accordingly, but not the content.
URL:
http://d3j.de/
Health Check seems to be fine, see
http://friendpaste.com/7a95FvJLsZhziioFDF266J
Its the friendly URLs that s causing it alright.
if you go to
http://d3j.de/index.php?id=blog
you can see the pages alright.
As you say Health check is showing everything ok.
dej,
what does your .htaccess file look like? Maybe that'll give us a hint about what might be wrong.
I had a similar problem with a subtree of pages a while back, but I can't, for the life of me, remember what the problem was. Connie, do you remember what caused/fixed it?
Now I see that dej is working hard ;=)
every call of a website brings server error
@dej,
delete the .htaccess file in your root directory and upload the htaccess which comes with the installation package
@polyfragmented,
the problem there was that the SLUG was called like a existing subfolder of GS, if I remember right
there was a page "plugins", the URL had to be
www.domainname.de/plugins, but that folder exists already :=)
I forgot to mention that one, the stock .htaccess didn't work with my setup, I had used the old one from Habari CMS.
This old .htaccess, with which the problem occurs, looks like this:
Code:
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteBase /
RewriteRule . index.php [PT]
RewriteRule ^(system/(classes|handlers|locale|schema|$)) index.php [PT]
### rewritecond %{http_host} !^d3j.de [nc]
### rewriterule ^(.*)$ http://d3j.de/$1 [r=301,nc]
rewritecond %{http_host} !^d3j\.de$
rewriterule (.*) http://d3j.de/$1 [R=301,L]
I need the last line for canonical redirect.
This is the .htaccess that came with GetSimple:
Code:
AddDefaultCharset UTF-8
Options -Indexes
# blocks direct access to the XML files - they hold all the data!
<Files ~ "\.xml$">
Order allow,deny
Deny from all
Satisfy All
</Files>
<Files sitemap.xml>
Order allow,deny
Allow from all
Satisfy All
</Files>
RewriteEngine on
# Usually it RewriteBase is just '/', but
# replace it with your subdirectory path
RewriteBase **REPLACE**
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule /?([A-Za-z0-9_-]+)/?$ index.php?id=$1 [QSA,L]
I noticed the **REPLACE**, and replaced it with both '/' and '/srv/http/', which is the directory from where Apache serves, but it didn't make a difference, the output is:
Code:
Die Anfrage kann nicht beantwortet werden, da im Server ein interner Fehler aufgetreten ist. Fehlermeldung:
Die Anfrage kann nicht beantwortet werden, da im Server ein interner Fehler aufgetreten ist. Der Server ist entweder überlastet oder ein Fehler in einem CGI-Skript ist aufgetreten.
dej Wrote:I forgot to mention that one, the stock .htaccess didn't work with my setup,
Ha, this is kind of a big thing to forget to mention. Care to explain why the default .htaccess file didnt work?
ccagle8 Wrote:Care to explain why the default .htaccess file didnt work?
Well, when I set up GetSimple I rm'ed all the files in my http-directory but forgot the dotfiles, so my old .htaccess stayed there. Curiously it worked with this one, but when I replaced it with the default .htaccess, I got the server error that you see now when you visit my website.
I'll translate the error message for you:
Code:
Query could not be answered due to internal server error. The server is either under heavy load or an error occured in a CGI-Script.
An update:
The problem was indeed only with the .htaccess file. I worked around it commenting out the lines regarding blocking access to the XML files.
Now, this sure doesn't sound too good... What are the security implications of this? And is there another way of blocking access to those files? Wouldn't robots.txt suffice?
Cheers,
dej
dej,
well normally the .htaccess as it is coming with GS should fit to most hosts
if you have trouble like this please contact the supporters of your host, as there must be a special configuration which is not in our hands
but a first rule:
if you don't block the access to the xml files, you can block any access from outside to directories:
add this to your .htaccess
Code:
Options All -Indexes
this means the server will not deliver a list of files in any directory which has no index.html
if that is not possible at your host (which should be reason to change the hosting company in my optinion) you can add an empty file with the name index.html in any directory which will be loaded when somebody calls the directory in a browser
but if you have so much trouble, you should have helpful supporters at your hosting company
Cheers, Connie
it shouldn't be too bad of a problem - we already block access to the XML files other ways, this was just an added security measure.
@Connie
I host my website myself on a Linux box
So, if you are familiar with the settings that could affect the functionality of the .htaccess, I would be happy to try them. Adding the line you suggested gave me the error message again.
Maybe my versions of apache and php are too new?
dej Wrote:Maybe my versions of apache and php are too new?
so give us the info from webserver-healthcheck, please
and one stupid question: which kind of editor did you use to edit the htaccess-file?
I know from window users who edited that file in WORD and by this got a lot of rubbish into the file ;=(
dej Wrote:@Connie
I host my website myself on a Linux box
another idea: there is one solution which is very often ignored:
do make a backup of your data
delete the complete installation
install anew
add the content like described in the wiki ,
http://get-simple.info/wiki/installation:migrating