On 6/14/13, David Galligani <[email protected]> wrote: > >> I don't believe it is possible to rename the default product either. It >> sounds like Olemis is suggesting that it should be possible to rename the >> default product, so perhaps we will leave #517 open and consider >> implementing that. >> https://issues.apache.org/bloodhound/ticket/517#comment:2 > > It seems logical to me ... why you'd want a product "default " that you > can't edit ?
Like I just said in a previous message wrt default product prefix there are subtle technical challenges involved ... that will be sorted out eventually. Notice that everything else may be edited , except immutable product prefix . ;) > Furthermore when you can assign the flag "default" to another one . > Having a default-not-default project doesn't make much sense to me :) > + >> >> You'll need to upgrade to> r1492525 to avoid the "qct not defined" >> error. >> > hmmm ... > svn co https://svn.apache.org/repos/asf/bloodhound/trunk bloodhound > U bloodhound/bloodhound_theme/bhtheme/htdocs/js/theme.js > U bloodhound/bloodhound_theme/bhtheme/theme.py > U bloodhound/bloodhound_theme/bhtheme/templates/bh_about.html > U bloodhound/bloodhound_theme/bhtheme/templates/bloodhound_theme.html > U bloodhound/bloodhound_theme/bhtheme/templates/bh_login.html > A bloodhound/bloodhound_theme/bhtheme/templates/bh_admin_users.html > A bloodhound/bloodhound_theme/bhtheme/templates/bh_account_details.html > U bloodhound/bloodhound_theme/bhtheme/templates/bh_report_delete.html > U > bloodhound/bloodhound_theme/bhtheme/templates/bh_admin_accountsconfig.html > U bloodhound/bloodhound_search/setup.py > U > bloodhound/bloodhound_dashboard/bhdashboard/widgets/templates/widget_grid.html > U bloodhound/bloodhound_multiproduct/tests/env.py > U bloodhound/bloodhound_multiproduct/setup.py > U bloodhound/bloodhound_multiproduct/multiproduct/env.py > U bloodhound/bloodhound_multiproduct/multiproduct/api.py > U bloodhound/bloodhound_relations/setup.py > Checked out revision 1493289. > > But still say " Powered by Apache Bloodhound 0.6.0dev-r1491434 > <http://tickets.ntwoo.com/products/N2O_/about>" :P > > There is something I should know ? > Maybe what's happening to you is similar to what happens very often to members of my team when deploying Bloodhound . This might be related to the approach used to install the virtual environment . - If using setup.py develop then the svn co should lead to an automatic upgrade of your BH instance * ... maybe after sending HUP to apache2 process(es) - If using setup.py install then you must run it once again to upgrade the copy in your site-packages ... if this is the case then it's a Python distutils thing ;) -- Regards, Olemis.
