[prev in list] [next in list] [prev in thread] [next in thread]
List: trac
Subject: Re: [Trac] Issue with fields displayed in the header of the ticket box
From: Nicolas MARTIN <ntmlod () locean ! upmc ! fr>
Date: 2018-01-23 16:00:13
Message-ID: 41b9678b-a162-c0fd-10c6-44cd74cfff85 () locean ! upmc ! fr
[Download RAW message or body]
Ok I got it.
After displaying debug output from HideVals, I saw that the owner field
had been filtered. From the administration interface, there is no panel
'Owner' under 'HideVals' so previously I thought that this field was not
affected by the plugin. The owner field is already controlled with a
dropdown menu thanks to 'restrict_owner' option.
I added 'owner' to 'dont_filter' option and so I got back the good heading.
Not sure if there is something to do here, it's more like a
misconfiguration.
Nicolas
On 23/01/2018 15:08, Nicolas MARTIN wrote:
>
> I found the culprit, HideVals plugin.
>
> The ticket type is one of the filtered fields so probably the plugin
> messes with 'fields_map' array but I don't know how.
> It should only remove the filtered entries within the dropdown menus
> in the 'Modify' section of the ticket.
>
>
> Nicolas
>
>
> On 22/01/2018 22:06, Ryan Ollos wrote:
> >
> >
> > On Mon, Jan 22, 2018 at 8:04 PM, Nicolas MARTIN
> > <ntmlod@locean.upmc.fr <mailto:ntmlod@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 <http://ticket.id>)}"
> > class="trac-id">#${ticket.id <http://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+unsubscribe@googlegroups.com
> > <mailto:trac-users+unsubscribe@googlegroups.com>.
> > To post to this group, send email to trac-users@googlegroups.com
> > <mailto: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.
>
> --
> 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+unsubscribe@googlegroups.com
> <mailto:trac-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to trac-users@googlegroups.com
> <mailto: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.
--
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+unsubscribe@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.
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-15">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Ok I got it.</p>
<p>After displaying debug output from HideVals, I saw that the owner
field had been filtered. From the administration interface, there
is no panel 'Owner' under 'HideVals' so previously I thought that
this field was not affected by the plugin. The owner field is
already controlled with a dropdown menu thanks to 'restrict_owner'
option.<br>
I added 'owner' to 'dont_filter' option and so I got back the good
heading.</p>
<p>Not sure if there is something to do here, it's more like a
misconfiguration.</p>
<p><br>
</p>
<p>Nicolas<br>
</p>
<br>
<div class="moz-cite-prefix">On 23/01/2018 15:08, Nicolas MARTIN
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:316c1fe2-34de-85d0-ebff-7308f7b65833@locean.upmc.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-15">
<p>I found the culprit, HideVals plugin.</p>
<p>The ticket type is one of the filtered fields so probably the
plugin messes with 'fields_map' array but I don't know how.<br>
It should only remove the filtered entries within the dropdown
menus in the 'Modify' section of the ticket.</p>
<p><br>
</p>
<p>Nicolas<br>
</p>
<br>
<div class="moz-cite-prefix">On 22/01/2018 22:06, Ryan Ollos
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+BGpn8U-rg2c95f7pANJKvp2dfKARY5a4_eVHM_wnDBebFf0g@mail.gmail.com">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 22, 2018 at 8:04 PM,
Nicolas MARTIN <span dir="ltr"><<a
href="mailto:ntmlod@locean.upmc.fr" target="_blank"
moz-do-not-send="true">ntmlod@locean.upmc.fr</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
<br>
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.<br>
Everything was going on as if an offset was at work
somewhere.<br>
<br>
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:<br>
<br>
<h2><br>
<a href="${href.ticket(<a href="http://ticket.id"
rel="noreferrer" target="_blank"
moz-do-not-send="true">ticket.id</a>)<wbr>}"
class="trac-id">#${<a href="http://ticket.id"
rel="noreferrer" target="_blank"
moz-do-not-send="true">ticket.id</a>}<<wbr>/a><br>
<span class="trac-status"><br>
${'status' in fields_map and
fields[fields_map['status']].r<wbr>endered or
ticket.status}<br>
</span><br>
<span class="trac-type" py:if="ticket.type"><br>
<!--${'type' in fields_map and
fields[fields_map['type']].ren<wbr>dered or
ticket.type}--><br>
${ticket.type}<br>
</span<br>
<span class="trac-resolution"
py:if="ticket.resolution"><br>
<!--(${'resolution' in fields_map and
fields[fields_map['resolution'<wbr>]].rendered or
ticket.resolution})--><br>
(${ticket.resolution})<br>
</span><br>
</h2><br>
<br>
Nothing really serious but I wonder if something is
relevant here as it is the first time I have to fix a
template.<br>
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.<br>
</blockquote>
<div><br>
</div>
<div>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:</div>
<div><a
href="https://trac.edgewall.org/wiki/TracInterfaceCustomization#ProjectTemplates"
moz-do-not-send="true">https://trac.edgewall.org/wiki/TracInterfaceCustomization#ProjectTemplates</a></div>
<div><br>
</div>
<div>Another possibility is that you haven't regenerated
static resources after a Trac upgrade:</div>
<div><a
href="https://trac.edgewall.org/wiki/TracUpgrade#a5.Refreshstaticresources"
moz-do-not-send="true">https://trac.edgewall.org/wiki/TracUpgrade#a5.Refreshstaticresources</a><br>
</div>
<div><br>
</div>
<div>Do you have a custom site.html?</div>
<div><br>
</div>
<div>The other possibility is as you mentioned, that a
plugin is causing the issue.</div>
<div><br>
</div>
<div>The issue you describe would certainly have been
noticed by now if it was a defect with the Trac 1.0.1.</div>
<div><br>
</div>
<div>- Ryan </div>
</div>
</div>
</div>
-- <br>
You received this message because you are subscribed to the
Google Groups "Trac Users" group.<br>
To unsubscribe from this group and stop receiving emails from
it, send an email to <a
href="mailto:trac-users+unsubscribe@googlegroups.com"
moz-do-not-send="true">trac-users+unsubscribe@googlegroups.com</a>.<br>
To post to this group, send email to <a
href="mailto:trac-users@googlegroups.com"
moz-do-not-send="true">trac-users@googlegroups.com</a>.<br>
Visit this group at <a
href="https://groups.google.com/group/trac-users"
moz-do-not-send="true">https://groups.google.com/group/trac-users</a>.<br>
For more options, visit <a
href="https://groups.google.com/d/optout"
moz-do-not-send="true">https://groups.google.com/d/optout</a>.<br>
</blockquote>
<br>
-- <br>
You received this message because you are subscribed to the Google
Groups "Trac Users" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a
href="mailto:trac-users+unsubscribe@googlegroups.com"
moz-do-not-send="true">trac-users+unsubscribe@googlegroups.com</a>.<br>
To post to this group, send email to <a
href="mailto:trac-users@googlegroups.com" \
moz-do-not-send="true">trac-users@googlegroups.com</a>.<br> Visit this group at <a
href="https://groups.google.com/group/trac-users"
moz-do-not-send="true">https://groups.google.com/group/trac-users</a>.<br>
For more options, visit <a
href="https://groups.google.com/d/optout" \
moz-do-not-send="true">https://groups.google.com/d/optout</a>.<br> </blockquote>
<br>
</body>
</html>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "Trac \
Users" group.<br /> To unsubscribe from this group and stop receiving emails \
from it, send an email to <a \
href="mailto:trac-users+unsubscribe@googlegroups.com">trac-users+unsubscribe@googlegroups.com</a>.<br \
/> To post to this group, send email to <a \
href="mailto:trac-users@googlegroups.com">trac-users@googlegroups.com</a>.<br /> \
Visit this group at <a \
href="https://groups.google.com/group/trac-users">https://groups.google.com/group/trac-users</a>.<br \
/> For more options, visit <a \
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br \
/>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic