Re: [Trac] counter
Am 29. Januar 2020 18:08:54 MEZ schrieb ONeal Freeman : >Is there a hit counter for trac to keep a count of how many users are >accessing the site? > >-- >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 view this discussion on the web visit >https://groups.google.com/d/msgid/trac-users/0d167c6c-972d-4fdc-a746-f6b3a739093a%40googlegroups.com. Have a look at https://trac-hacks.org/wiki/VisitCounterMacro While it may be a bit outdated, I know it worked for me back in der 0.12 days. After all it has no external dependencies, what matters to the usecase in question. Steffen Hoffmann Mit freundlichem Gruß Steffen Hoffmann -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/917C7935-268C-4A40-8C8B-14E3056518BD%40web.de.
Re: [Trac] Re: How to get all the menus of a user through program?
Am 16. Januar 2020 07:34:32 MEZ schrieb Velu Narasimman
:
>Well, I am getting menu as a dictionary as shown below,
>
>{'mainnav': [{'active': False, 'name': 'project', 'label': "a">}, {
>'active': False, 'name': 'added_common', 'label': },
>{'active':
>False, 'name': 'admin', 'label': }, {'active': False,
>'name':
>'reports', 'label': }, {'active': False, 'name':
>'metrics',
>'label': }, {'active': False, 'name': 'mytimesheet',
>'label': <
>Element "a">}, {'active': True, 'name': 'myprojects', 'label': "a"
>>}, {'active': False, 'name': 'timesheetapproval', 'label': "a">}],
>'metanav': [{'active': False, 'name': 'login', 'label': u'logged in as
>karthikeyan.nagaraja'}, {'active': False, 'name': 'logout', 'label': <
>Element "a">}, {'active': False, 'name': 'prefs', 'label': "a">}, {
>'active': False, 'name': 'about', 'label': }]}
>
>I get this, when I refresh the web page in my browser. These menus are
>dynamic, differs among different users based on the permissions that
>they
>have in system. But I wish to generate this without using a browser. So
>how
>can I make a web request handling in program itself and the above
>menus?
>
>
>
>On Thursday, January 16, 2020 at 10:24:17 AM UTC+5:30, Velu Narasimman
>wrote:
>>
>> Hi,
>>
>> I am using MenusPlugin <https://trac-hacks.org/wiki/MenusPlugin>
>for
>> displaying submenus. I need to get all the menus that are about to be
>
>> displayed for a user even before he logs into the site. Is it
>possible? If
>> yes, how shall I do it in a back-end program? Please share me your
>ideas.
>>
>> Thanks in advance.
>>
>
>--
>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 view this discussion on the web visit
>https://groups.google.com/d/msgid/trac-users/f1c42bf0-ed49-409d-805a-eaf723829ba9%40googlegroups.com.
So you know about XML-RPC-Plugin [1]?
IMHO this is the most standardized non-browser access to enabled Trac sites.
[1] https://trac-hacks.org/wiki/XmlRpcPlugin
Mit freundlichem Gruß
Steffen Hoffmann
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/trac-users/2181FE45-9EE8-4CBE-9D4B-7BC04E28D6EE%40web.de.
Re: [Trac] Re: Trac 1.0.19 Released
Am 9. Januar 2020 08:47:22 MEZ schrieb Roger Oberholtzer : >On Thu, Jan 9, 2020 at 6:10 AM Steffen Hoffmann wrote: > >> >Maybe it's time to enlist support in updating plugins? I'm a >> >programmer, but not a Python programmer. But I could consider >trying >> >a few plugins to update. >> > ... >I could help. Except that my python knowledge is not my strong point. >But I am willing to try. Great. Let's join by means of crearing guiding documentation in Trac-hacks Wiki this coming weekend then! Greetings, Steffen Hoffmann -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/DAC00565-EB4E-492E-A8E2-8BB724724789%40web.de.
Re: [Trac] Re: Trac 1.0.19 Released
Am 8. Januar 2020 19:33:16 MEZ schrieb Roger Oberholtzer : >On Wed, Jan 8, 2020 at 3:27 PM Martin wrote: >> >> On 2020-01-07 11:04, Roger Oberholtzer wrote: >> > Perhaps the Plugins that only work with Python 2 should be moved to >a >> > depreciated location? That might make it easier to see which >plugins >> > are effected by a move to Python 3. >> >> As a side note: In Debian we are in the process of remving Trac >> and all packaged plugins as part of the "py2removal" process. We >> would like to reintroduce the Python-3-based Trac again, when it >> is ready, of course. > >The list of Plugins for Trac 1.4 at least is much smaller than the >list of all plugins. > >Maybe it's time to enlist support in updating plugins? I'm a >programmer, but not a Python programmer. But I could consider trying >a few plugins to update. > >Is there a guide for the Trac part? Like the obvious things that need >to be changed for Trac 1.4? Something with example uses and not just >the names of the things to change? I've been reading about Python3 before and right now scanning Trac 1.3 changes while trying to get AccountManagerPlugin Code ready for current Trac 1.4. After current Trac 1.5 releases Trac 1.6 is meant to switch to Python3. I'm willing to share and improve developer instructions as I did some years before for spread I18n support among plugins too. Let‘s do that together. How about that? Greetings Steffen Hoffmann -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/8B47C075-7A01-433B-A235-8BA5666E7BE2%40web.de.
Re: [Trac] Re: Trac 1.0.19 Released
Am 7. Januar 2020 11:04:02 MEZ schrieb Roger Oberholtzer : >On Mon, Jan 6, 2020 at 5:23 PM M M wrote: >> >> What is the point of patching ancient versions? Why not just declare >1.0.x and 1.2.x end of life and focus on 1.4.x and porting to Python3? > >I think I agree. I am guessing the biggest reason for not just >supporting Python 3 is all the plugins that will no longer be usable. >It's not just Trac itself. > >Perhaps the Plugins that only work with Python 2 should be moved to a >depreciated location? That might make it easier to see which plugins >are effected by a move to Python 3. Why do that much extra effort? As we did with Trac that had other major, disruptive code changes before, we can just flag/tag hacks with „trac1.6“ or more explicitely „python3“ as coded for Python 3. Mit freundlichem Gruß Steffen Hoffmann -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/0A21EFF6-664C-411C-A078-0C5C0AC73DB5%40web.de.
Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
Am 19. November 2019 00:09:25 MEZ schrieb thos : >Ryan, > >I am a long-time Trac user, but new to this group. I appreciate your >attentiveness. > >We are trying to create lightweight containers for multiple Trac/SVN >instances, and having all of the development binaries pulled in by pip >is >undesirable. We also need control over when we upgrade resources. > >One difference is that apt-get puts the python packages in >/usr/lib/python2.7/dist-packages, while pip puts them in >/usr/local/lib/python2.7/dist-packages. (This is from memory so may be >off >a bit.) Also, the --force-reinstall doesn't actually remove the >system-installed packages. > >I will continue to explore what might be different. Could you point me >to >where in Trac the "Plugin" page is generated? That might give clues as >to >why the grouping is wrong. Of course the problem could be elsewhere >(e.g. >plugin registration) and I'm willing to do a little digging. It's just >odd >that no errors are produced. > >Thanks. > >-Tom > >On Monday, November 18, 2019 at 9:37:50 AM UTC-6, RjOllos wrote: >> >> >> >> On Sunday, November 17, 2019 at 10:24:24 PM UTC-8, thos wrote: >>> >>> I have some additional information to provide. In my Dockerfile: >>> >>> FROM debian:buster-slim >>> >>> ENV SITE_DIR /var/www/repos >>> ENV LANG C.UTF-8 >>> >>> RUN apt-get update; apt-get install -y \ >>> apache2 \ >>> libapache2-mod-wsgi \ >>> libapache2-mod-svn \ >>> subversion \ >>> python \ >>> trac \ >>> rsync \ >>> ; \ >>> rm -rf /var/lib/apt/lists/* >>> >>> There seems to be an issue with the package distribution. If I add >pip to >>> the installed packages and use it to force a reinstall of Trac, then >the >>> problem goes away: >>> >>> RUN apt-get update; apt-get install -y \ >>> apache2 \ >>> libapache2-mod-wsgi \ >>> libapache2-mod-svn \ >>> subversion \ >>> python \ >>> * python**-pip \* >>> trac \ >>> rsync \ >>> ; \ >>> rm -rf /var/lib/apt/lists/* ; \ >>> >>> * pip install --force-reinstall Trac==1.2.3* >>> >>> The problem with this solution is that python-pip carries a lot of >>> baggage with it (compilers, developer libraries, etc.) >>> >>> Perhaps there is a missing dependency in the trac.deb package? >>> >> >> I've seen the behavior during development and reinstall has always >fixed >> the issue, as you've noted. I'm unsure about the cause. >> >> Maybe a diff of the files installed by apt-get vs pip would provide a >clue? >> >> Another advantage of installing with pip is that you can get the >latest >> Trac, 1.2.5 or 1.4.0, rather than relying on the Debian package >managers to >> update the distribution. >> >> - 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 view this discussion on the web visit >https://groups.google.com/d/msgid/trac-users/e702bc84-b634-4459-af0d-94c954ae066d%40googlegroups.com. Just to throw in a thought: Would providing Trac DEB-packages be useful? I've been a couple of times before near doing some serious Debian developer work but never did the final step. Recently I've moved to a rather powerful private cluster computing structure, that would benefit from useful tasks like building packages. So how do your, Ryan, and others feel about a repository, that could provide more recent Trac and even development versions via apt rather then pip & Co.? Steffen Mit freundlichem Gruß Steffen Hoffmann -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/003E17EE-5D0A-4772-8206-A96E10190591%40web.de.
Re: [Trac] Re: [Trac-dev] Re: german translation
Am 26. Juli 2017 08:42:43 MESZ schrieb RjOllos <rjol...@gmail.com>: > > >On Tuesday, July 25, 2017 at 4:02:20 PM UTC-7, RjOllos wrote: >> >> >> >> On Friday, July 21, 2017 at 8:51:54 AM UTC-7, hasienda wrote: >>> >>> Am 10. Juli 2017 22:44:40 MESZ schrieb RjOllos <rjol...@gmail.com>: >>> > >>> > >>> >On Monday, June 26, 2017 at 11:29:16 AM UTC-4, Jörg Schulz wrote: >>> >>> ... >>> >>> >> Another question: if the pot-files at transifex are up-to-date, >are >>> >they >>> >> pulled >>> >> automatically before a release or is this in all cases the duty >of >>> >the >>> >> committer? >>> >> ( >>> >> >>> > >>> >https://trac.edgewall.org/wiki/TracL10N/Transifex#Translationteamcoordinator >>> >> ) >>> >> >>> >We've left it to the translation team coordinator to update the pot >>> >files >>> >in the repository from Transifex. However, there are only one or >two >>> >languages getting updated at present and we need to update the >process >>> >so >>> >that the files are pulled from Transifex automatically. >>> > >>> >I haven't worked with Transifex, but it would seem to me that the >least >>> > >>> >complicated thing to do would be to have all translation activity >done >>> >on >>> >Transifex and then just pull the pot files to the repository at the >>> >time of >>> >release. >>> >>> Syncing i18n stuff from time to time with Transifex has been the way > >>> Christian Boos did it before. He proposed a workflow, that should >still >>> work. >>> >>> I assisted Felix Schwarz in managing Tracs German translation >before. If >>> you, Ryan, get updates message catalogs, i'll try to help with i18n >issues >>> again as well. >>> >>> Steffen Hoffmann >> >> >> Thanks, Steffen. >> >> I will prepare a branch within the next few days and let you know >when >> it's ready for review. >> >> Regards, >> - Ryan >> > >For 1.0-stable I updated the catalogs and pulled the changes from >Transifex. I then pushed the updates to Transifex. >https://trac.edgewall.org/changeset/16145 > >However, I'm unsure about the changes pushed back to Transifex. It >seems >like there are still differences for the message.po file. > >Could you guys please review the changes? If it looks good I'll do the >same >for 1.2-stable and trunk, and then translation work can continue on >Transifex. > >I made a backup in case the changes need to be reverted on Transifex. > >- 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. Using Transifex before I remember hard times merging their changes, because there where always some I did not agree to. I think we'll need to find a way for the rather lange number of rather big msg catalogs for Trac, programmatically. Steffen -- 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.
[Trac] Re: [Trac-dev] Re: german translation
Am 10. Juli 2017 22:44:40 MESZ schrieb RjOllos <rjol...@gmail.com>: > > >On Monday, June 26, 2017 at 11:29:16 AM UTC-4, Jörg Schulz wrote: ... >> Another question: if the pot-files at transifex are up-to-date, are >they >> pulled >> automatically before a release or is this in all cases the duty of >the >> committer? >> ( >> >https://trac.edgewall.org/wiki/TracL10N/Transifex#Translationteamcoordinator >> ) >> >We've left it to the translation team coordinator to update the pot >files >in the repository from Transifex. However, there are only one or two >languages getting updated at present and we need to update the process >so >that the files are pulled from Transifex automatically. > >I haven't worked with Transifex, but it would seem to me that the least > >complicated thing to do would be to have all translation activity done >on >Transifex and then just pull the pot files to the repository at the >time of >release. Syncing i18n stuff from time to time with Transifex has been the way Christian Boos did it before. He proposed a workflow, that should still work. I assisted Felix Schwarz in managing Tracs German translation before. If you, Ryan, get updates message catalogs, i'll try to help with i18n issues again as well. Steffen Hoffmann -- 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.
Re: [Trac] Re: Account Manager Plugin
Am 18. Juli 2017 01:01:39 MESZ schrieb RjOllos <rjol...@gmail.com>: > > >On Monday, July 17, 2017 at 4:31:23 AM UTC-7, david.johnstone wrote: >> >> Ryan, >> >> >> >> I have changed the trac logging to DEBUG. Below are the last few >lines of >> the log file. The log is from running tracd. Get the same result >when >> using Apache. Tracd is on port 8080 and Apache is on port 80 >> >> >> >> Full log file is attached. >> >> >> >> 2017-07-17 21:19:23,313 Trac[main] DEBUG: Dispatching >> "GET '/login'"> >> >> 2017-07-17 21:19:23,328 Trac[main] DEBUG: Chosen handler is None >> >> 2017-07-17 21:19:23,328 Trac[session] DEBUG: Retrieving session for >ID >> u'david' >> >> 2017-07-17 21:19:23,328 Trac[chrome] DEBUG: Prepare chrome data for >request >> >> 2017-07-17 21:19:23,345 Trac[main] WARNING: [172.16.12.197] >HTTPNotFound: >> 404 Not Found (No handler matched request to /login), >> "GET '/login'">, referrer 'http://win-trac-2.locata.com:8080/trac' >> >> >> >> Cheers, >> >> David J. >> >> >> >> >> >> *From:* trac-users@googlegroups.com >[mailto:trac-users@googlegroups.com] *On >> Behalf Of *RjOllos >> *Sent:* Monday, 17 July 2017 3:55 PM >> *To:* Trac Users >> *Subject:* Re: [Trac] Re: Account Manager Plugin >> >> >> >> >> >> On Sunday, July 16, 2017 at 9:49:55 PM UTC-7, david.johnstone wrote: >> >> Ryan, >> >> >> >> Have installed r16714 and now get a message “No handler matched >request to >> /login”. >> >> >> >> The line in the trac log file is. >> >> 2017-07-17 14:44:59,489 Trac[main] WARNING: [172.16.12.197] >HTTPNotFound: >> 404 Not Found (No handler matched request to /login), >> "GET '/login'">, referrer 'http://win-trac-2.locata.com:8080/trac' >> >> >> >> Cheers, >> >> David J. >> > >You also need the following in your [components] section: >trac.web.auth.loginmodule = disabled > >I'll update the CookBook wiki page. > >- 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. This is one at least not critical. acctmgr will always check and fix configurations missing that, and it will be saved with other changes next time. Steffen Hoffmann -- 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.
Re: [Trac] Account Manager Plugin
acct_mgr.pwhash.* = enabled should get you started, until you understand more acctmgr internals. Bzw, you shouldn't start using md5 hashes but daher use sha256, if there no very good reason against it. Greetings, Steffen Hoffmann -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -- 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.
Re: [Trac] Re: Trac.ini
Am 9. Juli 2017 22:13:00 MESZ schrieb toto200891 <syedfarathsay...@gmail.com>: >Yes. is it possible? > >Regards, >SF > >On Friday, July 7, 2017 at 8:26:30 PM UTC+2, RjOllos wrote: >> >> >> >> On Friday, July 7, 2017 at 10:57:15 AM UTC-4, toto200891 wrote: >>> >>> Hi >>> >>> Could you somebody please tell me like how to have a whole trac.ini >file >>> within the trac environment? >>> >>> Regards, >>> SF >>> >> >> I'm unsure what you mean by "whole trac.ini file". >> >> - 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. We'll try to help you, if you need more than what our documentaton already covers. So please start by reading https://trac.edgewall.org/wiki/TracIni Hope, the global config section will already tell you much. Greetings, Steffen Hoffmann -- 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.
Re: [Trac] Re: Trac.ini
Am 7. Juli 2017 20:26:30 MESZ schrieb RjOllos <rjol...@gmail.com>: > > >On Friday, July 7, 2017 at 10:57:15 AM UTC-4, toto200891 wrote: >> >> Hi >> >> Could you somebody please tell me like how to have a whole trac.ini >file >> within the trac environment? >> >> Regards, >> SF >> > >I'm unsure what you mean by "whole trac.ini file". > I think, he's aiming at one central INI file with settings inherited by multiple Trac environments. Steffen Hoffmann -- 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.
Re: [Trac] Is it possible to turn off the wiki messages?
Am 15. Juni 2017 13:39:03 MESZ schrieb Jurgen Defurne <jurgen.defu...@gmail.com>: >I find the message boxes which pop up when I save a wiki page annoying. It sounds obvious as you write it, but I can't remember dealing with obsolete Trac messages. They popped up for good reason. So please give an example. >Is there a possibility to turn them off somewhere? Might be even in the >code or the templates. If it's no error message, sure, it depends on the source. A template modification would be preferred over some custom code patching, oft course. Steffen Hoffmann -- 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.
Re: [Trac] Ticket query
I found two issues while reading your code and message: Make sure to have the permission action named as you desire. In your message you spoke about 'TICKET_VIEW_STATUS' while it was written as 'TICKET_VIEW_STATUS' in code. For ticket status you'll need to compare to a string, so write it quoted like 'test' or "test". Steffen Hoffmann -- 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.
Re: [Trac] Custom policies
Am 2. Mai 2017 14:06:31 MESZ schrieb toto200891 <syedfarathsay...@gmail.com>: >Hello, > >I have a question related to custom policies. I am trying to define a >permission that allows a user to view the tickets only reported by him. >I >followed the steps in >https://trac.edgewall.org/wiki/CookBook/PermissionPolicies#SupportDeskPolicy > >and created a egg file using setuptools and copied the egg file in >plugin >directory > >and also granted the permission TICKET_VIEW_REPORTED > >But I still see that the user can see the tickets created by other >users >and also modify it, though the permission like TICKET_VIEW is been >revoked >from that user. Are you sure, the user in question owns no other TICKET_* permission, that inherits TICKET_VIEW? Even if you checked this yourself, I would rather double-check that before looking at your custom permission policy implementation. Greetings, Steffen Hoffmann -- 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.
Re: [Trac] Create new users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.07.2015 13:52, Nuno Ranito wrote: Thank you for the help... is there an easy fix that doesn't require updates? Fix for what? As outlined before your .htpasswd file has been corrupted by issues of the account manager plugin in auth store chaining mode. At the very least you'll need to fix the configuration suitable for your plugin version to no longer attempt to share one file. It means removing invalid stores (one of HtDigestStore and HtPasswdStore) and corresponding lines in the password file. Nevertheless upgrading is preferred, because we've not only fixed this issue, you see? Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlW8wYMACgkQ31DJeiZFuHf+HwCgjdDO5g5kzuPQb7hptxnLuAvK qZgAn2Ri46eS2kCzr7es3xI4npYq1uUN =+QWC -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Create new users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22.07.2015 15:55, Nuno Ranito wrote: Trac.ini file [account-manager] account_changes_notify_addresses = authentication_url = force_passwd_change = False hash_method = HtDigestHashMethod htdigest_realm = /home/trac/trac.htpasswd htpasswd_hash_type = crypt notify_actions = password_file = /home/trac/trac.htpasswd password_store = HtDigestStore,SessionStore,HtPasswdStore persistent_sessions = False verify_email = False HtDigestStore and HtPasswdStore cannot share a file. For chaining them sanely you must specify separate file paths for each of them. Therefor dedicated options have been introduced in v0.4 of the plugin, and you shouldn't use anything earlier than 0.4.4 right now. htpasswd_file - '/home/trac/trac.htpasswd' goes in here htdigest_file - '/home/trac/trac.htdigest' or similar goes in here htdigest_realm - is for the hash-prefix, not the file path This explains the wired file content! password_file is depreciated and not used since v0.4 by any of your configured authentication stores. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlWzNngACgkQ31DJeiZFuHf4YACfSNVLybf7CufdnsEalNd9w4i8 OdQAn0I97FkxWLbbfpMSx2nf3WBYZ5Ef =lFJI -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Created Modified timestamp formatting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.07.2015 13:56, Mo wrote: Hi, is there a way to edit the created and modified timestamp formatting in ticket lists? This is currently the elapsed time, but simetimes it's more useful to have absolute timestamps, which can be sorted. Browse to preferences page, so you can choose the relative vs. absolute time stamp format for that UID/session. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlWoBZkACgkQ31DJeiZFuHdcQQCfWKNqjjuBsms9EkV5pmPel/fb KX8AoNe+WYOjJE6rqUM4Ju/Dra1epKAI =tRUw -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Status sorting in ticket list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.07.2015 18:56, Ryan Ollos wrote: On Thu, Jul 16, 2015 at 4:49 AM, Mo burcheri.mass...@gmail.com mailto:burcheri.mass...@gmail.com wrote: Hi, if sorting for status in the ticket list this appears to sort alphabetically like accepted, closed, new. A workflow sorting would be more appropriate here like new, accepted, closed. It this already possible or worth a bug report? Best regards. Only alphabetical sorting is possible in the Report and Query views. While there is an intuitive ordering for the 3 states you've shown, it's not clear what criteria would actually be used to sort them. Consider a moderately more complex workflow. What is the intuitive ordering, and what the algorithm be to determine the ordering? http://trac.edgewall.org/wiki/TracWorkflow#Environmentscreatedwith0.11 No algorithm, but I remember using the nearly undocumented action.weight option for sorting actions in ticket view (see docstring of ITicketActionController.get_ticket_actions method [1]). IMHO the same ordering sould be considered for an alternative sort. Steffen Hoffmann [1] http://trac.edgewall.org/browser/tags/trac-0.11/trac/ticket/api.py#L42 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlWoBMMACgkQ31DJeiZFuHdXKACgpkx2ausjbu/mx3vrTgpKvNiS SoMAoJBqMB/O4SGu6aCxutBWylqUyK8A =bhZR -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Create new users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.07.2015 15:34, Nuno Ranito wrote: I checked the trac.htpasswd file and I see that some users have lines like userName:password (this one accesses trac) and others have username:/home/trac/trac.htpasswd:password* (this one cannot access trac) What is the difference, and why this happens?? *something encrypted? The first type of entries is expected for htpasswd auth file store (user:passwd-hash), the second line is clearly an accident, maybe something related to htdigest (user:realm:passwd-hash), like was suggested before, at best. You should be able to update each users entry via the users admin web-ui provided by account manager plugin. Your trac.ini settings regarding account manager components and plugin related section [account-manager] are mandatory to help resolving the mystery around these wired entries. Can you remember and explain a bit more, how these entries have been created in that file? Some history with concurrent HtDigestStore would explain a lot, albeit it has been fixed for ages now. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlWm2C8ACgkQ31DJeiZFuHdhDACfUQs+edwWbZqTwKOqLmTLzOPd 3psAnRHEs/RrlYfFsLjF2g7XDuJFQGJq =3iun -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] How to rename users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.05.2015 16:23, Mo wrote: Adding acct_mgr.model.* = enabled did not help either. However from the debug log, the right plugin is loaded, but there is no component acct_mgr.model It might be worth looking for a small (i) sign in the web-UI, that should explain, that UID change support is not available. Apart from UID changer components there is more about the UID change, especially it relies on password reset enabled an working too [1]. My own recent tests regarding this issue indicate, that it might be too hard by now to accomplish a working setup. Comments and suggestions welcome. Steffen Hoffmann [1] https://trac-hacks.org/wiki/CookBook/AccountManagerPluginConfiguration#PasswordReset -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlVdEF4ACgkQ31DJeiZFuHfIDwCeJFy+Z2SR7wEjzdyAmK7Oxjfe sPcAmgLN+2igqne0FhSK8ZvAgBnYoPLH =2ewk -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac 1.0.4, TracAccountManager 0.4.4 with SessionStore authentication
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29.04.2015 16:40, Mark Antonson wrote: I'm trying to setup Trac authentication with the AccountManager plugin. I'm running the FastCGI version through lighttpd's spawn-fcgi component, hosted through Resin 3.0 (don't ask, it's already on this server and needed to support another old application). ... I registered an account named admin and manually added the permissions per the cook book, but when logging in it takes the username and password but doesn't actually log you in, still browsing using anonymous. Set the trac logging to DEBUG and this is what I see in trac.log: | 2015-04-29 09:32:38,796 Trac[main] DEBUG: Dispatching RequestWithSession POST '/login' 2015-04-29 09:32:38,797 Trac[web_ui] DEBUG: LoginModule._remote_user: Authentication attempted for 'admin' 2015-04-29 09:32:38,799 Trac[web_ui] WARNING: LoginModule.authenticate: 'REMOTE_USER' was set to '' 2015-04-29 09:32:38,799 Trac[web_ui] DEBUG: LoginModule.authenticate: Set 'REMOTE_USER' = 'admin' 2015-04-29 09:32:38,801 Trac[session] DEBUG: Retrieving session for ID u'admin' 2015-04-29 09:32:38,862 Trac[main] DEBUG: Dispatching RequestWithSession GET '/' 2015-04-29 09:32:38,863 Trac[session] DEBUG: Retrieving session for ID 'd8350ff6f918db420e1197ec' 2015-04-29 09:32:38,870 Trac[chrome] DEBUG: Prepare chrome data for request | So it appears an authentication is starting, but the REMOTE_USER is being lost. After researching, I thought I'd found a solution in setting the environ_auth_overwrite = false, but then the login fails with Invalid username or password. The trac.log shows: Why should this become a solution? The authentication has been going well as before, far as it could on Trac and accountmananger side. I've not heared anything about that Resin server software and how it could be configured to pick-up the 'REMOTE_USER' authentication result on the server side, but this is what as to be done now I guess. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlVBOPwACgkQ31DJeiZFuHcFdwCfW1zZnfWHrJTdULM+nIeyIEju hhgAniW5qExo9GX/UDLkSC9J4EJMTvem =ykAm -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Validate custom field before saving ticket
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.04.2015 22:52, RjOllos wrote: Another approach would be to have TicketValidatorPlugin add a label on an empty field, and an empty field in the case that the field doesn't allow the empty value. This would avoid creating dummy values like your Component --- Please choose a state --- Nice idea. I've often seen trailing (red) star behind a required input field label as visual sign for required input. If others agree, that this is sufficiently common, it could become a Trac default visual style too. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlUsNZEACgkQ31DJeiZFuHf+sgCg0bUNtKvgtIhLgbGbljbg5yV0 5h4An20zyk+wYO7KJN76Mahww4Gdpjbw =Bnz0 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Mandatory fields
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.03.2015 20:13, pineapplehandler wrote: continuing: I'm still struggling to understand how the... [fieldscheck] and [ticketvalidator] entries in trac.ini are passing their values to the code, but I think all I need is some time to understand it. Generally you should rather write below previous message's text. Avoid top-posting, because it effectively ruins reading flow (top-down for most languages). On you current topic: There are definitions you can use to establish know configuration options. Look at Option and friend in trac.config. Furthermore you'll find many examples, where options are declare in a plugin class. These options are then made class attributes, and you can read their current value by calling either self.option_name or self.config.get(section, option_name) Note that configuration changes applied permanently will trigger Trac environment reload (incl. configuration). Hope, this will get you make it a bit easier for you. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlUVxxUACgkQ31DJeiZFuHczNgCfX+krHwKFYM+nRhkBnfw4+ul0 C+QAn1OBaZMd63n3YYP0WiiNPPJl5rF0 =Xwax -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: LDAP plugin advice, user details
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.03.2015 22:33, pineapplehandler wrote: Our use case was to utilize the Assign-to as Drop-Down List http://genshi.edgewall.org/wiki/TracTickets function for users who haven't logged in yet. I see. In Trac core this drop-down list is populated from *authenticated* user/session records only. I cannot see, how you could make it come true without faking authenticated sessions, like AccountManager does for administrative account creation. How did you mean to provide user IDs, a list or sort of an all known users query to LDAP, if that can work at all? Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlUR570ACgkQ31DJeiZFuHdobwCgzKsXePgQfB7B8xsNb3AHtf7E 99sAn3dhFG+X0aRJ8CYpo3MmtXRmnyDB =eDzR -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: LDAP plugin advice, user details
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.03.2015 15:20, pineapplehandler wrote: We'd like to pre-populate our users and email addresses from LDAP. Is this something that's been worked out already? Sorry, but all I've ever seen has been per-request (session) runs. IMHO there's nothing like an administrative user mass-creation tool. Anyway I'd still like to understand your use case a bit more. Since there's no distinct user object in Trac until now, it only takes a successful authentication request and a pull of suitable attributes like email on-success to establish entries forming a permanent representation of an authenticated session/user ID in the Trac database. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlURzy0ACgkQ31DJeiZFuHf0tACfXimDQf0hNPHIS04oYRzTkXIG Y74AniQSN+rIYl8YhLDkElEB5G/JbaQ+ =Hqba -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac 1.0 + Bitten + mySql Lite Support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.03.2015 20:27, tolu...@gmail.com wrote: Ok. Here is the debug log output for three pages that took ~10 seconds to load each. This is on the faster side of loading times. As you can see, trac has to restart itself everytime it loads a new page. TracAccountManager-0.4.3 could be upgraded, but it shouldn’t make any difference for your situation. While Trac env reload 'only' takes approx. 5 s of the total request processing time, this is not only much too slow these days, but the cause for the reload should be determined in the first place. This is certainly no near normal Trac behaviour. Did you already try to debug by deactivating plugins one-by-one to find the culprit? Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlUAoVcACgkQ31DJeiZFuHeNOACfUHyglH645g5h8uPIf7pBWUtu HPcAoKxtrZfjwcQt3ZYaxVWUrjCBLM3g =LmnU -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac 1.0 + Bitten + mySql Lite Support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.03.2015 18:30, tolu...@gmail.com wrote: On 03/11/2015 01:24 AM, tol...@gmail.com wrote: - There are about 1000 tickets, and about 50 users. Eeep... we couldn't get past 5 users on SQLite. SQLite has very coarse locking, so it would lock whole tables and users would get errors. We switched to PostgreSQL (not my favorite, but MySQL support was pretty new at the time) and things got loads better. Hm, I'm running past 10k tickets with a lot more than 5 users on SQLite by now, and this is not even latest Trac stable but plugins mostly still using the depreciated Trac 0.11 db API. I think *concurrent* user requests are the issue, not total number of registered users, and ticket count might be not much of an issue in general. Still I'm approaching SQLite to PostgreSQL migration myself. While I foresee quite a bit more procession overhead for the PostgreSQL backend, it will certainly help with the locking issues, that are nasty with SQLite indeed. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlUApJQACgkQ31DJeiZFuHdppgCfZpC79ubGfztrpfGwOds347KM g0gAoLde72klU9pOp2a9xd9AXxXUiuSf =oJ4e -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Translate users from svn with account-manager to Git with wsgi/LDAP-authentication
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09.03.2015 09:54, Mattias Vannergård wrote: I have, sorry to say, no clue where it went wrong. Your positive feedback is appreciated, since it adds another successful real-life test of upcoming new user ID change support, that encourages next account manager release, thanks. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlT+HTsACgkQ31DJeiZFuHeuTwCfTkKUhXLL+xomg39GhuF4F+94 u8wAoJlRav3Svf4l+r/TgOvImdhh1Bg7 =EpZ3 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Change user name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06.03.2015 21:41, Ryan Ollos wrote: On Fri, Mar 6, 2015 at 2:55 AM, Mattias Vannergård mattias.vannerg...@gmail.com mailto:mattias.vannerg...@gmail.com wrote: Hi! According to, amongst other, this thread https://groups.google.com/forum/#!searchin/trac-users/change$20user/trac-users/lpA2qSWgOPM/Ok7EesP7ATIJ it seems like a non-simplistic task to change the user id in a trac db. I have written a small C#-program that does this, if anyone is interested. Or if anyone knows a current plugin, you may feel free to share. BR /Mattias It could be nice if AccountManagerPlugin supported this, but it seems unlikely that it would be widely used, and as the other thread noted, it's not entirely trivial to implement (which you likely found when writing your C# program). Sure, this is not trivial, and maybe I don't get it by now, but what about current functionality in AccountManagerPlugin [1] trunk? Isn't it just what you're asking for? Steffen Hoffmann [1] http://trac-hacks.org/ticket/10945 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlT6SasACgkQ31DJeiZFuHdWdQCfQ7BW6mWwm2lALEm5JAC7WSXP 0EIAn2rbmU5dtLdqvxYk7kpvwHzRIdnF =UVqc -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: CommitTicketUpdater
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.03.2015 10:14, Mo wrote: However I'm using AnnouncerPlugin for mailing, does that conflict with the CommitTicketUpdater? No. These are both ticket change listeners, and as such they are separate tasks, that just get triggered one after the other on ticket change. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlT2FeUACgkQ31DJeiZFuHfhAgCeOOZFZSt+M40duxVRh1Bx+c9G Dx4AnjF2aaXlDjsd3yd7KpaPEloccos0 =LbsU -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Collapsible groups in custom query?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.02.2015 16:34, Cooke, Mark wrote: I am just looking at a custom query grouped by status and am thinking it would be nice to make each result group collapsible, just like the `Filters` and `Columns` sections. I see, and I know that from other systems, not Trac (yet). Does that sound useful to anyone else? I recommend to keep the list pager in mind. Only if there are results for more than one group at a given page, it would be sensible to collapse. I do not know a system, that does so automagically, but it is what I would expect from Trac, if such a feature would be implemented at all. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlTTyqIACgkQ31DJeiZFuHd4eQCfafsI3gr+SztfD651CQh3vjrf cfoAoIUMHq2dGCEtFtBuTeQ5sAxwdWXU =nwAm -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] PrivateTicketsPlugin issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.02.2015 16:46, Bj Fennell wrote: I wanted to restrict *Tuser* to only the tickets he/she reported, owned, or was cc'ed on. However for *Tuser2* I wanted him/her to see any and all tickets without making *Tuser2 *an admin. I have *Tuser *with *TICKET_VIEW_SELF *permission while *Tuser2* has *TICKET_VIEW_GROUP* permission. I believe I also have both *Tuser* and *Tuser2 *in a group called *EntireContract*. This should enable *Tuser2* to see any ticket that *Tuser *has reported , owned, or been cc'ed on, and yet when I create test tickets as *Tuser*, and log back in as *Tuser2 *I can't see any of those tickets. Not sure about this, but ultimately I believe it doesn't matter, for Tuser2. If you gave just TICKET_VIEW to Tuser2 he/she could see any ticket, that is pretty standard requirement and what you required too for that user. As long as there are not more requirements than what you told before, I see no reason for creating that EntireContract group and using TICKET_VIEW_GROUP at all. As an admin I can see all the tickets created by *Tuser*. When I login as *Tuser*, I see the tickets I am supposed to, and those that are restricted are invisible to me. Fine, but restricted by what means? If you mean 'neither created nor owned nor cc', well. Otherwise you should explain a bit more. But the *Tuser2 *profile doesn't seem to be able to see anything reported, owned, or cc'ed by *Tuser* Should be resolved by granting TICKET_VIEW to Tuser2 as stated above. If not, respond with more details, please. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlTTzmwACgkQ31DJeiZFuHc5dwCgsWqAFEBd0mz5P9Gtokh4YpXm vQcAoIn7G5fRV2eFjYON9SQjWLLbkIXr =ZA+p -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Wiki: How to create a table attached in the file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.01.2015 13:45, mimi wrote: Hi, I'd like to create 4x2 table (effectively 2x2, two rows I'd like to keep reserved as the names for every cell) into which I could split my content. I'd like to display this table on the main page. The aim is to have a better view on what is going on in the project without scrolling and clicking on links. The content of the cells could be a links, tables, other wiki pages, etc. What I'd like to stick to are the names for the cells which are presented as the test on the gray background. How to do that? Most flexible is WikiProcessor based table markup, and the only one capable of nesting one or more levels of tables inside. I trust you to find the correct syntax by looking at the corresponding wiki documentation [1]. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/WikiFormatting#Processors-example-tables -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlS28FgACgkQ31DJeiZFuHc4CgCfZsP6yzqA0xlm3gMDpZLK3UA6 VyAAnjkLwVNsTzQhsteHP7bAkmmGoOlf =4ajJ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Uploading files for Download
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.01.2015 12:15, Roger Oberholtzer wrote: line 52, in readline return self.req.readline(size) MemoryError I guess that you'll need quite a bit more RAM than the biggest file you try to upload on that machine. But this shouldn't be the problem in your case. May it be, that Python simply has not permission (process memory quota or similar restriction) to reserve enough memory for buffering the received data stream in memory? Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlS1irQACgkQ31DJeiZFuHfmqgCg5r1qtFmJxL1dTK69hEfNLdoh +LoAnRWS05u63vQcWw9ihqNCF+ZL7mdV =mErl -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] SQLite database question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.01.2015 07:45, Roger Oberholtzer wrote: Specifically, what I am trying to accomplish is updating a file in the file system, and then updating the date and size fields in the Trac download table to reflect this. If I could do this via Trac I would be happy. I'd implement some XMLRPC method [1] extending DownloadsPlugin [2] for altering the Trac db. Get an idea of how such an RPC implementation is done from another, recently added implementation [3] of that API. But I think this is not possible. Specifically such a thing like is not possible does not exist for a highly versatile, modularized CMS like Trac. :-) Steffen Hoffmann [1] https://trac-hacks.org/wiki/XmlRpcPlugin [2] https://trac-hacks.org/wiki/DownloadsPlugin [3] http://trac-hacks.org/changeset/13858/tagsplugin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSu4ssACgkQ31DJeiZFuHexDgCgxDXskJWs1kR41zQRQg2QffIP aYEAnjQICAd2nsfgUaU/hGuszq7pR456 =flUV -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Possible to render a specific log revision in ticket comment?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.01.2015 08:20, Leho Kraav wrote: On 03.01.2015 00:48, RjOllos wrote: On Sunday, December 21, 2014 3:47:49 PM UTC-8, Leho Kraav wrote: I'm thinking something like this for a macro [[Diff(repository:revision)]] Does anything similar to this already exist? th is taking about 5 minutes to load any page, can't check hack index. Just to be sure, you want to display the diff, and not just the log message? I haven't seen anything like that on t-h.o, but a Changeset macro would be a valuable addition to Trac. Yeah. It can be used for avoiding pasting code into wiki when documenting examples and also as a lightweight, model-free code review tool in ticket comments. With psuter's autocomplete magic from http://trac-hacks.org/intertrac/WikiAutoCompletePlugin picking a revision to use for the macro could be a really nice experience. Feels like most of the required logic is already in Trac core, but has to get rendered inline for the wiki macro call rather than dedicated changeset page. If it was so smart to accept a path as optional argument, one could display exactly what is shown at corresponding Trac browser pages when showing diffs reduced to a directory or file. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSnng8ACgkQ31DJeiZFuHfV4wCgxw85Fd9/5Vto5wibIPuDhtEy r2sAnj7U8Fcg8FamzdCghg0pRAjF9pxf =QMyJ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Update problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30.12.2014 12:04, RjOllos wrote: I gave a bit of thought as to whether to make the change on 1.0-stable or the trunk. I gave more weight to the issue being a potential security concern, and figured that users might see an error when upgrading regardless of whether it's a major or minor release. I think, this was the right decision. IMHO Rogers response made clear, that it was a problem on his side not reading changelogs and not understanding the rather clear note. You could hardly give clearer feedback, because instructions how to fix the issue are already there. You don't attempt to make reading and proper admin reaction obsolete, do you? ;-) Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSi7t8ACgkQ31DJeiZFuHdX+wCbBGSeR/Smmmq9ACIFQRocqJfV TikAn0ScxQVVuo1oovb6A10cRzAOahtW =LI8d -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] a problem when sychronizing svn repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.12.2014 09:28, 董乾林 wrote: * Look in the Trac log for more information. i don't know what's wrong. can any one help me with this warning which is exactly an error. So did you look into the log file yet? Btw, you should set DEBUG logging level [1] for seeing all hints there. And you could even find dedicated information on setup and management of repositories in your Trac wiki [2]. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracLogging [2] http://trac.edgewall.org/wiki/TracRepositoryAdmin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSXIHcACgkQ31DJeiZFuHd7rACeLSmVtrB/9s7+yg6okHVsuDYY DEIAoIP755W1vJftpnGLvFS17f+mvV67 =pI51 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Trac interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.12.2014 09:08, stephan nathanael wrote: i want to use customized interface in trac ? how to do that ? On Monday, December 15, 2014 3:34:59 PM UTC+3, stephan nathanael wrote: hi Trac users , Am using trac 1.0 and i tied to work on Trac and i face a problem almost a week now on how i can connect trac from its templete folder there is lot of ways i tied but without sucssesfull can any one help me with simplest way possible please . link am using to connect is as follows http://trac.edgewall.org/wiki/0.11/TracInterfaceCustomization http://trac.edgewall.org/wiki/0.11/TracInterfaceCustomization thanks for your support. i hope my problem is already solved. I can't see exactly what problem you have with following the wiki guide about Trac interface customization [1]. You speak about connecting something, but it is just modifying Genshi XHTML template(s) and adding a custom style sheet. Furthermore you did not state the Trac version you use. Not that it would matter much for this issue, but never start a new project on ancient Trac install like 0.11, but use at least current stable v1.0.2 instead. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracInterfaceCustomization -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSR5mwACgkQ31DJeiZFuHe56gCgn//bhkeARhj7qdodA51Plg8x gC0AoJ2sj2AGXGYzQe+vVWfv1HAtZxLm =WnVn -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.12.2014 13:34, stephan nathanael wrote: on how i can connect trac from its templete folder Maybe its just me, but I cannot understand that. Not much to answer by now. What exactly do you want to do? Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSPT/cACgkQ31DJeiZFuHdTtgCfVSFNMyVOFkhW4ZFc78GcCL8c 62cAoIrzo7oud5aQqnHR2r99gBrsAlXl =pZ+i -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Table Cellspacing in Trac Ticket
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.12.2014 22:02, Kristen wrote: Hello, When adding a table to the description textbox of a trac ticket, is there a way to format the spacing between cells? ... This does not happen when creating a table in a wiki page, only in a trac ticket. This doesn't happen in Trac 1.2dev too (1.1.1 here), so I think, this is an issue with older Trac versions and a fixed one after all. Or your setup has some relevant custom style definitions in place. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlSHIVIACgkQ31DJeiZFuHf4hgCeKQFIURM0OHi1JD3YPJVaKQtj IrkAn1AjwyyDjEYGaWZlm2ml5ctRUDc7 =scQS -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] multiple ticket templates in one environment?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21.11.2014 21:19, Kevin Crilley wrote: Does anyone know how to create multiple ticket formats in one environment? I think it is just ticket type, probably enhanced by DynamicFieldsPlugin [1] and/or TracTicketTemplatePlugin [2] If not, we will need more details about your requirements to help. Steffen Hoffmann [1] http://trac-hacks.org/wiki/DynamicFieldsPlugin [2] http://trac-hacks.org/wiki/TracTicketTemplatePlugin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRwR+UACgkQ31DJeiZFuHdGCQCgzXft9fSOD5TywP0n/nlrnaLT Be0An3wZ61hvuDnGArPl2lIgZdrhzElV =o9Aj -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Can anyone tell me what I've done? Trac is now broken...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22.11.2014 11:46, Ron Kyle wrote: Can anyone tell me what the heck is wrong, or really just how to go about fixing it? You did not provide much to us yet, and I really hope you know more than you told us by now. To fix the project you'll need to go to the place, where most project content lives by default: the Trac environment directory. It is right, if you see folders like /config, /db, /log, /files (or /attachments for older Trac versions) /plugins and /templates inside it. Go to /plugins and try to delete anything not looking like a Python egg or simple Python skript file (*.py). Something like 'setup.cfg' or 'setup.cfg' certainly doesn't belong there. Restart you web server, and you should be already back in the comfort zone. And never try installing Trac plugins without a clue on the underlying system layout again but read more on TracPlugins ASAP. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracPlugins -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRwi1IACgkQ31DJeiZFuHfATACguqz+km9bkHEd4Y0KWvYVV1bF bJcAoJPBi95zHKJw0CH7/J+NwmGdx/xA =AVmj -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] TICKET_MODIFY permission acting like TICKET_ADMIN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.11.2014 20:57, Shawn Baker wrote: It seems odd to me that anyone who is authenticated in the system can change the status of any ticket as they see fit. Less restriction doesn't yield a mess automatically. Fact remains, that this is how it works for a good number of projects. Personally I know community-driven as well as commercial ones, but the number of authenticated users varies a lot between all of them. The critical point is, that you can track changes all the time. Trac (timeline with RSS feed, individual change ticket/wiki/.. history) also with RSS feed, these are powerful ways of social control in good wiki common sense that work. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRuTtcACgkQ31DJeiZFuHf6ngCdFw6oisLgXwvW/52EySIzXgRp 5PEAnjTAYvuZE2qrK7N8++NSowgfzsKx =lVpy -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Cannot access /Project/login/xmlrpc from Trac installation (with HTTP Basic authentication)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.11.2014 21:28, quasiroot wrote: What else can I try? Sure you know, that XMLRPC requests for priviledged actions have to go through authentication individually? So you need to provide appropriate, valid credentials for each request. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRuUg4ACgkQ31DJeiZFuHdEiQCgvkQs8Umf0ySi9NLlwTrH2XW/ sHMAnj5icY4CTFU/s8glYBpR4lMSS2T7 =U6Df -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] trac-admin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.11.2014 23:30, ONeal Freeman wrote: Believe it or not I seem to run the ticket remove command a lot. It is the preference of my department to delete the ticket instead of marking it invalid or wontfix. Your department rule, but I doubt this policy will either encourage contribution of tickets (hey, they just delete them as they like) nor help in understanding, what topics are inappropriate for tickets (hey, they just delete them as they like) nor identify demand based priority (dunno, if we already had that question twice, we just delete duplicates). Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRoVSQACgkQ31DJeiZFuHev1QCg3Epz8qbBgaaQjy6oUTF9fWUM TAIAoMwTOdsT5d9qT94EQDk5iUXb1ifW =MDER -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Can Trac Hidden Project List?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.11.2014 10:35, 柯餅乾 wrote: Hello everyone, I'm a new user for Trac. I have a problem that how can I make a distinction for different user to display different project according to their different permission. And how to hidden the project that the user doesn't have the permission on those. We had this question before (should be in the mailing-list archive). This is neither default nor optional Trac core behavior, and due to permission definitions on 'project level' it would require a) authentication prior to/at the project listing page b) checking permission for each project by reading their Trac db for every access to the project listing As your boss or yourself, what it is really worth. It could be done by a separate script. Don't remember yet, if someone already published a solution before, sorry. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRkgfIACgkQ31DJeiZFuHeaGgCg6NEC4ONQzcEIpRg0QRkuvSCG ejgAoNsFmC9KlDvmmNfCq/PDApTfLCyR =otX3 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Needing Urgent Help!!!! Traceback
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.11.2014 22:10, Richard Smith wrote: I seemed to have broken one of our main links in TRAC our Admin Link. Our primary directory labeled NOVA is spitting out this message whenever I try and access it. The story behind this is I was trying to load a plugin and accidentally clicked on the API.py and now I'm getting this whenever I try and connect to that link. I cannot simply load from our backup because coworkers have been writting to it all day. (Heaven, who let that guy fiddle with a production Trac server without a big picture of the installation, not even a plan for restore in case of failure?) I really hope that you're not as clueless as these lines look like. Trac is rather well self-documented, and you could find out about Trac db and file storage rather easy on your own. My question is how can I go about fixing this? If data is stored on the D drive then I could just reload the C drive and be alright (The other projects are on the D drive) I am not sure how TRAC saves their information regarding tickets though and am quite hesitant to take do that in the case of losing a days worth of work. I amextremely green when it comes to TRAC. Our TRAC does work but it is limping. I hope this is enough information for you guys and hope to hear from you guys soon! Hm, without knowing much about your server setup I guess it is ... Traceback (most recent call last): File C:\Program Files (x86)\VisualSVN Server\trac\python\lib\site-packages\setuptools-0.6c11-py2.6.egg\pkg_resources.py, line 201, in get_provider __import__(moduleOrReq) ImportError: No module named tracusermanager just that you destroyed/movered/removed UserManagerPlugin, or just did replace but not restart the server properly after updating the egg. Looking through all files named trac.ini tells you the exact locations of db and file storage, and ultimately answers your question, if D.\ is really all Trac environments home or not. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRlLBcACgkQ31DJeiZFuHdfoQCfSvdBUCFoa2fXDAsAqc2nMZku MMMAoNgempq7NBmoV2i8gE5EOcslmYdI =UZ9T -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Following up TracAccountManager Plug in - Ticket 12055
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.11.2014 17:56, Pablo Eduardo Hernández wrote:
Hi!
Following up on ticket http://trac-hacks.org/ticket/12055
http://trac-hacks.org/ticket/12055
I'm trying to install account manager plug in on RHEL 6.6.
Apache version is 2.2.15
{{{
Command that I execute to install was:
easy_install https://trac- https://trac-/
hacks.org/svn/accountmanagerplugin/tags/acct_mgr-0.4.4
http://hacks.org/svn/accountmanagerplugin/tags/acct_mgr-0.4.4
}}}
Trac is working, and Admin tab is showing, however there's no Account
section on the left menu?
I need advice with this one!
You likely need to explicitly enable all/desired modules to make them
work (see our configuration examples collection [1] for details).
Steffen Hoffmann
[1] http://trac-hacks.org/wiki/CookBook/AccountManagerPluginConfiguration
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlRhNxMACgkQ31DJeiZFuHeXYgCfdULUn9Qj+99SZsftnswiUz+m
KmEAn06Oq2qMHDqI5/ypADpbMaSAPE4e
=ptsG
-END PGP SIGNATURE-
--
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 http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
Re: [Trac] How do I rename a wiki hierarchy entry?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06.11.2014 20:05, Peter Suter wrote: On 06.11.2014 01:45, mham...@sandia.gov wrote: I've searched the archive for old posts relating to rename, and checked the wiki on the edgewall site, and all seem to indicate that the rename capability was added in version 0.12. What am I doing wrong? How do I get Trac to change 'Tools' in the wiki hierarchy to 'NewName'? Unfortunately hierarchical renaming isn't implemented yet. The relevant ticket is #4412. http://trac.edgewall.org/ticket/4412 There is still WikiRenamePlugin, that is capable of renaming all wiki pages in a 'hierarcy' as side-effect. When this is intended, it should work even better than current core wiki-rename function. Just note, that you need to have support for any additional plugin store, that relates to wiki pages, such as FlexibleWiki [2] and Tags [3], but I have unofficial patches to provide this, if you care. Steffen Hoffmann [1] http://trac-hacks.org/wiki/WikiRenamePlugin [2] http://trac-hacks.org/wiki/FlexibleWikiPlugin [3] http://trac-hacks.org/wiki/TagsPlugin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRdQz4ACgkQ31DJeiZFuHfksQCgib3IzAQuIS4GoUtOKI9HNM0A OFoAnjzr9vzND6qFFKNEszNi0tn+U+3V =ZAkZ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Nessus able to create user in Trac
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Dave, thanks for taking care to contribute your thoughts and share development results with us. On 05.11.2014 17:33, Dave Love wrote: RjOllos rjol...@gmail.com writes: For reference, solutions have been provided in: http://trac.edgewall.org/ticket/11803 http://trac-hacks.org/ticket/12047 For what it's worth, I've just had spam accounts created, despite the AcctManager BotTrapCheck. I wanted something like TracQuestionRegister, but that no longer works. For reference here you referred to QuestionRegisterPlugin [1], correct? For what it's worth the expected incompatibility of this hack with current accountmanager versions has been reported [2] early, including an offer to assist on new API adoption. Seems like the hack is currently unmaintained. I hacked up this change to the current AccountManager to ask a project-specific question (What's the command to ...) which should be more robust. I'll try to contribute it if trac-hacks will talk to me sometime. Your patch submission enables inclusion of the functionality of QuestionRegisterPlugin into accountmanager, that has been blocked by the incompatible licenses before. I assume that you agree to put you patch unter accountmanager's BSD license [3], but I'd still prefer, if you acknowledged that here yourself. Once I've got your feedback I'm prepared to obsolete the separate hack for the upcoming acct_mgr-0.5 and later. [The form you get from bottrap seems a bit odd to me. The box is labelled Parole: -- which is correct, but not a word I'd ever have used for that -- rather than the hint which appears below, but I didn't try to change it. Also, it was unclear what the register_check list could comprise and exactly how to customize things without the admin GUI.] Regarding configuration you must have missed the relevant wiki documentation [4]. As non-native speaker I'm not in the position to argue about wording, but surly I took advice before making that choice. Make sure to check, what SpamFilterPlugin [5] could do for you. Steffen Hoffmann [1] http://trac-hacks.org/wiki/QuestionRegisterPlugin [2] http://trac-hacks.org/ticket/10270 [3] http://trac-hacks.org/wiki/License/MandatorySignOff [4] http://trac-hacks.org/wiki/AccountManagerPlugin/RegistrationInspector#ModularRegistrationChecks [5] http://trac.edgewall.org/wiki/SpamFilter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRamKIACgkQ31DJeiZFuHfHvwCguDVsSn5IaaeoZ4Tm75pZyfvm iqcAnR0alxwLDZBGWIIRIQWO3UJBxQSS =mWex -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] TypeError: 'NoneType' object is unsubscriptable during trac-admin resync after trac upgrade from 0.11 to 1.0.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.11.2014 01:12, ytp...@gmail.com wrote: I just upgraded trac from 0.11 to 1.0.2. I followed the steps 1 ~ 6 described in http://trac.edgewall.org/wiki/TracUpgrade. When I try to resync the project repository, I got the following error: [root@dm-git conf]# trac-admin /usr/share/trac/projects/partiqle repository resync '*' 19:55:45 Trac[env] INFO: environment startup [Trac 1.0.2] ... 19:55:45 Trac[loader] DEBUG: Loading git from /usr/lib/python2.6/site-packages/TracGit-0.11.0.2-py2.6.egg ... /usr/lib/python2.6/site-packages/TracGit-0.11.0.2-py2.6.egg/tracext/git/git_fs.py, line 180, in __init__ Repository.__init__(self, git:+path, None, log) File /usr/lib/python2.6/site-packages/Trac-1.0.2-py2.6.egg/trac/versioncontrol/api.py, line 788, in __init__ self.reponame = params['name'] TypeError: 'NoneType' object is unsubscriptable 19:55:45 Trac[PyGIT] DEBUG: PyGIT.Storage instance 42904824 destructed [root@dm-git conf]# Any advise on how to fix this is most appreciated! I don't use Trac with repositories at all, but I agree to Ryan, that you should rather enable and use new bulit-in Git support than the external plugin (TracGit-0.11.0.2), because Git support officially moved into Trac's optional modules. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlRWj+MACgkQ31DJeiZFuHdxfwCg1FpffaZ4dOaSDTiDtdmxTSVL EuUAoNWtoknT3T+R+goLwvVoq835Dthn =NU9e -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac, Ubuntu and svn (no changeset 0)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25.10.2014 11:41, Jeff Skyrunner wrote: So, pretending to ignore my dumbness, could you please help me with another issue? I've commited a file in the repo, but had to manually resync the repository to see that file in the source code... shouldn't that be provided automatically by the hooks? Or am I missing (again) something very obvious? You may find the part on repo sync in TracRepositoryAdmin [1] wiki page (self-documentation as in you own Trac environments) enlightening. In short, since Trac v0.12 you'll have to install a repository-specific hook script (examples available) or opt for per-request sync. And make sure that the related option 'repository_sync_per_request' is set accordingly in you trac.ini file. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracRepositoryAdmin#Synchronization -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlRLtRgACgkQ31DJeiZFuHfwWQCfQeD6gsPUNAKswKpQFMeHCymm O9MAniJBqDEZ8sBJaHBrAw/4JIeo73xp =Jx3I -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Obfuscate Usernames By Role
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.10.2014 21:02, akor...@smartsoftwareinc.com wrote: I did find a trac-hacks plugin that was doing something similar to what I wanted, which lead me to the IRequestFilter interface that seems to work for my purposes (although it's a bit hackish). Yeah, the name of the site is there for some reason. :-) My next step is submitting a search request to an LDAP server to determine the group my user is in. I've installed the python-ldap library on my machine and confirmed that scripts on my machine can use the library, but when I add import ldap to my plugin it immediately fails to load with an ImportError: No module named ldap. I'm guessing this is an issue with getting the python-ldap library into the scope of my trac virtual environment but I'm lost beyond that. Has anyone seen this issue before? I guess you installed python-ldap after creating that virtual env? There are some ways to make globally installed libraries known to a virtual env too, and you should really find hints about it on the net easily. Anyway, other than making all libs (exiting at time of virtual env creation time) known to a new virtual env, there is a method I use [1] to do this later on and selectively. Steffen Hoffmann [1] http://codersbuffet.blogspot.com/2009/09/mercurial-subversion-and-virtualenv.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlRANmQACgkQ31DJeiZFuHfo7ACZAYDp7I5uBoJNcNKUxeZ+bXG8 jS4AoNyG9Rivm6xrvT3cw+Tre8+Mj3DJ =Eu79 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Obfuscate Usernames By Role
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.10.2014 01:43, akor...@smartsoftwareinc.com wrote: I need a way to convert usernames to roles everywhere that usernames are displayed in the application. So, users in my group will be able to see my name as the ticket reporter/owner, in the change history section, etc but users in other groups will only see Developer (my group name) in those places. ... Does anyone have any ideas of how I might go about accomplishing this task? Is there some centralized ticket object/class that I can tie into, perhaps override a getter/setter so I can manipulate this data everywhere it is shown in the application? Can I accomplish this with additional fields and permission checks, so one group sees the username fields and another sees corresponding user role fields? Have a look at Chrome.format_author() method in trac.web.chrome, that is the canonical place, but especially watch out for plugins that might not respect this convention. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQ48rUACgkQ31DJeiZFuHeAqACfc5TDW31jXLdiUJrSoKDRy/6J xs8An1+sDhfpF+RzgyG5PouWpeVjyfS5 =TqBa -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Unable To Post Attachment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.10.2014 21:51, Duckworth, Douglas C wrote: Good Afternoon, I am getting this error when attempting to post an attachment: Trac detected an internal error: OSError: [Errno 13] Permission denied: '/var/www/trac/files/attachments/ticket' The path must be writeable for the UID that your Trac process is running with. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQ2/yQACgkQ31DJeiZFuHdACQCg0jfvCFg7Qai+bAKDQ3WXR/KX TZ0AoIdL7wp14M+2YAAHjI2luX1dhCds =5wwr -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac isn't sending me verification emails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.10.2014 23:04, Eric Crockett wrote: On Tuesday, September 30, 2014 2:15:09 PM UTC-4, Matthew Caron wrote: Judging by the links in your email, you tried to register on the server trac.haskell.org http://trac.haskell.org, right? I would speculate that something is wrong with their Trac setup and you should contact them and let them know. Any idea how I might contact them? All help/support links are for the generic trac project which point to this mailing list. I've just checked the instance a bit. Following the instruction on WikiStart you can login to the guest account. The timeline reveals, that this Trac has been initially setup on 2010-04-12 and updated to 0.11.1 on 2011-02-01, but has never seen any more activity. Anyway, if I where you, I'd try to contact these folks via their IRC channel [1] or mailing-list [2]. Steffen Hoffmann [1] http://www.haskell.org/haskellwiki/IRC_channel [2] http://www.haskell.org/haskellwiki/Mailing_lists -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQuWOkACgkQ31DJeiZFuHeJIACgo8x640Ned2K33JkdsvWPG2PE nqsAoIJVACyXGtLMvnotRL5VQEMfjsTf =SmXs -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Plugin Dev: is it safe to open a second environment?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30.09.2014 12:10, Cooke, Mark wrote: Folks, I am playing with a plugin to help manage my trac sites and am wondering if it is safe to open a different project's environment within the plugin? By chance, have you seen AccountManagerPlugin code for auth cookie distribution (cheap single-sign-on-like behavior for a multiple Trac env in parent dir setup)? I've reworked that code since its initial publication, because I've noticed what I think is a memory leak from these cross-env-operations. While it has improved I've not been able to totally avoid the effect. OTOH we're just in the process of adopting current Trac 1.0 db API, and I'm very eager to see the effect of using that improved db backend handling code. Steffen Hoffmann [1] http://trac-hacks.org/wiki/AccountManagerPlugin [2] http://trac-hacks.org/wiki/CookBook/AccountManagerPluginConfiguration#SingleSignOn [3] http://trac-hacks.org/ticket/11915 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQtkyIACgkQ31DJeiZFuHdpwACfdqPB7UflzojklGOOZ9KbVyMs RFcAnjbxcxwYUCqFk4GuCkSxNAWRcJt8 =R3Xv -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Row span in Trac wiki tables
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22.09.2014 20:45, Jun Omae wrote: On Tue, Sep 23, 2014 at 3:30 AM, Christopher Nelson chris.nelson.1...@gmail.com wrote: I swear I saw something in Trac 1.0.x release notes that I could now have a cell in a pipe-delimited table span multiple rows. I know how to do a multi-column cell but can't find the multi-row format now that I want it. Am I imagining it? See Example 3: Complex Tables in http://trac.edgewall.org/wiki/WikiFormatting#Processors Sure, but this is neither new nor what Christopher is asking, as far as I understand the question. Sorry, but I've not seen any change for pipe-delimited table wiki format so far. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQgfTQACgkQ31DJeiZFuHfcBACgzjZdvjVQlJpQtfGnX959wJqG ty4Anj0iRytKrK5N7YaqHAP4fX/WiJQV =PeDI -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Logging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.09.2014 18:32, Sigurdur Bjarnason wrote: Hi all, Hope you can direct newbie of Trac about logging, I have managed to setup trac with svn however... when I try to set logging in the trac.ini No log file is created? I have been google-ing around but with now hint to what is going on. I am running on Ubuntu and this is the logging section in my global.ini [logging] log_file = trac.log log_level = DEBUG log_type = file ..no matter what I do.. no log file is created :/ please hint me in the right direction here.. There have been some hints, of what I think the permission is the most common reason to look for. Did you finally get to it? Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQZ0/EACgkQ31DJeiZFuHc5RgCghYA+ncNL4fpfJZyCNWPcSNm8 SsoAn0Fat37sQW1IMRyQEQq5bH6OPuAT =1OUc -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] German translation TracTicketChangelogPlugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.09.2014 10:45, Riedel, Torge wrote: On the other hand Changelogs is not listed in the message file since it is hard-coded here. Created a new ticket https://trac-hacks.org/ticket/11983 for it including change of section title. Thanks for the suggestions. I went ahead and extracted another hard-coded string as well. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQYpGAACgkQ31DJeiZFuHc29QCgmMWrVnlu/1s0v0C2tH9nWK0x wTkAn29SKS3tqFmroShZmTZrvHRCUBvj =2vp0 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re2: [Trac] Re: TracTicketChangelogPlugin does not display anything in Tickets
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.09.2014 09:54, Riedel, Torge wrote: Another thing: We enabled German language for trac, how can I support translating this plug-in? You're welcome. I've had a quick look at the source, and Richard seem to have prepared i18n for this plugin, but no one did extract messages before. Best to follow the included hints for developers [1] or our more general advice regarding Trac plugin translation work [2][3]. Maybe there is something to fix regarding the 4 years old i18n code, but this could be sorted out, if you care and ask more specific questions. I'll try to assist, if required. Another thing #2: It might be confusing to have a title Changelogs when having already a title Change History in the ticket view. What about Commit Logs or Commit History? Feel free to propose message_id change in an enhancement request (ticket) against this plugin. But I do not feel entitled to judge about English wording that much, more regarding successive German translations. Steffen Hoffmann (hasienda) [1] http://trac-hacks.org/browser/tracticketchangelogplugin/0.12/i18n_for_developer.txt [2] http://trac.edgewall.org/intertrac/wiki%3ACookBook/PluginL10N%23Prepareplugincode [3] http://trac-hacks.org/wiki/TracPluginTranslation -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlQXXjMACgkQ31DJeiZFuHfoMQCgjXublQAV4SMPOBjs+QZXvtT/ i8IAoM228EiNffrp/jf0dO0yrl1O9kMc =1Qrb -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] SubWiki page syntax
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.08.2014 13:27, Roger Oberholtzer wrote: I am trying to Include a sub-wiki page in a wiki page. If I have a page called 'here', the following works: [[Include(here/subPage)]] but the following does not: [[Include(./subPage)]] It complains that ./subPage cannot be found. According to the docs, the second syntax should be equivalent with the first. With docs you refer to TracLinks, specifically the paragraph on relative links [1]? Well, a short look at the current source code reveals, that that wiki page name resolution is not implemented yet in IncludeMacro. To implement it, one would have to use a wiki page link resolver syntax like in WikiSystem component [2]. Unluckily that one is modular, but not exposed for re-use by plugins, so we would need to copy it. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracLinks#Relativelinks [2] http://trac.edgewall.org/browser/trunk/trac/wiki/api.py?rev=12853#L405 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlP+NtYACgkQ31DJeiZFuHc0ugCfS5OMc9X3o3oKO+/c8eyXWMCI UDwAoJKCiE3JUU3Mi0lpTsl6/8PbToSJ =pSeJ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] SubWiki page syntax
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.08.2014 22:22, Peter Suter wrote: On 27.08.2014 21:51, Steffen Hoffmann wrote: Unluckily that one is modular, but not exposed for re-use by plugins, so we would need to copy it. Actually it is a bit exposed now, since it is reused in TitleIndexMacro [1]. (At least the requested, and IMO most useful part.) I think it would be something like this: if page_name and formatter.resource and formatter.resource.realm == 'wiki': page_name = formatter.wiki.resolve_relative_name(page_name, formatter.resource.id) Added just before retrieving the WikiPage [2]. Right, I saw that. While this is a good thing for the future, it is a) not too hard to include the full support and b) not backwards-compatible. AFAIK current IncludeMacro still aims at 0.11 compatibility. I've proposed a solution for the corresponding, rather old ticket [3], saving a conditional import of the aforementioned method for . Steffen Hoffmann [3] http://trac-hacks.org/ticket/3591 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlP+hCMACgkQ31DJeiZFuHd9KgCeOkY+fY2uFqAjy+6HqdjeFQTR LgYAoLi8o9QQfO7/f+SejMy3HTurC4Fl =jsJg -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: PostgreSQL - a straw poll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.08.2014 19:11, Jared Bownds wrote: After checking the postgres DB after the migration, there is no table called subtickets. Perhaps the migration script is not equipped to include this type of table? I've had a quick look at TracMigratePlugin. Its unlikely that it misses specific tables as it is designed to copy ALL tables. Unless there was an error on migration, as Ryan already suggested. Another look, this time at TracSubticketsPlugin source confirms, that the plugin i.e. provides integer version numbers from tracsubtickets/db_default.py for writing to Trac db table system (see tracsubtickets/api.py), but that table is defined with text columns. So type sloppiness is a likely cause of the TracSubticketsPlugin upgrade failure that you shall see on migration. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlPqdAMACgkQ31DJeiZFuHc5JACcCQ9bLKES5wo9FHSQeb+nw2aq UFAAoMiYYy0sstUvJFoybwqztFsGGBeR =V1IV -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: How to apply a patch to Trac
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.08.2014 20:36, Jared Bownds wrote: For example, would these be an expected output? (jared)-(11:33:30)-(/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac) - *patch -p1 Trac-show_full_names-sorted-r4-0.12.2.patch* Yes. As you see at least some changes apply. Otherwise it could be just on the wrong level, but obviously you adjusted it correctly with -p option. Offset is a hint on code changes between the version the patch has been created an the version you're trying to apply the patch. With only offset it might, but is not guaranteed to work. Anyway the presented case includes failing lines too, so you're required to rework the changes collected in the corresponding *.rej files to fit into the current version. Depending on the intermediately introduced changes adjusting a patch is anything between trivial and almost impossible. Recent commit messages could help to reveal potentially complicated changes. No one could tell without seeing the code in detail. And certainly it is no longer just patching but will require some Python knowledge to do the work. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlPmHpgACgkQ31DJeiZFuHcB/QCeITZc6kpdzv6+SfVkhR3P8Poe yFoAoKP+raVrTZPdotcXzuUMkyHSyHPe =0vbt -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Unable to complete upgrade to 1.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.07.2014 16:02, Anton Piatek wrote: I just upgraded my Ubuntu 12.04 server to 14.04.1 and as part of that upgraded trac. I get the following error trying to complete the upgrade of trac when running the trac-admin ... upgrade command The upgrade failed. Please fix the issue and try again. AttributeError: I have enabled the log and it shows Smart move. Now you only need to read with an informed eye. So it was the right thing to post here too. /usr/local/lib/python2.7/dist-packages/TracTags-0.6-py2.7.egg/tractags/model.py, line 23, in environment_needs_upgrade if self._need_migration(db): File /usr/local/lib/python2.7/dist-packages/TracTags-0.6-py2.7.egg/tractags/model.py, line 47, in _need_migration db.rollback() Your version of TagsPlugin [1] is rather old an well-known to be incompatible with Trac=1.0. But this is not a problem, because the issue has been resolved for you months ago and you'll get an even better plugin by upgrading. Just do it. :-) Be sure to handle further issues similarly by looking at locally installed plugins first. I remember that we found a number of plugins that shared the troublesome upgrade check code, so chances are you have some of these installed at well. Sincerely, Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlPWbgcACgkQ31DJeiZFuHeiHQCZARI3JZatn19l3enO3KKAHEZm xk4AoOiWoX6yFHARicqngxrLi4EiF/tb =gVsp -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Read only ticket according to custom resolution type
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.07.2014 08:55, RjOllos wrote: Btw, in vulnerable_tickets.py, should the check be changed?: if 'VULNERABILITY_VIEW' not in perm: - if 'VULNERABILITY_VIEW' not in perm(resource): It depends on the intention. From earlier discussion I remember, that recommended, performance conscious practice of Trac permission checking involves a rather cheep pre-check, if the required permission is assigned to the SID at all. That's what the first line would be good for. The suggested replacement does the fine-grained check, that required the resource object. I've been testing with 'only' 30.000+ tickets in my Trac development environment to learn, that constructing resource objects IS a costly task that shall be avoided, if possible. Just my 2 cents. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlPWcDoACgkQ31DJeiZFuHfkdgCg1mOSo/WP+SIhnFbOQgAoomac GpsAnA3jTWSLj6fkz5E+3+6IrnwQqBVd =UsxY -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Can you link two Trac repository to one SVN repository?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.06.2014 21:39, Abtin Khatoonabadi wrote: Hello, I am trying to have the following set up. Assume that my customer has two different project developments in one SVN repository, project A and project B. Project A and project B are also sharing the same Trac repository. Sorry to interfere, but there is no such thing like a Trac repository. Trac repository browser accesses existing repositories and provides views on them. Of course you may only show parts of a repository using different fine-grained permission [1] settings for different Trac instances. I'm assuming your setup is a multiple Trac environments in single parent directory, but this doesn't matter at all here. My customer is asking me to do the following: · Both Project A and B are going to share the same SVN repository. Possible starting from Trac 0.12. [2] · Project A and B need to have their own Trac repository. Unclear, see above. · When there is a commit on the project A part of the SVN repository, the referenced ticket on the Trac repository A needs to be updated. You need to customize the ticket commit updater script to know about the mapping of different SVN branches to respective Trac environments. · When there is a commit on the project B part of the SVN repository, the referenced ticket on the Trac repository B needs to be updated. Likewise. I looked at /_http://trac.edgewall.org/wiki_/and I didn’t find anything about one SVN repositoriy for multiple Trac repositories. I was wondering if this capability exists? If yes, then could you provide the link so I can read and learn? All supported repository types have optional components that you need to enable explicitly, even SVN since 1.0 IIRC. See the repository administration page [3] for details. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracFineGrainedPermissions [2] http://trac.edgewall.org/wiki/MultipleRepositorySupport [3] http://trac.edgewall.org/wiki/TracRepositoryAdmin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlOYwUIACgkQ31DJeiZFuHcxMgCg0dB3GG8zsYQDSWY33eeENHWQ T7UAmwcf9gQuRoZYjUNCWuLaP2xKciwu =b3GN -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Error while using DiscussionPlugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01.06.2014 20:02, Ryan Ollos wrote: On Jun 1, 2014 11:42 AM, Ramprasad S homeofm...@gmail.com mailto:homeofm...@gmail.com wrote: Can you please help me here? You already opened a ticket for the issue and the plugin maintainer has been trying to help you resolve the issue. You should continue working with him to resolve the issue. http://trac-hacks.org/ticket/11800 I'm confident to resolve this issue for the reporter. But obviously he's not as sure. And I wouldn't mind additional feedback, but I've been reviewing the code for more than a month now, and right now there are likely not many developers that have equal insight. If someone would proof me wrong, this would be the person we're looking for maintainer-ship, or at least co-maintenance. :-) Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlOLceAACgkQ31DJeiZFuHfHBgCdGr3GIr9ep5NPU4ax0ynQssqt wGAAnRPeniL/BIPOMgIDUzX94xmOL3q+ =bh3l -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] SensitiveTicketsPlugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.05.2014 11:50, russell gower wrote: Hi, I’m evaluating the SensitiveTicketsPlugin but I’ve hit a snag that may prevent me from using it, basically we don’t want users with TRAC_ADMIN privileges to see tickets marked as sensitive unless they would see them if they didn’t have the TRAC_ADMIN privilege, is this possible? Sorry for the late response, but No, you cannot do that because of hard-coded TRAC_ADMIN behavior to inherit ANY action/permission defined on a Trac system. If you really want to break admin privilege (reliably), IMO the only way is (strong) encryption. I meant to provide such methods by now [1], but unfortunately development is on hold already for too long. Steffen Hoffmann [1] http://trac-hacks.org/wiki/CryptoPlugin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNz1b4ACgkQ31DJeiZFuHeeQwCeOYquetiNoxGkJsHSyUQVtIlB WIUAmwfw4XJti3xzR/p23M+O93sz2hXe =kjBZ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac fails with UnknownLocaleError after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.05.2014 00:41, Felix Mayer wrote: File /usr/lib/python2.7/dist-packages/babel/core.py, line 313, in parse raise UnknownLocaleError(input_id) UnknownLocaleError: unknown locale You do not explicitly disclose your Trac version. I see you use Python2.7, and no Trac plugin seems involved here (in traceback), so the best guess is reinstalling babel with you distribution's tools [1]. Because Babel is optional for Trac you could even get rid of it by uninstalling Babel, at least as temporary workaround. Steffen Hoffmann [1] http://trac.edgewall.org/ticket/10589 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNkylIACgkQ31DJeiZFuHcFSACgzylYE/5PMVpSiY1ebLBWjZpO S28AnAizYbcOW/CCoQ+vUKjgRdo6FUf1 =INKy -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] description diff without rebuilding the exe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01.05.2014 17:10, David Vanleeuwen wrote:
Also, is there a way to run a python script in genshi?
I do know at least of two:
Python code block/lines (as permitted by Genshi xmlns as I guess)
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
xmlns:xi=http://www.w3.org/2001/XInclude;
xmlns:py=http://genshi.edgewall.org/;
!--!
Copyright (C) 2007-2011 Radek Bartoň black...@post.cz
This software is licensed as described in the file COPYING, which
you should have received as part of this distribution.
--
xi:include href=discussion-macros.html/
xi:include href=layout.html/
head
titleForum List ndash; Discussion/title
/head
?python
from trac.wiki.formatter import format_to_oneliner
from trac.util.datefmt import format_datetime, pretty_timedelta
from tracdiscussion.api import format_to_oneliner_no_links
?
Python code snippet inside ${} (another Genshi XHTML template extension)
py:def function=display_group(group, forums)
table class=listing
thead
tr py:if=group and group.id != 0
th class=group colspan=11
div class=name${format_to_oneliner(discussion.env,
context, group.name)}/div
div
class=description${format_to_oneliner(discussion.env, context,
group.description)}/div
/th
/tr
Beware, that cited examples are not showing ideal code by no means, just
meant for illustration of the real-world use case.
Steffen Hoffmann
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iEYEARECAAYFAlNi7Z8ACgkQ31DJeiZFuHdomwCfTq79KKM2ksOxHox0NT1gEReI
m4oAn0aBussl6zBtFrke0vV3nfEfCymZ
=s7V7
-END PGP SIGNATURE-
--
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 http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac using apache on windows
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29.04.2014 16:13, ONeal Freeman wrote: Has anyone upgraded or patched their Bitnami installed Apache? Not yet, but I know that BitNami staff is reading, is quite helpful and listens to its users, so you should get an authoritative answer rather soon. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNfvGgACgkQ31DJeiZFuHeEVACgx2ARucbNPsHGDBWDsD5EmG35 dAIAn3kCBPyXQLDJLTnv+UyRfEmHEGW1 =CC7c -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: One repository and two trac instances
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 18:26, shath...@e-z.net wrote: The trac subsystem complained about a duplicate repository and disabled one. IMO this shouldn't be detected at all. So if you're running Trac 1.0 and could provide some more details about that setup, this should justify a ticket against the repository code management of Trac core. When using trac-admin $ENV repository commands, I was able to accomplish repository sharing across multiple trac environments. As I would expect. It might be an early hint to narrow the issue location down to some web-UI stuff rather than the main/db-facing middleware code? I am still in the proof-of-concept stage of enterprise deployment for Trac, Subversion, Apache2, and MS-Active Directory authentication. Sounds like a reasonable Trac application, not too exotic. I guess, that there are already similar applications out there. The ability to link repository updates to Trac tickets in several environments would be useful, but not a show-stopper. My biggest concern regarding linking subversion commits to Trac tickets would be how to enforce the recognition of ticket linkage to only one of several repository browsers. On the repository side (commit comments) TracLinks with InterTrac syntax will resolve with only suitable configured Trac out-of-the-box. I did already hint on the requirements for correct placement of commit messages to tickets of the referenced environment(s). IMHO, only one trac environment should be authoritative for repository maintenance, even if multiple trac environments can serve as browsers. This reads a bit confusing. From Trac's side it is all management and linking, browser-only. Nothing that would neither allow nor require being authoritative in any obvious way. Any action beyond code examination has still to be done with native repository clients and tools. Hope, this clears it up a bit for you. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNei/QACgkQ31DJeiZFuHdyuwCgx2e9BzWXNu0vL8aLwpiXQZsZ Ok4An1J/hLX7mU32YAYGCYC0isZJ9OF0 =2r6+ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] One repository and two trac instances
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25.04.2014 12:54, mimi wrote: Question: is there any extension to the #-type links which can point a particular ticket in the particular trac instance? Or have to put full url link? You may be able to code something different, but speaking of existing functionality, there InterTrac [1] link syntax for http://trac.edgewall.org/wiki/TracLinks [2] will allow to set links to different issue tracker instances - just what you want. Easy enough, if you create speaking and memorable InterTrac aliases for both. Likely the biggest part might become the work for extending CommitTicketUpdater [3]. While it shouldn't be hard to filter for references with prefix matching local environment name, at least I cannot see, that InterTrac ticket links are supported as ticket reference out-of-the-box [4]. OTOH there is an old ticket [5] referring to a demand like yours. Someone even worked out a patch, that you may give a try and possibly support further development by reporting back, if you care. Steffen Hoffmann [1] https://trac.edgewall.org/wiki/InterTrac [2] https://trac.edgewall.org/wiki/TracLinks [3] https://trac.edgewall.org/wiki/CommitTicketUpdater [4] https://trac.edgewall.org/browser/tags/trac-1.0/tracopt/ticket/commit_updater.py [5] https://trac.edgewall.org/ticket/4746 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNaT70ACgkQ31DJeiZFuHdaawCg0cOVsEzyF+cpSpMEWcBLowpF EZUAoNbwHV1qze0a4B7/grUDtcrLalCq =4ri/ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] OperationalError: (1136, Column count doesn't match value count at row 1)
On 04.04.2014 15:07, Frank wrote: Steffen, Thank you for the information. Do you think it's possible to run 1.1.2dev-r11794 on the same new box at the same time as 0.12.2 (the .deb packaged version)? If so, I wouldn't mind copy/paste the markdown and recreating the pages manually between browser tabs. That would enable me to stay with the .deb upgrade process in the future. Thoughts? Sure, you can do this, like Olemis already pointed out. Debian packages python-virtualenv virtualenvwrapper are excellent for using some Trac versions in parallel. You should definitely try it out, because it will help you testing future upgrades too, but on a copy of you environment next time. Steffen Hoffmann smime.p7s Description: S/MIME Cryptographic Signature
Re: [Trac] OperationalError: (1136, Column count doesn't match value count at row 1)
On 04.04.2014 15:07, Frank wrote: Steffen, Thank you for the information. Do you think it's possible to run 1.1.2dev-r11794 on the same new box at the same time as 0.12.2 (the .deb packaged version)? If so, I wouldn't mind copy/paste the markdown and recreating the pages manually between browser tabs. That would enable me to stay with the .deb upgrade process in the future. Thoughts? Sure, you can do this, like Olemis already pointed out. Debian packages python-virtualenv virtualenvwrapper are excellent for using some Trac versions in parallel. You should definitely try it out, because it will help you testing future upgrades too, but on a copy of you environment next time. Steffen Hoffmann smime.p7s Description: S/MIME Cryptographic Signature
[Trac] Announce: New TagsPlugin 0.7 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, due to joined effort we've finally pushed out tractags-0.7 [1] tonight. This version is not just a release but a major milestone. It is the first release after this plugin has been totally rewritten by Alec Thomas in 2008. The plugin does not only fully support i18n, but comes with 4 complete (for Korean, German, Japanese, Chinese(China)) and 2 advanced translations (for French and Russian), and there are more on the way. For this release we've been working to resolve more than 50 bugs and 20 enhancement requests, from what the most noticeable might be #2429: TagsPlugin should handle versioning of wiki tags #4503: Performance issues #7857: Regression in Tag query functionality #9061: Mass tag replacement functionality with tagged realm filtering #9521: New install impossible on Trac 0.13dev This work has been enabled and driven by contributions of more than a dozen ambitions developers and translators. Thanks to all of you. Note that we've arranged source distribution via PyPi [1] for your convenience as well. Have fun, and continue successful Trac hacking. Steffen Hoffmann [1] https://trac-hacks.org/wiki/TagsPlugin [2] https://pypi.python.org/pypi/TracTags -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNB0ogACgkQ31DJeiZFuHeHsACgrsHv6Ovk7sdUAxholhQZ63h4 uQQAoIvGZ+8hElNQGdXh0OcXNxOEjGZs =wM2k -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] OperationalError: (1136, Column count doesn't match value count at row 1)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2014 14:22, Concord wrote: Trac 0.12.2 *Moving my Trac install from from svn version 1.1.2dev-r11794 to the Ubuntu 12.04LTS version of Trac 0.12.2. I'm having trouble ... ... Oops… Well, you're in trouble, of course. You cannot downgrade that easily. If you really took a Trac environment, that has been used with Trac 1.1.2dev before, there is no way going back without altering the db. Between 0.12-stable and 1.0 the attachment storage has been totally reworked, and there is only an upgrade script. You should have lost access to all attachments by moving to the older Trac version, and there is certainly more trouble to expect. These options bring you back into safe waters: Install and use Trac 1.1.2dev on the new server as well. Use a db backup from before the upgrade to 1.1.2dev, if you have one, but you will loose your work done after that point. Use a new environment for 0.12.2, if you can effort to loose all data. Any downgrade attempt is unexplored land, and you're mostly on your own. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlM8Yg4ACgkQ31DJeiZFuHckJQCeI8eUaQroitjUa1SZa0LQmVSg 3xMAn2h/jcf1rWIN1LRSbXVpK42XIjqu =Kbj9 -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Question about next Trac 1.0.2 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25.03.2014 20:37, anton wrote: I have only a small question: Small step for me, big step for mankind ... ;-) When will Trac 1.02 be available. Good question. There was an argument on doing such a new release few weeks ago, also to familiarize new developers with release actions. I ask because some times ago the Miletone in the Roadmap showed nearly 100% closed tickets. But as time passes, always new tickets are added ... so will there ever be a Trac 1.0.2 ?? At least 1.0.2 is more likely to happen in the near future then 1.2 IMHO. Wouldn't it be better to relese 1.0.2 and move the actual tickets to 1.0.3? Maybe. But these, who actually resolve tickets, rule. Or is 1.2 the next step? Next major release, yes. Pull and engage Trac when ever you like and need it. You'll always get a working product, and developers work hard to ensure integration with many Trac plugins as possible and seemless upgrades to any future minor and major release. I like that dedication a lot. And you'll appreciate it too. Sorry, but coding rules. Numbers are just milestone labels. And its ready when its ready (borrowed from Debian guys). Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMx71AACgkQ31DJeiZFuHeRpwCfaFNvuX56TDh/CE1O9HJNuJso pe0AoJSfUINSA4Kmmep8e+cBDKbAQYpX =7bcf -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Cannot update tickets after 1.0.1 upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.03.2014 13:50, omar.c...@thyme.it wrote: Hi all, I already saw this ticket http://trac.edgewall.org/ticket/11155, and this https://groups.google.com/forum/#!topic/trac-users/7PIjhH5N2_Y discussion too, but I can't resolve my problem. After upgrading from TraC 0.11 to 1.0.1, I cannot modify tickets, nor old nor the newly created ones. But the logs you provided reveal no permission issue, in fact no failed permission checks at all. Does the session log come from session with TRAC_ADMIN privileges? Do you have all/most Trac modules enabled? I haven't Agilo installed, so the solution described in the above discussion does not apply to me. The strange thing is that only one of my six TraC environments has the problem, and they use all the same environment (same machine, same database, no external plugins). ... I would watch out for old custom templates in env/templates, because I saw a lot of issues for upgraders coming from conflicts causes by old custom templates. Installed Plugins Name Version Location ... TracAccountManager http://trac-hacks.org/wiki/AccountManagerPlugin 0.2.1dev Too bad, this one is full of issues and obsoleted for years. Do not dare to use it one day longer, but upgrade to current stable ASAP, looking at upgrading notes for important, required configuration changes. If I try to udpate a ticket, the log says: (snip) Fine, no obvious problems here. Loaded modules/libraries: (snip) All well on first sight. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMwetIACgkQ31DJeiZFuHe76ACg4yIyFSO8RXDs2Jj6GiH/rdD6 iAcAoL1sG3tEsAjWbWwAO7gNIUuwIJpn =N2QW -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.03.2014 14:54, ONeal Freeman wrote: I will admit that I am struggling with the queries trying to get tickets close during a period like the last 30-days. I am quite confused as to why the developers would chose to use seconds and milliseconds but who am I... As you've not been involved into related issues and development, this is a valid question. In short, we've got reports of issues with timestamps when doing automated changes within some milliseconds while the time resolution has been only seconds. I.e. it was no longer guaranteed, that composite keys in ticket_change db table consisting of timestamp + ticket ID were unique for each change. Accounting for future improvements of IT equipment and making a step into safe water it was consequent to boost time resolution by a factor of 6 - up to microseconds, you see? You'll make your way with adapting queries to that time stamps too. For issues browse the mailing list first, and ask detailed questions, if required. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMp4GUACgkQ31DJeiZFuHcMOACcDAL6Odew9K/u5OA0c3E46e9r gsIAn3NBN5rADFIUsVvasPV3/Kam30qu =vkrY -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Reporter/Owners who have left
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.03.2014 21:25, RjOllos wrote: If you're looking for a web interface to the session data, I believe that AccountManagerPlugin will delete the session data when a user is deleted. Yes, at least recent versions do that reliably. A special case are valid email addresses as usernames, what might still drive notification from existing reporter/commenter entries. Steffen Hoffman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMqA0UACgkQ31DJeiZFuHfqKwCcCPzMrKouFF29eG1wDymo2ANc qQoAn1NpNWWktHWZ/GQK5yYlayAvu15d =XqPP -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.03.2014 01:57, RjOllos wrote: I think those will only be shown for a specific permission, such as TT_USER, so you may be able to change that behavior by adjusting the permissions. Correct. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMmy3kACgkQ31DJeiZFuHf2PACdHT/WncmUeYI6kMI0x2ceKt+D lJYAmwcf7ZzdYjyspz5ECJSOTPnne67V =93/+ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Authentication information not available. Please refer to the installation documentation.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17.03.2014 09:34, RjOllos wrote: Creating a user for htpassword does not affect the permissions table. You'll need to use the permission add command to grant permission for the admin user. The admin user will have all the permissions of the meta-users anonymous and authenticated. For clarity: It does not work automatically by using a reserved user name like 'admin', rather you'll get full permission assigned by executing the trac admin CLI like so: $ trac-admin path-to-trac-env permission add username TRAC_ADMIN See wiki documentation for more details on Trac permissions [1] and on the admin CLI [2] respectively. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracPermissions [2] http://trac.edgewall.org/wiki/TracAdmin?version=21 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMm/q4ACgkQ31DJeiZFuHe6rwCgrVxCAkyVg0J6+JQhE2/fpv5W 6dAAoJUVrMfLGPqNQSWixYdQ/bpUmzg1 =qT1z -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.03.2014 17:06, ONeal Freeman wrote:
I did take Trac live today on my server and trying to work through the
bugs as they appear. We depend on it so heavily.
Dependency can push things - good, unless you start to act too hastily.
If you recall I have a test machine I work on before making changes to
the actual server. I have a couple of issues on my server instance that
are not present on my test machine. One is that my tickets on the server
show last modified 44 years ago where the test machine shows 8 weeks.
You're looking at time column content, that has not been upgrades from
POSIX seconds to microseconds correctly. This could quite easily fixed
manually, if needed, but I fear there could be more than that.
I.e. Trac 1.x totally changed the attachment file storage organization.
Did you check, that you can still open/view your old attachments?
Also in the tickets from trac 0.10.4 we used the {{{ }}} around emails
pasted into the comments. In trac 1.0.1 those same {{{ }}} in the
comments are showing up. Again, they look fine on the test machine but
not the server.
{{{ }}} is still a special character constellation. If it does not work,
there is a) something broken regarding WikiFormatting or b) content
malformed, similar to what you reported for the description ticket field
before.
I have spent a lot of the morning comparing the plugins and the trac.ini
between the test machine and server to make sure it is entirely
duplicated but I am obviously missing something.
Well, it might be worth following Ryan's advice, if it is possible for
you to roll-over to that alternative import db.
Steffen Hoffmann
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iEYEARECAAYFAlMnTjwACgkQ31DJeiZFuHeyxwCfY8Im+sl3LS+B0IdTaQ+rg6ii
qMoAoOgNOj+upt/PUGsecSqVJy+gvcHq
=snVr
-END PGP SIGNATURE-
--
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 http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Trac.db questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2014 17:55, ONeal Freeman wrote: Good in theory but it did not work in my case since something during the trac-admin upgrade command is wiping out some rather important db fields. Now that's not to say that I do not have something mis-configured. It is this 'something' that is worrying me. Granted that Trac upgrades are solid and reliable, million times tested process it is unlikely, that just you'll get hit by a flaw. Experiencing issues I would repeat the process with all plugins disabled/uninstalled and just upgrade Trac core, upgrade plugins later on, if required. This is my first dealing with Trac from this prospective. Since I never got the tractickettemplateplugin to work I am wondering if all of this is associated with the BitNami install of Trac. Nothing special with BitNami's stack as far as I know from using it two times on WinXP. Again, I am a novice but I have definitely learned a lot. Please don't take any of this wrong, I sincerely appreciate you guys helping me and your assistance has gotten me this far. Sure, you're welcome. Still i hope, that we'll finally get a clue, what is going on. Did we talk about DEBUG logs from upgrade process yet? Mysteries in code do not any good. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMkrnUACgkQ31DJeiZFuHdafACdGG8Kl+m8OtsnFNNV/mN2u4Mf 2YoAnjVbYgp3shiZQ0/J+DJzhEjorv1/ =6ehf -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.03.2014 00:25, RjOllos wrote: One other thing that's probably not related. In the logs I noticed: 2014-03-11 08:18:59,848 Trac[web_ui] DEBUG: Auth distribution skipped: tmg From reviewing the code in AccountManager 0.4.3, the message seems to be due to an exception trapped in LoginModule_distribute_auth. I assume it is similar in the 0.3.2 version that Bitnami is still using. Steffen, do you have any idea if the message related to anything harmful? Not at all. It notices about finding another Trac env, that has different auth_cookie setting, so it is skipped for distribution authentication data (auth cookie information for new single-sign-on, that has only been introduced during 0.4 development, not available in 0.3.x). Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMk8hoACgkQ31DJeiZFuHcjbwCfUI4obYBdAlgc1JP9113BHjvx jbEAoLChiwaI1USYb0CSiJk6L6B3ldOD =pDin -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac.db questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.2014 18:00, ONeal Freeman wrote: I am migrating trac 0.10.4 from a linux server onto a new trac instance 1.0.1 on windows server. I copied over the trac.db to keep our existing tickets. I have just noticed that the ticket.time, ticket.changetime, and ticket_change.time fields are 0 in the copied db although those fields are correct in the original backed up db. Has anyone else experienced this? No, although I've been moving several Trac environments, version 0.12 from GNU/Linux to Trac 1.1.1 on WinXP myself. I am thinking that this was caused by the trac-admin upgrade command or the installation of the TracTicketTemplatePlugin which apparently adds a new table, ticket_template_store to the db. I know that each such Trac db upgrade leaves a copy of the old (SQLite) db in the env/db/ directory, so you could easily confirm or rule that out yourself. Since the plugin in question does add a new db table but has no business like altering db table 'ticket' I cannot see a justification for such a suspicion. Am I suppose to do a import of some sort to preserve my data? Always keep a full Trac environment copy before changing things. Apart from that Trac will tell you required steps. I've upgraded Trac environments a lot within the last 5 years and never encountered data loss like you suggest that it happened to you. I do not tell you, it is impossible, but highly unlikely, and certainly not normally to expect. There might be some non-obvious things that stepped in your way. Did you copy the db while the environment was active? You should at least us the trac-admin db hot-copy command and only move that offline copy of your db. You might want to move a tar or zip archive instead of the raw db to detect data alteration on archive unpacking time at the target system. These are just some thoughts from the top, without knowing details about your migration process. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMiE3YACgkQ31DJeiZFuHf1pgCgqUZ9rcON/ArmPI8Rpn3q7QMA a6oAnj3hpN3IC+MdTdIZTAsRwG4nPbD4 =L39w -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Trac.db questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.03.2014 21:00, ONeal Freeman wrote: I just determined that the trac-admin path to env upgrade is wiping out the time and timechange fields. Which db upgrade do you mean, a Trac core upgrade module? Steffen Hoffmann PS: Despite of posting below the last message text it has been hard to spot that comment to yourself in your latest message. Would you try to do the e-mail message threading more obviously, please? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMiFJIACgkQ31DJeiZFuHfOzQCgixAb++Cv2iZdCjeQ51yqMGj3 vxIAnR33WOhGW4jkSv8ulR7ieeLLT/fu =ptrw -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Disable notify on BatchModify updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.03.2014 22:41, RjOllos wrote: On Monday, March 3, 2014 6:21:13 AM UTC-8, Rob Weigel wrote: In the new[er] release, I see that some of the BatchModifyPlugin http://trac-hacks.org/wiki/BatchModifyPlugin functionality has been rolled into main product. My question is, is there a way in the new release to disable the ticket notifies when using the native batch modify functionality? The kicker is we still want the notifies sent on the manual, singleton updates. It's not currently possible as far as I can see. It seems like a reasonable request. We can probably add a configuration option if you open a ticket: http://trac.edgewall.org/newticket There is QuietPlugin [1], but that one supports only TracAnnouncer alias AnnouncerPlugin [2]. With batch modification in Trac core I see the need for having similar functionality available as part of the standard too. Btw, I've spammed myself by testing the new TagsPlugin [3] mass tag change admin function on a test instance with 30.000+ tickets, changing almost 10.000 tickets two times in succession - a true nightmare for my private mail server and local inbox. Steffen Hoffmann [1] http://trac-hacks.org/wiki/QuietPlugin [2] http://trac-hacks.org/wiki/AnnouncerPlugin [3] http://trac-hacks.org/wiki/TagsPlugin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMfl4cACgkQ31DJeiZFuHfJsACgoXjHkW3eoTtz7D3LwvKqAKyU qdYAoOkjY1qlSSq7mRhFx3Slk8l/JLOD =NTdS -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, btw, both of you are NOT the only people reading on this list. It might be, that Ryan is very active and often a bit earlier with responses, so I (and maybe others) do not interfere, as long as I can't see what to do more. As Ryan declared he would run low of ideas I step in now, but don't promise to do any better though. On 10.03.2014 14:55, ONeal Freeman wrote: I cleared browser cache but that did not make a difference. The about page does show auto_preview_timeout as 2.0 I edited a wiki page in side-by-side and the changes were not shown in the preview side. I then opened the console and performed the wiki edit again.but the same error was displayed: Uncaught ReferenceError: auto_preview_timeout is not defined I remember your report from earlier test with console interaction. I'm quite sure, that there is an issue with Trac core wiki preview rendering or interference between that and the ticket template plugin. As I do use Trac with that plugin and I know that both can work flawlessly I'm most anxious to see this case resolved. I feel that the auto-preview blocks the plugin from working properly, but I cannot see yet how to nail it down. Could you try to kind of refresh your Trac install to make sure it is really complete? Never heard of a similar issue with for the whole lifetime of this great feature, so I tend to believe it is a local installation issue. The configuration is already confirmed to be ok by you feedback. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMeB1IACgkQ31DJeiZFuHezBwCgsZDJruj8Z1lsymInGyD3BmR8 o/4An23p06FoanZdtqu3h9paI/7IijH0 =uLlU -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Control the default columns of the milestone queries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.03.2014 13:24, RjOllos wrote: On Friday, March 7, 2014 12:51:21 AM UTC-8, Kristian Nørgaard wrote: I am interested in the results that are provided from the roadmap view, when we click to see a list of tickets for a given milestone. I know about the default_query option in trac.ini, but this does not seem to affect this query. Can I control which columns are shown per default? The queries in the milestone progress bars can be customized in the [milestone-groups] section of trac.ini: http://trac.edgewall.org/wiki/TracIni#milestone-groups-section I think, Kristian is asking for customization of the query underneath the various ticket links from progress bar groups, so especially to change default columns, right? Configuration options for trac.ini in [milestone-groups] section are for you [1], so it will change the corresponding links. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracIni#milestone-groups-section -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMeIb8ACgkQ31DJeiZFuHdzlwCeODV5XLBkTFifX6Dvvre7rxML jxcAn3B9OFICDFObXRA1YOO4bC2qKSZG =rJzm -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.03.2014 19:53, ONeal Freeman wrote:
Something I have not mentioned to Ryan is that my site.html does not
include macros.html. I had read where macros.html will be eliminated
from trac very soon. Is it possible that I am missing a important
function which may be contained in the macros.html?
Good, that you mention such things, but the script files in question do
not get included by templates statements but by explicit function calls
('add_script()' from trac.web.chrome) instead.
The script containing the auto-preview js function may even load, but
not get interpreted properly. I thought of a jQuery clash or similar,
but neither have I looked at the corresponding Trac core code nor do I
feel like a JS guru to spot issues in JS code easily.
Anyway, because it works for Ryan, me and any others, we'll have to get
it working for you too. More ideas, anyone? :-)
Steffen Hoffmann
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iEYEARECAAYFAlMeI4QACgkQ31DJeiZFuHfK+ACfQUDTyALrMZkPHPhDLHQzfKyn
XGUAnA0cCN7E4hvDsScpTHxsTkrdOTQm
=IyCo
-END PGP SIGNATURE-
--
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 http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Trac 1.0.1-1 Ticket default description
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.03.2014 20:22, ONeal Freeman wrote: I sincerely appreciate the time you have spent on this with me. Like I said in my first post, I feel like I've read (but not understood) everything on the internet about trac. I've been struggling no less than 6-weeks with getting trac on windows. It hought BitNami would simplify the install... This is no normal issue. I assure you, that I as almost Win noob got Trac to fly by using a BitNami Trac stack in WinXP within less than one hour, then started tweaking for a few more, not more than one day in total. Sorry, we'll still try, just need some more logging or another fresh idea. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMeJHkACgkQ31DJeiZFuHdjWwCfQtsX6WnEaDKJqpT0ILPd5k9Y d+MAoI+Ep83dT6HluLDC9oH2bksAhavg =9SiF -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.03.2014 21:51, RjOllos wrote: Perhaps we need to see take a look at the full log file at DEBUG level, for a session that spans restarting the web server to navigating to the /newticket page. Indeed this was/is what I've been thinking too, more debut logging, please. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMeKocACgkQ31DJeiZFuHdL0ACePEb2uKb/itt4OzS45NmD/uPr zZsAn3desUAVEGznAnYIN5NKv0hgfslt =4+cZ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: TracTicketTemplatePlugIn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.03.2014 23:01, ONeal Freeman wrote: On Monday, March 10, 2014 4:11:38 PM UTC-5, hasienda wrote: On 10.03.2014 21:51, RjOllos wrote: Perhaps we need to see take a look at the full log file at DEBUG level, for a session that spans restarting the web server to navigating to the /newticket page. Indeed this was/is what I've been thinking too, more debut logging, please. So let me see if I understand what you want me to do with the debug log. Start trac and then restart the web server (apache) without exiting trac. Refresh trac and navigate to newticket? Just restart the server, that is providing dynamic Trac content. Capture the log from after restart up to the end of the first request, that shall target /newticket directly. It will show a full Trac environment reload and the request itself. A browser refresh would only lengthen the log without providing additional information. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMeP1gACgkQ31DJeiZFuHe00gCglbxpHY+CRYFvKPigeKUa2CQK eYQAoIzHEerdGdDSrxv4JfkZdVeOZ27b =ogY/ -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] use_base_url_for_redirect= true don't work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04.03.2014 08:27, Arik Pshedezki wrote: I try to use trac standalone (tracd) with stunnel to connect with https. I acted similar to this manual: http://trac.edgewall.org/wiki/STunnelTracd I switched to a ready-made configuration using fcgi when needing https, so I have no own experience with tracd specifically. But I guess you'll get a clue what is going wrong by reading the DEBUG log [1] of such a mis-redirected request. Did you try that already? Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracLogging#LogLevels -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMWp/EACgkQ31DJeiZFuHeE8QCfZj5nRptoAgO2XZGDiK1VOu/Z oCEAoLfGrC47fAHDKBn2tQtucLA+qhzR =1s2j -END PGP SIGNATURE- -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
