Wiki package installed as home page package, but inactive by default (3.1)

[mtkr0l]

When I install BW3.1 I choose Wiki package to install and be the default package for home page.
It is installed but upon first run I have to activate the package manually - after reading the message on the front page.
Confusing for first users.

I'm not sure which package is responsible for this, so I'm creating issue under "install"

[lsces]

God I hate github ...
How do we see what issues are open across the project :( git was not designed to handle modular projects only heavyweight stuff like the linux kernel...

Yes this is an installation problem, but I think that it is more to do with defining the what a default 'new user' setup should be? And that depends on just what the user is planning to do with the site. I don't think it is unreasonable to start with the site 'locked down' so what I think is missing is some guidelines to take you through the various options and help you 'open up' things in the right way, once the site has been configured.

Perhaps what is missing is a 'home page' that is displayed when site does require a user to log in to use the site? This would probably be an alternative to the login page and give some contact details and the like for the site owner? It would perhaps simply be an alternative template fro the login page as I can't see an easy way to bypass security and display a page when - for instance - wiki is not installed anyway. Perhaps the 'user page' for the guest/anonymous account could be an alternative starting point?

[mtkr0l]

In 2.x I could choose to include "dummy content" in Wiki (well, not exactly dummy, as this was a short manual) shown right after install, in 3.x it's sort of the opposite, I install Wiki as the front page package, but it's not even there when I first access my site, all I see is a short note about Wiki not being active. It's an easy fix, just an unfortunate first impression.

[lsces]

I must have missed something when I installed fresh. I can remember seeing the 'dummy content' option which I skipped but I'm sure it needed me to log in before I could do anything. Need to check this again with the next build!

[mtkr0l]

I'm totally sure it's there. I used it a couple of times, and I remember getting an installer message that was something like "I couldn't really install that content for you, because the Wiki package is inactive" :)

[lsces]

I wonder if this came about because of the bug hiding of non-selected plugins? That might explain it, and perhaps I'm looking at the wrong thing now. Certainly wiki should be enabled automatically ... that is the setting in the install settings. Need to ensure that it HAS been fixed in the next build.