On Tuesday, September 3, 2013 4:41:39 PM UTC-7, JamesThomasMoon1979 wrote:
> I want to hide some fields permanently (but not remove).
>
> The current trac.ini has contents
>
> planid = text
> planid.label = Test Plan
>
> I stop the trac server and apache2 . I comment out these fields
>
> # do not want to display this field
> # planid = text
> # planid.label = Test Plan
>
> Then I restart the trac and the apache2. However, the webserver requires
> me to upgrade the database trac-admin /var/trac/ upgrade
> Afterward, trac.ini has been reverted to
>
> planid = text
>
> planid.label = Test Plan
>
>
> *How do I permanently hide this field planid ?*
>
> Using trac 0.12.2 with apache2 and sqlite database. Plugin
> TestManagerForTracPlugin<http://trac-hacks.org/wiki/TestManagerForTracPlugin>
> .
> I know about the trac plugin DynamicFieldsPlugin . However, before I
> install more plugins (and risk destabilizing the server), I wanted to see
> if there is a safer solution.
> I know about trac plugin
> BlackMagicTicketTweaksPlugin<http://trac-hacks.org/wiki/BlackMagicTicketTweaksPlugin>.
> However, that is not ready for version 0.12.2 and I cannot risk
> destabilizing this trac server.
> I know about trac plugin
> TicketSubmitPolicyPlugin<http://trac-hacks.org/wiki/TicketSubmitPolicyPlugin>.
>
> However, that is claimed to be
> buggy<https://groups.google.com/d/msg/trac-users/maPOLfAXFWE/8QAcsJK3hzcJ>
> .
>
TestManagerForTracPlugin is restoring the custom field. From the
implementation of IEnvironmentSetupParticipant, in the method _need_upgrade:
if 'testcaseid' not in custom or 'planid' not in custom:
self.env.log.debug('TestManager needs to be upgraded: missing
custom ticket fields.')
return True
I suppose you'll need to do one of the following:
* Remove TestManagerForTracPlugin
* Make an argument for a use case of not requiring this custom field and
ask the plugin author to make it optional
* Hide the field using one of the approaches you've already suggested
A final possibility, which probably won't help you much immediately, would
be to request an enhancement to Trac allowing a custom field to be hidden.
I suppose in general there could be use cases for hiding a custom field
from the interface, while keeping it as a member of the ticket model.
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.
