@ramadama

"Home / Main" collections are meant to host the home page of your site (http://b2evolution.net/man/collection-type-panel). They are set to display the Special Front Page display (disp=front). Also for generic functions such as messaging, user profiles, etc.

New skins as "Horizon" are often delivered in two packages (or more). One for regular "Blog" collections and another for that special "Home / Main" collection.

Do i get this right: it would mean to set up a site with two collections, intropage with Mail skin and then a blog with blog skin and the blog would be a subdirectory to the first one then?

Yes, you do get it right. If you want a home page design, you need at least two collections in your site, but there is no need to create one of them in a subfolder.

b) is there a way to keep the sidebar in the 'Single post page'-mode with the Horizon blog skin? I don't want loose the sidebar/menue and wonder if there's a switch to keep it.

This skin doesn't implement sidebars for single disp. You can apply this workaround to get it in your site: https://github.com/mgsolipa/b2evolution/commit/e5716a0b557d2bfae02873f8898a53a0b68c0b9c

Regards!

@ramadama now you can download the skin again. A new parameter to decide if the sidebar will be displayed in disp=single is already included in version 1.1.

http://skins.b2evolution.net/horizon-blog-skin

back to this situation, this time beyond the theoretical interest: I have a collection set up to a subdomain http://kerosinsteuer.wald.org and the startpage is 'Special Front page' and is meant to hold only one post Type: Intro-Front

I want show regular blog posts all in a subfolder http://kerosinsteuer.wald.org/info/ but don't understand, how to tell the system about that.

Achieving this, I've set up an additional collection and now face two problems: either i choose absolute url http://kerosinsteuer.wald.org, but then the blog posts don't show in the subdirectory or i choose http://kerosinsteuer.wald.org/info/ as url, but then i get an 'Error 404: NOT FOUND!'

running b2e 6.6.6 ... and the system is installed at another domain to which the subdomain http://kerosinsteuer.wald.org is linked to.

@ramadama your different blogs approach is correct. Just keep the sub-domain collection URL pointing to its root: http://sub-domain.example.com/. For the second collection you can use a stub (http://b2evolution.net/man/stub-file) file, so try this:

1. Create a folder info in the root directory of your site.
2. Copy & paste index.php and .htaccess to it.

3. Open info/index.php and do the following:

   1. Modify the first statement to correctly find the config.php main file. i.e.: change it from:

      require_once dirname(__FILE__).'/conf/_config.php';

      to

      require_once dirname(__FILE__).'/../conf/_config.php';

   2. Add the ID of the collection you're pointing to. You can find a line with the following text:

      //A blog has been requested... Let's set a few default params:
      $blog = 99; // Replace 99 by the ID of your own collection

4. Set the URL Relative to baseurl or Absolute URL. In any case, the final URL should be something like: http://sub-domain.example.com/info/

That might do the trick. Please let us know.

Regards!

Thanks a lot for this solution, Manuel. It indeed did partly, what i wanted. But there is one thing, which is strange: it shows the postings of all the collections running on this installation - see http://kerosinsteuer.wald.org/news/ (i replace info with news). What is causing this confusion and how do i get rid of it?

And there is one idea, that probably would help a lot with setting up this kind of 'twin'-collections: if there would be a feature 'copy collection', which should copy all the relevant settings, like skin and widget details. because most time one would want the twin have a similar appearance and it would save time doing it.

Meanwhile i've set up another or new collection ... this time it behaves well: no posts from other collections mixed into this fresh collection.

As i am not sure, how come to have this blend of posts of various collections in this new one AND not knowing if, once i delete this not well behaving collection, it might kill all the postings wrongly attached to it, i still kept this one waiting for some advice maybe.

I 'moved' this not well behaving collection to a new directory for documentation purpose, now it is http://kerosinsteuer.wald.org/news30/