On Mon, Jan 22, 2018 at 8:04 PM, Nicolas MARTIN <ntm...@locean.upmc.fr>
wrote:
> Hello,
>
>
> Recently, I noticed that the header of the ticket properties box with the
> ticket number was not correct: I found the ticket priority in the
> 'trac-status' span, the ticket resolution in 'trac-type' span and nothing
> between the brackets for 'trac-resolution' span whereas the ticket was
> closed.
> Everything was going on as if an offset was at work somewhere.
>
> At first, I suspected one of our several plugins to be at the root of this
> but finally, without further evidence, I fixed it by removing the first
> part of tests with 'fields_map' queries in the ticket_box.html template:
>
> <h2>
> <a href="${href.ticket(ticket.id)}" class="trac-id">#${ticket.id}</a>
> <span class="trac-status">
> ${'status' in fields_map and fields[fields_map['status']].rendered
> or ticket.status}
> </span>
> <span class="trac-type" py:if="ticket.type">
> <!--${'type' in fields_map and fields[fields_map['type']].rendered
> or ticket.type}-->
> ${ticket.type}
> </span
> <span class="trac-resolution" py:if="ticket.resolution">
> <!--(${'resolution' in fields_map and
> fields[fields_map['resolution']].rendered
> or ticket.resolution})-->
> (${ticket.resolution})
> </span>
> </h2>
>
> Nothing really serious but I wonder if something is relevant here as it is
> the first time I have to fix a template.
> We are still on Trac 1.0.1 but I guess nothing has really changed in the
> core related to this on the 1.0 development branch.
>
Do you have modified copies of the templates the environment or shared
"templates" directory? If so, you'll need to reapply your modifications
after every upgrade of your Trac instance, as described here:
https://trac.edgewall.org/wiki/TracInterfaceCustomization#ProjectTemplates
Another possibility is that you haven't regenerated static resources after
a Trac upgrade:
https://trac.edgewall.org/wiki/TracUpgrade#a5.Refreshstaticresources
Do you have a custom site.html?
The other possibility is as you mentioned, that a plugin is causing the
issue.
The issue you describe would certainly have been noticed by now if it was a
defect with the Trac 1.0.1.
- Ryan
--
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
