On Tuesday, October 31, 2017 at 6:47:51 AM UTC-7, Clemens Feige wrote: > > > RjOllos wrote on 29.10.2017 at 22:32: > > > > > > On Sunday, October 29, 2017 at 4:52:37 AM UTC-7, Clemens Feige wrote: > >> > >> > >> RjOllos wrote on 27.10.2017 at 20:45: > >>> > >>> > >>> On Friday, October 27, 2017 at 9:09:02 AM UTC-7, RjOllos wrote: > >>>> > >>>> > >>>> > >>>> On Friday, October 27, 2017 at 4:09:46 AM UTC-7, Clemens Feige wrote: > >>>>> > >>>>> Hello > >>>>> > >>>>> I am using the TracKeywordsPlugin which generates an "Add Keywords" > >>>>> entry field at the bottom of each ticket HTML page. It works > properly > >>>>> most of the time, but sometimes this entire field is missing. What > may > >>>>> be the reason? > >>>>> > >>>>> https://trac-hacks.org/wiki/TracKeywordsPlugin > >>>>> > >>>>> Independent from this particular plugin, what mechanism may prevent > >>>>> that a plugin may execute? > >>>>> (Please note that generally it works, but not always.) > >>>>> > >>>>> How shall I investigate plugin problems? > >>>>> > >>>>> Maybe it depends on which Apache server instance is used by the > >>>>> particular client (although I restarted Apache, see below...) > >>>>> > >>>>> Some more details: > >>>>> > >>>>> 1. > >>>>> We have TRAC version 1.0.4 running on Linux with Apache server. > >>>>> Clients > >>>>> are under Windows with Firefox browser. The plugin is installed as > >>>>> Python-Egg file in the plugin-directory of the TRAC repo. > >>>>> > >>>>> 2. > >>>>> Of course it looks like browser cache problem. But this cannot be > the > >>>>> root cause, > >>>>> - because it happens also with tickets which I never visited > >>>>> before. > >>>>> - reloading the page does not help (Firefox, press F5 twice) > >>>>> - totally different browser has same issue > >>>>> > >>>>> 3. > >>>>> Restarting the Apache-Server and reloading the page cures the > problem. > >>>>> But after a while it re-appears with other tickets. > >>>>> > >>>>> 4. > >>>>> Log-file does not show any plugin errors. > >>>>> > >>>>> Thanks for help > >>>>> Clemens > >>>>> > >>>> > >>>> Any errors in the browser console? > >>>> > >>>> > https://trac.edgewall.org/wiki/TracTroubleshooting#ChecktheBrowserConsole > >>>> > >>>> TracKeywords should be modified to so that it doesn't use a Genshi > >>>> Transformer. I will make some changes to the code today. > >>>> > >>>> - Ryan > >>>> > >>> > >>> Please try the latest from TracKeywords trunk. I modified the plugin > so > >>> that Genshi Transformer is no longer used. > >>> https://trac-hacks.org/changeset/16925 > >>> > >>> - Ryan > >>> > >> > >> Hello Ryan > >> > >> I appreciate very much your work and r16925 renovation of the > >> TracKeywords plugin. Good work! > >> > >> Anyway, using the latest trunk revision r16925 I still frequently miss > >> the entire keyword field. Sometimes it is there, sometimes not. Miss > >> rate is approx. 25%. > >> > >> The browser console does not show anything related to TracKeywords. > >> > >> I can confirm the issue with different browsers, on different machines, > >> with different Trac repos (but all on same server). > >> > >> What makes this issue mysterious to me is that it is an intermediate > >> problem. It occurs only from time to time. May this be related to the > >> server-side state of the Apache-server? > >> Do you think it is worth to test with the trac-build-in webserver? > >> I have no idea ... > >> > >> Thanks > >> Clemens > >> > > > > Next time you see the issue, view the page source and look whether the > > keywords have been added to the page in the trac_keywords array, and if > the > > trac_keywords.js file has been added in a script tag. > > > > - Ryan > > > > Hello Ryan > > I did as you requested: > > The problematic HTML page differs from a correct one as follows: > - it does not load trac_keywords.css, > - it does not contains the trac_keywords JavaScript array, > - it does not load scriptrac_keywords.js. > > I am not familiar with TRAC and plugin internals. But I begin to > understand that the TracKeywordsPlugin does its magic based on > JavaScript. The original page source actually never contains the final > keyword area at bottom of page. Instead the keyword area is supposed to > be inserted solely by JavaScript. > > I digged into the TRAC log-file and found issues follows: > > LOG FOR FAILURE SITUATION: > > 2017-10-31 14:19:05,402 Trac[main] DEBUG: > Dispatching <RequestWithSession > "GET '/chrome/keywords/trac_keywords.js'"> > 2017-10-31 14:19:05,405 Trac[chrome] WARNING: > File trac_keywords.js not found in any of [] > 2017-10-31 14:19:05,405 Trac[main] WARNING: > [172.16.70.200] HTTPNotFound: 404 Not Found > (File trac_keywords.js not found) > > LOG FOR WORKS FINE SITUATION: > > 2017-10-31 14:40:22,705 Trac[main] DEBUG: > Dispatching <RequestWithSession > "GET '/chrome/keywords/trac_keywords.css'"> > 2017-10-31 14:40:22,828 Trac[main] DEBUG: > Dispatching <RequestWithSession > "GET '/chrome/keywords/trac_keywords.js'"> > > What else can I do? > > Thanks > Clemens >
You've demonstrated that the script is not found. The script should be served by Trac: https://trac.edgewall.org/browser/tags/trac-1.2.2/trac/web/chrome.py?marks=727#L710 It seems like the plugin is not loaded in the process that is serving the request. I suspect it must be a web server configuration issue. It would be interesting to see if you can reproduce the issue with tracd. Which web server are you running? Can you share the configuration? - 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.
