second URL
second URL
Hi!
You can make serendipity listen to multiple domains, but not multiple directory names.
You can run s9y on www.lowicki.de/s9y and www.netzomane.de/s9y, or www.lowicki.de/ and www.netzomane.de/ - but not mixed once with / and once with /s9y.
Regards,
Garvin
You can make serendipity listen to multiple domains, but not multiple directory names.
You can run s9y on www.lowicki.de/s9y and www.netzomane.de/s9y, or www.lowicki.de/ and www.netzomane.de/ - but not mixed once with / and once with /s9y.
Regards,
Garvin
Re: second URL
strange .. where has my question gone? I see the answer but it looks like you edited my request since I am the author ?!?!?!? Never had this before.
Will multiple domains work with the lite version?
br
Daniello
Will multiple domains work with the lite version?
br
Daniello
Re: second URL
Shouldn't matter. As far as I understand Garvins reply out of context, it doesn't require a shared installation, and it definitely doesn't require extra templates. That's the whole difference of LITE vs. FULL.daniello wrote:Will multiple domains work with the lite version?
YL
Re: second URL
the next big question is: Is it possible to lift the current installation to / without reinstalling? At the end of the day I want to run it under www.lowicki.de. Or must I stop now and start from scratch?
There's no content yet .. I just spent hours on fiddling around with the layout (I know .. it's not spectacular .. but I am not a programmer
br
Daniello
There's no content yet .. I just spent hours on fiddling around with the layout (I know .. it's not spectacular .. but I am not a programmer
br
Daniello
-
- Regular
- Posts: 3652
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
Re: second URL
You can move everything up one level to the web root, but you will need to reconfigure s9y, and may also need to reconfigure certain plugins. If you feel that is too much of a hassle, you can always reinstall.
=Don=
Re: second URL
>you can always reinstall.
Is this "start from scratch" by deleting everything and copying all original files back to the server? Or is there a way to copy what I have and then run the installer of that (to possibly keep something)?
I do remember having quite some problems after copying from root to /s9y .. I couldn't run the configuration or anything (I think the .htaccess file was the culprit).
br
Daniel
Is this "start from scratch" by deleting everything and copying all original files back to the server? Or is there a way to copy what I have and then run the installer of that (to possibly keep something)?
I do remember having quite some problems after copying from root to /s9y .. I couldn't run the configuration or anything (I think the .htaccess file was the culprit).
br
Daniel
-
- Regular
- Posts: 3652
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
Re: second URL
It has been a REALLY long time since I have moved an installation from a folder to the web root... however, if I was going to do it today, I would
If it was still a complete failure, I would delete the file serendipity_config_local.inc.php, then hit the site which should trigger reinstallation.
Again, I have not done this in a very long time, and only did it a couple of times.
- Move everything up one folder level.
- hit /yoursite.com/serendipity_admin.php.
- Check/change all the paths as required.
- Save the configuration.
- Check each plugin for potential path modifications.
If it was still a complete failure, I would delete the file serendipity_config_local.inc.php, then hit the site which should trigger reinstallation.
Again, I have not done this in a very long time, and only did it a couple of times.
=Don=
Re: second URL
Thanks .. sounds very helpful. Gives me a great starting point.
Daniello
Daniello
Re: second URL
If you had existing entries, you'd want to get a database dump and change all the paths to point at the root instead of the subdirectory. Since the database dump is plain text, this can be done with any decent editor.
As a side-effect, the plugin configuration also changes all its paths, since that data is also stored in the database.
The only other place incorrect paths could exist would be .htaccess and the config_local.inc.php.
As a side-effect, the plugin configuration also changes all its paths, since that data is also stored in the database.
The only other place incorrect paths could exist would be .htaccess and the config_local.inc.php.
-
- Regular
- Posts: 3652
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
Re: second URL
I don't think serendipity_config_local.inc.php has any path info.....judebert wrote:The only other place incorrect paths could exist would be .htaccess and the config_local.inc.php.
=Don=
Re: second URL
oh my .. I tried but I didn't manage. Every time I selected a konfiguration item I was sent back to the login page. I had this earlier .. but after enabling session cookies it was gone. This time it persited.
I'll live with /s9y/ being my root folder for my blogsite. The redirect from http://www.lowicki.de is working fine so it's not that bad .. helping to keep my root a bit tidy.
But I do have another problem that I need to address.
I have a folder "www.lowicki.de/bla" that I need to access directly without getting a foward to the the blogpage. I searched the web for modwrite exceptions .. but I don't manage to get it right. In fact there are quite a few folders that I'd like to address directly.
Could anyone please give me a hint on how to exclude that directory so that it simply displays the index.htm in there ?
below .. pls find my .htacess which is the only file currently resindig in my root directory.
br
Daniello
I'll live with /s9y/ being my root folder for my blogsite. The redirect from http://www.lowicki.de is working fine so it's not that bad .. helping to keep my root a bit tidy.
But I do have another problem that I need to address.
I have a folder "www.lowicki.de/bla" that I need to access directly without getting a foward to the the blogpage. I searched the web for modwrite exceptions .. but I don't manage to get it right. In fact there are quite a few folders that I'd like to address directly.
Could anyone please give me a hint on how to exclude that directory so that it simply displays the index.htm in there ?
below .. pls find my .htacess which is the only file currently resindig in my root directory.
br
Daniello
Code: Select all
# BEGIN s9y
ErrorDocument 404 /s9y/index.php
DirectoryIndex /s9y/index.php
php_value session.use_trans_sid 0
php_value register_globals off
php_value session.use_cookies On
redirect 301 /cv.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /cv2.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /cv3.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /cv4.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /partner.htm http://www.lowicki.de/index.php
redirect 301 /artikel.htm http://www.lowicki.de/s9y/pages/fachartikel.html
redirect 301 /artikel2.htm http://www.lowicki.de/s9y/pages/fachartikel.html
redirect 301 /artikel3.htm http://www.lowicki.de/s9y/pages/fachartikel.html
redirect 301 /kontakt.htm http://www.lowicki.de/s9y/pages/contactform.html
redirect 301 /weiterbildung.htm http://www.lowicki/index.php
redirect 301 /fresh.htm http://www.lowicki.de/index.php
redirect 301 /index.htm http://www.lowicki.de/index.php
redirect 301 /index.html http://www.lowicki.de/index.php
RewriteEngine On
RewriteBase /s9y/
RewriteRule ^serendipity_admin.php serendipity_admin.php [NC,L,QSA]
RewriteRule ^((archives/([0-9]+)-[0-9a-z\.\_!;,\+\-\%]+\.html)/?) index.php?/$1 [NC,L,QSA]
RewriteRule ^(authors/([0-9]+)-[0-9a-z\.\_!;,\+\-\%]+) index.php?/$1 [NC,L,QSA]
RewriteRule ^(feeds/categories/([0-9;]+)-[0-9a-z\.\_!;,\+\-\%]+\.rss) index.php?/$1 [NC,L,QSA]
RewriteRule ^(feeds/authors/([0-9]+)-[0-9a-z\.\_!;,\+\-\%]+\.rss) index.php?/$1 [NC,L,QSA]
RewriteRule ^(categories/([0-9;]+)-[0-9a-z\.\_!;,\+\-\%]+) index.php?/$1 [NC,L,QSA]
RewriteRule ^archives([/A-Za-z0-9]+)\.html index.php?url=/archives/$1.html [NC,L,QSA]
RewriteRule ^([0-9]+)[_\-][0-9a-z_\-]*\.html index.php?url=$1-article.html [L,NC,QSA]
RewriteRule ^feeds/(.*) index.php?url=/feeds/$1 [L,QSA]
RewriteRule ^unsubscribe/(.*)/([0-9]+) index.php?url=/unsubscribe/$1/$2 [L,QSA]
RewriteRule ^approve/(.*)/(.*)/([0-9]+) index.php?url=approve/$1/$2/$3 [L,QSA]
RewriteRule ^delete/(.*)/(.*)/([0-9]+) index.php?url=delete/$1/$2/$3 [L,QSA]
RewriteRule ^(admin|entries)(/.+)? index.php?url=admin/ [L,QSA]
RewriteRule ^archive/? index.php?url=/archive [L,QSA]
RewriteRule ^(index|atom[0-9]*|rss|b2rss|b2rdf).(rss|rdf|rss2|xml) rss.php?file=$1&ext=$2
RewriteRule ^(plugin|plugin)/(.*) index.php?url=$1/$2 [L,QSA]
RewriteRule ^search/(.*) index.php?url=/search/$1 [L,QSA]
RewriteRule ^comments/(.*) index.php?url=/comments/$1 [L,QSA]
RewriteRule ^(serendipity\.css|serendipity_admin\.css) index.php?url=/$1 [L,QSA]
RewriteRule ^index\.(html?|php.+) index.php?url=index.html [L,QSA]
RewriteRule ^htmlarea/(.*) htmlarea/$1 [L,QSA]
#RewriteCond %{REQUEST_URI} !-U
RewriteRule (.*\.html?) index.php?url=/$1 [L,QSA]
<Files *.tpl.php>
deny from all
</Files>
<Files *.tpl>
deny from all
</Files>
<Files *.sql>
deny from all
</Files>
<Files *.inc.php>
deny from all
</Files>
<Files *.db>
deny from all
</Files>
# END s9y
Re: second URL
It's a bit odd that the s9y .htaccess rules are in your root directory. The "Redirect 301" rules I can understand: those were probably hand coded to replace plain HTML pages. The ErrorDocument and DirectoryIndex make sense, too. But all those RewriteRules really belong in /s9y/.htaccess.
This is the one causing the trouble:
If you comment it out, you'll be able to access any subdirectory you like. But you'll also lose permalinks. You need something better.
We expect that the s9y/.htaccess will have those RewriteRules. If so, you can remove them from your root directory. If not, I believe they got manually moved around, perhaps during the attempt at relocation. Comment out the RewriteRules in the root .htaccess, then change the Serendipity "paths" configuration and save it. S9Y will write a .htaccess file in the s9y/ directory.
Once you've got the RewriteRules in the s9y/ directory, you should be able to directly access the files in bla/. For instance, bla/blahblah.html should work. However, bla/ will still take you to the s9y front page. That's because you didn't specify a file, so the webserver tries to find an index for the directory. The .htaccess specifies the index for a directory with the DirectoryIndex command (appropriately enough). If it can't find one in the current directory (bla/) it checks the parent directory. It continues up the tree until it finds /.htaccess, which says to use /s9y/index.php.
That's easy to fix. Just put a .htaccess in the bla/ directory with a DirectoryIndex pointing to a real file, like index.html or something. Then when you try to access bla/, you'll get that file.
I hope I'm not rambling too much. In short, have Serendipity write a /s9y/.htaccess, remove the RewriteRules from the /.htaccess, and add a /bla/.htaccess with a valid DirectoryIndex. Then you'll be able to access everything you want.
This is the one causing the trouble:
Code: Select all
RewriteRule (.*\.html?) index.php?url=/$1 [L,QSA]
We expect that the s9y/.htaccess will have those RewriteRules. If so, you can remove them from your root directory. If not, I believe they got manually moved around, perhaps during the attempt at relocation. Comment out the RewriteRules in the root .htaccess, then change the Serendipity "paths" configuration and save it. S9Y will write a .htaccess file in the s9y/ directory.
Once you've got the RewriteRules in the s9y/ directory, you should be able to directly access the files in bla/. For instance, bla/blahblah.html should work. However, bla/ will still take you to the s9y front page. That's because you didn't specify a file, so the webserver tries to find an index for the directory. The .htaccess specifies the index for a directory with the DirectoryIndex command (appropriately enough). If it can't find one in the current directory (bla/) it checks the parent directory. It continues up the tree until it finds /.htaccess, which says to use /s9y/index.php.
That's easy to fix. Just put a .htaccess in the bla/ directory with a DirectoryIndex pointing to a real file, like index.html or something. Then when you try to access bla/, you'll get that file.
I hope I'm not rambling too much. In short, have Serendipity write a /s9y/.htaccess, remove the RewriteRules from the /.htaccess, and add a /bla/.htaccess with a valid DirectoryIndex. Then you'll be able to access everything you want.
Re: second URL
Thanks!
Great and very comprehensive reply !!!
I can access everything that i need now - just like I needed it.
Cheers,
Daniello
Great and very comprehensive reply !!!
I can access everything that i need now - just like I needed it.
Cheers,
Daniello
Re: second URL
Judebert, seeing that you know much about the htaccess file.
Metacheckengines e.g. http://www.friseurwelt.de/service/meta.php deny to check my site when I enter: http://www.lowicki.de
Entering the path http://www.lowicki.de/s9y/index.php works.
So I figure that the htaccess file in the s9y dir is fine but the htaccess file in my root isn't.
Do you possibly see a flaw?
Any pointer is greatly appreciated.
edit (2): I found a tool that did not get hickups on DirectoryIndex /s9y/index.php so I was unsure if google would see my tags or not. Asking google's webmaster tools I found out - it will not see my tags
Just working with 301 redirects within the .htacces fill doesn the trick - search engines can handle those. Now google and all other tools read my tags. The downside is .. that the my second URL doesn't remain in my web-url anymore (which was really nice while it lasted). So http://www.netzomane.de now immediately switches to http://www.lowicki.de .. kind of a pity .. but .. who needs a website that can't be indexed by google.
The next alternative would be to use a meta redirect within an index.html file .. this fixes the domain issues once again but obviously kills the ability for meta-checks again. So .. nice try .. but no success.
Any hints on how to fix all issues in one are greatly appreciated.
Cheers,
Daniel
Metacheckengines e.g. http://www.friseurwelt.de/service/meta.php deny to check my site when I enter: http://www.lowicki.de
Entering the path http://www.lowicki.de/s9y/index.php works.
So I figure that the htaccess file in the s9y dir is fine but the htaccess file in my root isn't.
Do you possibly see a flaw?
Code: Select all
# BEGIN s9y
ErrorDocument 404 /s9y/index.php
DirectoryIndex /s9y/index.php
php_value session.use_trans_sid 0
php_value register_globals off
php_value session.use_cookies On
redirect 301 /cv.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /cv2.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /cv3.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /cv4.htm http://www.lowicki.de/s9y/pages/cv.html
redirect 301 /partner.htm http://www.lowicki.de/index.php
redirect 301 /artikel.htm http://www.lowicki.de/s9y/pages/referenzen.html
redirect 301 /artikel2.htm http://www.lowicki.de/s9y/pages/referenzen.html
redirect 301 /artikel3.htm http://www.lowicki.de/s9y/pages/referenzen.html
redirect 301 /kontakt.htm http://www.lowicki.de/s9y/pages/contactform.html
redirect 301 /weiterbildung.htm http://www.lowicki/index.php
redirect 301 /fresh.htm http://www.lowicki.de/index.php
redirect 301 /index.htm http://www.lowicki.de/index.php
redirect 301 /index.html http://www.lowicki.de/index.php
# END s9y
edit (2): I found a tool that did not get hickups on DirectoryIndex /s9y/index.php so I was unsure if google would see my tags or not. Asking google's webmaster tools I found out - it will not see my tags
Just working with 301 redirects within the .htacces fill doesn the trick - search engines can handle those. Now google and all other tools read my tags. The downside is .. that the my second URL doesn't remain in my web-url anymore (which was really nice while it lasted). So http://www.netzomane.de now immediately switches to http://www.lowicki.de .. kind of a pity .. but .. who needs a website that can't be indexed by google.
The next alternative would be to use a meta redirect within an index.html file .. this fixes the domain issues once again but obviously kills the ability for meta-checks again. So .. nice try .. but no success.
Any hints on how to fix all issues in one are greatly appreciated.
Cheers,
Daniel