You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/07/12 05:06:31 UTC

[Apache Bloodhound] #589: Improve security and verbosity of the "Trac Environment needs to be upgraded" message

#589: Improve security and verbosity of the "Trac Environment needs to be
upgraded" message
-------------------------+--------------------
 Reporter:  rjollos      |      Owner:  nobody
     Type:  enhancement  |     Status:  new
 Priority:  major        |  Milestone:
Component:  trac core    |    Version:
 Keywords:               |
-------------------------+--------------------
 A discussion occurred on the [http://markmail.org/message/2yimvwnaxavxuopt
 mailing list] regarding the //Trac Environment needs to be upgraded//
 message. A typical example of the message that displays in the browser
 after upgrading Bloodhound or Trac, or installing / upgrading a plugin is:

 {{{
 Error

 TracError: The Trac Environment needs to be upgraded.

 Run "trac-admin
 /home/user/Workspace/bh586/bloodhound/installer/bloodhound/environments/sqlite
 upgrade"
 }}}

 Two suggestions resulted from the discussion:
  * It would be preferable if the server path was not revealed to a user
 that doesn't have the `TRAC_ADMIN` permission. Users without `TRAC_ADMIN`
 might only see a HTTP 503 ''Service unavailable'' response with body
 //Under maintenance//.
  * Since Bloodhound will often be installed in a virtualenv (as is
 suggested in the Installation Instructions), the full path to `trac-admin`
 should be provided in the message. The specific case that came up in the
 mailing list discussion was that the user had Trac installed in the global
 packages directory and was inadvertently running the `trac-admin`
 associated with that install because they had not run the activate script
 in their virtualenv or provided the full path to `trac-admin` in the
 virtualenv.

 The changes associated with this ticket will most likely be suggested for
 the Trac core.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/589>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #589: Improve security and verbosity of the "Trac Environment needs to be upgraded" message

Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#589: Improve security and verbosity of the "Trac Environment needs to be
upgraded" message
--------------------------+-------------------------
  Reporter:  rjollos      |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:  Unscheduled
 Component:  trac core    |    Version:
Resolution:               |   Keywords:
--------------------------+-------------------------
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/589#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #589: Improve security and verbosity of the "Trac Environment needs to be upgraded" message

Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#589: Improve security and verbosity of the "Trac Environment needs to be
upgraded" message
--------------------------+--------------------
  Reporter:  rjollos      |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:
 Component:  trac core    |    Version:
Resolution:               |   Keywords:
--------------------------+--------------------

Comment (by rjollos):

 Additionally, from time to time I've seen comments on trac-hacks that a
 "plugin broke the installation", and it turns out that the user just saw
 "Error" and didn't read or understand the meaning of the //environment
 needs upgrade// message. It could be useful to present the message as
 something other than an //error//, just noting that a //manual upgrade
 step is needed//. Even using the term //Alert// could be better than
 //Error//.

 See also related discussion in trac:comment:20:ticket:11189.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/589#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker