On Tuesday, May 16, 2017 at 1:53:03 PM UTC-7, RjOllos wrote:
>
>
>
> On Tuesday, May 16, 2017 at 12:33:49 PM UTC-7, bampo...@upenn.edu wrote:
>>
>> We are creating a new TRAC server. The current server runs TRAC .12 on
>> CentOS 5.11. The new server is CentOS 7.3. So, the following questions:
On Tuesday, May 16, 2017 at 12:33:49 PM UTC-7, bampo...@upenn.edu wrote:
>
> We are creating a new TRAC server. The current server runs TRAC .12 on
> CentOS 5.11. The new server is CentOS 7.3. So, the following questions:
>
> 1. If we install TRAC 1.2 on the new server, is there a migration
On Tuesday, May 16, 2017 at 6:44:07 AM UTC-7, toto200891 wrote:
>
> Hi,
>
> I got this error after installing annoncer plugin
>
> AttributeError: 'Environment' object has no attribute 'get_db_cnx'
>
> File "build/bdist.win32/egg/trac/web/main.py", line 623, in _dispatch_request
> dispatcher.d
We are creating a new TRAC server. The current server runs TRAC .12 on
CentOS 5.11. The new server is CentOS 7.3. So, the following questions:
1. If we install TRAC 1.2 on the new server, is there a migration path for
our TRAC .12 data to TRAC 1.2?
2. If we prefer to stay with TRAC .12, is
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 quote
Hi,
I got this error after installing annoncer plugin
AttributeError: 'Environment' object has no attribute 'get_db_cnx'
File "build/bdist.win32/egg/trac/web/main.py", line 623, in _dispatch_request
dispatcher.dispatch(req)
File "build/bdist.win32/egg/trac/web/main.py", line 239, in dispatch
Hi,
Will this policy allow a user with TICKET_VIEW_STATUS permission to view
tickets whose status is TEST? Please have a look at policy below:
# -*- coding: utf-8 -*-
#
# Copyright (C) 2017 Edgewall Software
# All rights reserved.
#
# This software is licensed as described in the file COPYING, w
On Tue, May 16, 2017 at 1:17 AM Roger Oberholtzer <
roger.oberholt...@gmail.com> wrote:
> On Tue, May 16, 2017 at 9:18 AM, Ryan Ollos wrote:
> >
> >
> > On Mon, May 15, 2017 at 11:09 PM Roger Oberholtzer
> > wrote:
> >>
> >> When I do a batch modify of a field (Trac 1.2), I often get this error:
On Tue, May 16, 2017 at 9:18 AM, Ryan Ollos wrote:
>
>
> On Mon, May 15, 2017 at 11:09 PM Roger Oberholtzer
> wrote:
>>
>> When I do a batch modify of a field (Trac 1.2), I often get this error:
>>
>> Trac detected an internal error:
>>
>> ValueError: invalid literal for int() with base 10: 'um:'
On Tue, May 16, 2017 at 12:22 AM toto200891
wrote:
> Hi
>
> Same like SupportPolicy, is it possible to restrict the view of tickets to
> users based on Ticket status? As in, if there is certain group named
> testers, and tickets with being status TESTING, should only be viewed to
> testers and th
Hi
Same like SupportPolicy, is it possible to restrict the view of tickets to
users based on Ticket status? As in, if there is certain group named testers,
and tickets with being status TESTING, should only be viewed to testers and
they should not be able to see all the new tickets. Is this pos
On Monday, May 15, 2017 at 8:27:57 AM UTC-7, emecas wrote:
>
> MultipleWorkflowPlugin works for that
>
> https://trac-hacks.org/wiki/MultipleWorkflowPlugin
>
> MC
>
Keep an eye on #13106 for forthcoming Trac 1.2 compatibility.
https://trac-hacks.org/ticket/13106
- Ryan
--
You received this
On Mon, May 15, 2017 at 11:09 PM Roger Oberholtzer <
roger.oberholt...@gmail.com> wrote:
> When I do a batch modify of a field (Trac 1.2), I often get this error:
>
> Trac detected an internal error:
>
> ValueError: invalid literal for int() with base 10: 'um:'
>
> File
> "/usr/lib/python2.7/site-
13 matches
Mail list logo