Okay, it works now. Just to clarify from previous post, in trac.ini it is
"[components]" not "[component]". And adding under "[components]" was still
necessary before upgrade processed. Thanks again ;)
On Tuesday, February 20, 2018 at 1:32:13 PM UTC-5, David S wrot
Error is occurring on the command line when trying to upgrade the database,
after enabling Agilo plug-in in trac.ini (agilo.* = enabled). Trac is
installed in a virtualenv. After a new project is created, Agilo
installation requires adding to trac.ini. Agilo's docs state only to add
"agilo.* =
traceback?
On Monday, February 19, 2018 at 11:28:18 PM UTC-5, RjOllos wrote:
>
> Please share the full traceback associated with the exception.
>
> Ryan
>
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop re
But yes, multiple uninstalls of TracAccountManager did not prove successful.
On Monday, February 19, 2018 at 11:22:36 PM UTC-5, David S wrote:
>
> Thanks for your quick response! This must be being caused by a different
> issue, although the error message is the same. The error is occur
s okay. Then added agilo.* = enable to
conf/trac.ini. Finally, running trac-admin upgrade results in the above
error.
On Monday, February 19, 2018 at 5:31:52 PM UTC-5, RjOllos wrote:
>
>
>
> On Monday, February 19, 2018 at 10:18:06 AM UTC-8, David S wrote:
>>
>> Tried:
>&
Tried:
$ pip uninstall TracAccountManager
$ pip install svn+https://trac-hacks.org/svn/accountmanagerplugin/trunk
But no succuss.
On Monday, October 9, 2017 at 4:28:48 AM UTC-4, RjOllos wrote:
>
>
>
> On Mon, Oct 9, 2017 at 1:22 AM, Mike Dewhirst > wrote:
>
>> How can I deal with this?
>>
>> T
I could be wrong about this since I'm new to Trac...
But I'm not sure you can split the function of wiki from tickets. LIke
Mark said, that seems to just be a built-in function of Trac itself.
Do you mean you want to "store" wiki pages on server A and the db
(sqlite) tickets on Server B?
I've onl
/whatever so there's no locking contention. If you
> just want to delete the comments from a specific author on a specific ticket:
>
> delete from ticket_change where ticket = 1700 and field = "comment" and
> author="davids";
>
> On Apr 18, 2011, at 1:56
Perfect. That fixed it.
On Apr 15, 12:58 pm, Ryan J Ollos wrote:
> David S-6 wrote:
>
> > Does anyone know the custom setting for the trac.ini file which allows
> > users to be assigned from a menu listing all all the users that have
> > accessed a particular page?
>
arently incorporated into 0.12, anyway.
>
> David
>
> On 2011-04-18, at 1:56 PM, David S wrote:
>
>
>
>
>
>
>
> > Ok, now that I've finally have two newly created projects working I'd
> > figure I'd learn on how SQLite Manager works. I'
Thanks for those who replied. I'll try out those suggestions.
On Apr 15, 12:58 pm, Ryan J Ollos wrote:
> David S-6 wrote:
>
> > Does anyone know the custom setting for the trac.ini file which allows
> > users to be assigned from a menu listing all all the users t
Ok, now that I've finally have two newly created projects working I'd
figure I'd learn on how SQLite Manager works. I've been tasked with
either removing a ticket complete (say, ticket #1700) or finding a way
to remove a comment that exist within ticket #1700. Is the second
option possible or is it
trac-users@googlegroups.com [trac-users@googlegroups.com] on behalf
> > of David S [salinas.d...@gmail.com]
> > Sent: Thursday, April 14, 2011 2:51 PM
> > To: Trac Users
> > Subject: [Trac] Customizing Tickets
>
> > Does anyone know the custom setting for the
up, once they have logged in at least once.
>
> Try adding one other user and permissions and logging them in and see if the
> Assigned-To changes to a choice list with that person in it.
>
>
> From: trac-users@googlegroups.com [tra
ading.
On Apr 14, 3:04 pm, Ryan J Ollos wrote:
> David S-6 wrote:
>
> > So, when you said you went back and "deleted" the first ticket ID 50, you
> > mean you used sqlite manager via firefox?
>
> Yeah, I deleted ticket ID 50 with SQLite Manager in Firefox. Th
Does anyone know the custom setting for the trac.ini file which allows
users to be assigned from a menu listing all all the users that have
accessed a particular page?
Currently, my default ticket only has "Assigned to" as a single field.
But I want to have a list of people that I selected from a
Jason,
Well, I did some searching and found some 2007 and 2009 post in which
someone did the same thing as me. Everyone that responded said that he
should just "rm -r /some/wrong/location/myproject"
During initialization, the 'trac-admin /some/wrong/location/myproject
initenv' went fine and w/out
I inadvertently created a new project under /usr/local/myproject
instead of /usr/local/trac/myproject.
How do I redo this? Can I just edit the trac.ini file and just
manually move the newly created myproject or do I have to run trac-
admin and remove it that way, and just start over?
I'm trying v
Thanks. I'll try that and post the conclusion here.
On Apr 13, 5:57 am, Ryan J Ollos wrote:
> David S-6 wrote:
>
> > Once I create a new Trac project and get my trac.ini and db settings
> > all set. Is there a away for me to edit a config file so that the
> > star
Thanks.
On Apr 12, 9:46 pm, jevans wrote:
> On Apr 12, 4:01 pm, David S wrote:
>
> > I'm new to Trac, so bare with me...
>
> > Each project I support has their own Trac wiki. The addresses, are
> > listed as such.
>
> >https://tracserver1.domain.c
I'm new to Trac, so bare with me...
Each project I support has their own Trac wiki. The addresses, are
listed as such.
https://tracserver1.domain.com/trac/project1
https://tracserver1.domain.com/trac/project2
https://tracserver1.domain.com/trac/project3
But I noticed that if I remove the project
Once I create a new Trac project and get my trac.ini and db settings
all set. Is there a away for me to edit a config file so that the
starting "New Ticket" starts with say, #5000 and not #1 before I hand
it off to the team to start working?
--
You received this message because you are subscribed
22 matches
Mail list logo
