Error with subdomain ...

[garvinhicking]

Hannelore,

yes that it right. As I mentioned earlier in the thread it is NOT POSSIBLE to make serendipity listen on two different directories. The way you want it to work would be two different directories.

That will not work. You need to resort to one single way of the setup and configure the paths to be correct for that one option. You can only setup HTTP redirection on the other URL you want it to be.

The reason why the blog does not show up without index.php is that in index.php you find a DirectoryIndex /serendipity/index.php value. When you call the subdomain, such a directory does not access! Thus the error, which is also the root of the problem. Serendipity can only configure one path, it cannot autodetect its path (currently).

I do not know of any PHP cms/blog application that works within two completely different directory layouts, so you need to workaround it with HTTP redirection or mod_rewrite redirection.


Regards,
Garvin

[hannelore]

Thanks Garvin. Actually I do not need two paths. The subdomain would be enough.
But how can I make the necessary changes?
I could move the serendipity folder to the root, but then I still have path-problems.

Should I do a whole new installation?

[garvinhicking]

Changing everything to the subdomain should work like this:

1. Copy all serendipity files into the path where the subdomain points to.

2. Make sure that all files and directories have the same permissions after copying. The webserver needs to be able to write to .htaccess, serendipity_config_local.inc.php and templates_c!

3. Now enter the admin interface via http://subdomain/serendipity_admin.php. Go to the configuration and now set all path and URL settings to point to your subdomain and save your settings. If that does not work or makes trouble, use phpMyAdmin or sth similar to check out your serendipity_config DB table. There you can manually alter all the path settings!

HTH,
Garvin

[hannelore]

After updating to vers. 0.9 I had something similiar as before, that's why I add it to this post (hope it is ok)

If I call
http://blog.matriarchy.info/
I get an error 403 Der Zugriff auf die angeforderte Datei wurde verweigert.

If I call
http://blog.matriarchy.info/index.php

the blog shows

BUT, and here it comes: if I delete the .htaccess file from the server (what I did) the subdomain works just fine!

Now its up to you to find out why

[garvinhicking]

Well, this is easy. The .htaccess file contains this directive:

DirectoryIndex /blog/index.php

This URL can only be found if the blog is called on http://matriarchy.info/blog/ - if you call it in the subdomain, the path /blog/index.php cannot be found and thus you get a 403 error.

So you would need to remove that directoryIndex directive, but if you disable this you cannot use URL rewriting for "pretty URLs". I think also with mod_rewrite it wouldn't work becaues both use path settings, and they would differ when being accessed on the main domain or the subdomain. Now that I write about it, this is the more problematic reason why two different paths do not properly work

Regards,
Garvin