On 29 April 2013 12:57, Gary Martin <[email protected]> wrote:
> On 29/04/13 11:42, Anze Staric wrote:
>
>> Upgrading wikis to multiproduct now moves all wikis (and attachments)
>> to default product. As a result, the main page ('/') is blank, as the
>> page WikiStart does not exist in the global product.
>>
>> If a user plans to create multiple products, this is not a big
>> problem, as he will probably need a new entry page anyway. We could
>> add one of the guides as a WikiStart page in global env to avoid
>> PageNotFound error.
>>
>> But if a user does not need multiple products (he just upgraded to
>> bloodhound because of our other awesome features), how should he
>> proceed? Should we provide a way to enable mapping of wikis in default
>> product to global namespace (the way we do with tickets, reports,
>> ...)? Or should such users just disable the multiproduct module in
>> trac.ini?
>>
>
> Hi,
>
> We could suggest that if an installation is only ever expected to be a
> single product installation then webserver configuration could be used to
> hide the global level. I think that a proper installation should include a
> webserver rather than using tracd directly. It might be possible to offer
> the opportunity to have non-multiproduct version if this decision is made
> early in the installation procedure as it may be more difficult to switch
> away later. If we were to support this then we would need more testing to
> be put in place of course to cover that possibility.
>
I don't believe we should provide a 'single product only' installation
option, if that's your suggestion. More complication for little gain. Users
that are so opposed to potentially using multiple products in future that
they want to decide at the point of installation to not use them should use
Trac instead.
>
> Meanwhile, I think putting in a new WikiStart page for the global
> frontpage would be pretty reasonable. We might consider listing the
> products on that page in some way along with any other default text we want
> to provide.
>
I think we should serve up the dashboard page as a landing page by default.
That page does need to be improved further to help facilitate the setup in
a new installation, but that's another topic and shouldn't stop us from
using it as the default landing page (global frontpage as Gary called it).
>
> Cheers,
> Gary
>
Cheers,
Joe
--
Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/>
@jdreimann <https://twitter.com/jdreimann>
