On Jul 31, 1:59 am, jevans <[email protected]> wrote: > On May 7, 12:15 am, "Mihamina Rakotomandimby (R12y)" > <[email protected]> wrote: > > On May 6, 5:51 pm,jevans<[email protected]> wrote: > > > Hello, > > > > We finally moved our project from an old Win2k server to a newer XP > > > server with 0.11.4 and noticed that our embedded TicketQuerymacro > > > results tables are no longer shaded by priority. /query results pages > > > are shaded as expected. > > > Went back to the old server (0.11.3) and a test XP server (0.11.4.rc1) > > > to verify it worked on both of them. > > > Tracd web server is used in all cases. > > > I do not see anything about this on the Trac site or this list so I am > > > suspicious I have something set up wrong. > > > > I see this in the log on the new server: > > > > 2009-05-06 11:10:36,901 Trac[api] WARNING: HTML preview using > > > <trac.mimeview.enscript.EnscriptRenderer object at 0x01AAFD90> failed > > > (Running enscript failed with (0, 'enscript' is not recognized as an > > > internal or external command, > > > operable program or batch file.), disabling EnscriptRenderer (command: > > > 'enscript --color -h -q --language=html -p - -Epython')) > > > Traceback (most recent call last): > > > File "c:\programs\python26\lib\site-packages\Trac-0.11.4-py2.6- > > > win32.egg\trac\mimeview\api.py", line 715, in render > > > rendered_content, filename, url) > > > File "c:\programs\python26\lib\site-packages\Trac-0.11.4-py2.6- > > > win32.egg\trac\mimeview\enscript.py", line 147, in render > > > raise Exception(err) > > > Exception: Running enscript failed with (0, 'enscript' is not > > > recognized as an internal or external command, > > > operable program or batch file.), disabling EnscriptRenderer (command: > > > 'enscript --color -h -q --language=html -p - -Epython') > > > > But I am not sure what to make of it. Any suggestions? > > > -jevans > > > 1°) I wonder what is not clear in this Exception message. > > 2°) Searching the web with the error message will help > > I'm a bit slow getting on this. > > You're right, I hadn't looked for the error text. I was looking for > terms like TicketQuery, priority, and shading. Now that I look into > Enscript a bit, I'm quite positive I've done nothing with it > previously and yet TicketQueryshading worked for us on two previous > servers. The Trac docs seem to be recommending Pygments over Enscript > at this point for code syntax highlighting. Doesn't seem like the > same thing but I tried installing Pygments today with no effect. > > I set logging to DEBUG. I don't see any entries when I access a page > with TicketQuerytables except that it was accessed. It's been long > enough I'm no longer sure of the circumstances of the error in my > original mail above. > > So a question (or 2) - what does TicketQueryuse to do its priority > shading, and why might it not work when /query's does work? Any clues > what I might ought to be looking at? > > The server is still 0.11.4. > > Thanks for any suggestions, > -jevans
Finally found something on this. I had a ProgressMeter macro at the top of each page containing the TicketQuery macros. When I remove the ProgressMeter macros, the TicketQuery results are priority shaded as they should be. - jevans --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
