On Sat, Jun 15, 2013 at 6:05 AM, Matevž Bradač <[email protected]> wrote:
> > On 15. Jun, 2013, at 8:13, Olemis Lang wrote: > > > On 6/14/13, Ryan Ollos <[email protected]> wrote: > >> On Fri, Jun 14, 2013 at 5:02 PM, David Galligani <[email protected]> > wrote: > > [...] > >>> Ok ... > >>> seems I cannot rename it either :) > >>> I' ve got the same error qct not defined ... > >>> > >>> I create another ( a third ) product , but when I try to create ticket > >>> for > >>> this I have the same error too . > >>> BTW , I have 0.6.0dev-r1491434 > >>> > >>> > > [...] > >> > >> I don't believe it is possible to rename the default product either. > > > > I'd rather say «not yet» ;) > > IMHO this is not still supported because : > > > > - It's not a trivial task > > * i.e. not just a single SQL update , notice that (almost) > *everything* > > is connected to a products > > - this can be avoided by setting config values > > One thing to note here - there are two 'names' related to a product, > the product prefix and the product name. The prefix cannot be simply > changed (as explained above), however there should be no problem > changing the product name. The name should have no effect on any > other DB table, it's just a display name. > As for the prefix for the default product, that can be configured > during the installation, using the --default-product-prefix option. > It sounds like a reasonable way to handle this for now would be to emphasize to the user through the installation docs the importance of choosing the desired default product prefix at install time, with extra emphasis that this can't (or can't easily) be changed later.
