[Trac] Re: trac.ini problem

2021-05-26 Thread Aca Guy
Thanks Ryan, all is explained.

On Wednesday, May 26, 2021 at 11:55:40 AM UTC-5 RjOllos wrote:

> On Wednesday, May 26, 2021 at 7:44:27 AM UTC-7 Aca Guy wrote:
>
>> I probably got a recent automatic update trac and just got the following 
>> message:
>>
>> Internal Server Error
>>
>> TracError: DuplicateOptionError: While reading from 
>> '/home/me/trac/conf/trac.ini' [line 49]: option 'log_level' in section 
>> 'logging' already exists
>>
>> I had two lines in trac.ini:
>> log_level = DEBUG
>> log_level = CRITICAL
>>
>> The trac.ini file had a modification date of 2020 on it, so I didn't 
>> change it yet Trac failed to run.  I removed the CRITICAL line and it ran 
>> fine.
>>
>> Given that I didn't change the .ini file and both lines have been there 
>> for a while, does that indicate a potential bug in a new version of Trac?
>>
>
> Duplicate options are not allowed in Trac 1.5.3 and later.
> https://trac.edgewall.org/ticket/11538
>
> 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/c645dd6f-0f02-4c46-b7ba-be9a091542ddn%40googlegroups.com.


[Trac] Re: trac.ini problem

2021-05-26 Thread RjOllos


On Wednesday, May 26, 2021 at 7:44:27 AM UTC-7 Aca Guy wrote:

> I probably got a recent automatic update trac and just got the following 
> message:
>
> Internal Server Error
>
> TracError: DuplicateOptionError: While reading from 
> '/home/me/trac/conf/trac.ini' [line 49]: option 'log_level' in section 
> 'logging' already exists
>
> I had two lines in trac.ini:
> log_level = DEBUG
> log_level = CRITICAL
>
> The trac.ini file had a modification date of 2020 on it, so I didn't 
> change it yet Trac failed to run.  I removed the CRITICAL line and it ran 
> fine.
>
> Given that I didn't change the .ini file and both lines have been there 
> for a while, does that indicate a potential bug in a new version of Trac?
>

Duplicate options are not allowed in Trac 1.5.3 and later.
https://trac.edgewall.org/ticket/11538

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/01ed9a8b-843f-47a5-9072-fe87bdd5d2c4n%40googlegroups.com.


[Trac] Re: trac.ini upgrade to Trac 1.4.1 results in new [mainnav] ordering

2020-05-31 Thread Aikido Guy
On Friday, May 29, 2020 at 11:47:09 PM UTC-4, RjOllos wrote:

> On Friday, May 29, 2020 at 7:45:08 PM UTC-7, RjOllos wrote:
>
>> On Friday, May 29, 2020 at 7:00:37 PM UTC-7, Aikido Guy wrote:
>>>
>>> I have a global trac.ini file that contains [mainnav] information. This 
>>> global ini file is read-only.
>>>
>>  
I should have also mentioned that:
(1) I created a test environment from scratch and got it to work
(2) I manually modified all entries in my global ini file

I also have a project specfic trac.ini file that is read-and-writable for 
>>> an older version of Trac that inherits the global ini file.
>>>
>>
(3) All of my project specific ini files are read-writable and I let the 
upgrade process rewrite them as needed

When I perform a trac-admin upgrade of the project specific file, the 
>>> process adds a new [mainnav] section (and a new [metanav] section) to the 
>>> project specific trac.ini file
>>> - the new [mainnav] section contains different *.order values than my 
>>> global [mainnav] file
>>> - this results in an unexpected tab ordering when I load it in my browser
>>>
>>> Work around:
>>> - If I comment out this new [mainnav] section in my project trac.ini 
>>> file then my project is displayed with the tabs in the expected order as 
>>> per my global trac.ini file
>>> - No other changes are needed to get it to work properly
>>>
>>> Question:
>>> Is there a way to upgrade all of my 60 projects and keep my [mainnav] 
>>> items in the correct order as per my global trac.ini file?
>>>
>>> In Trac < 1.2, the order is configured through the [trac] mainnav and 
>> [trac] metanav entries:
>> https://trac.edgewall.org/wiki/1.0/TracNavigation#nav-order
>>
>> The db41 upgrade steps writes these to [mainnav] and [metanav] sections:
>> https://trac.edgewall.org/browser/tags/trac-1.4.1/trac/upgrades/db41.py
>>
>> If you are upgrading from Trac < 1.2 your mainnav and metanav ordering 
>> should be configured in the [trac] mainnav and [trac] metanav options
>>
>
> Meaning, the inherited config file you used with Trac < 1.0 should have 
> defined the ordering using the [trac] mainnav and [trac] metanav options
>  
>
>> It likely fails to account for the possibility that [trac] mainnav and 
>> [trac] metanav are configured in an inherited config file. In that case, it 
>> should issue a warning message and not modify the env trac.ini file.
>>
>  
> To the point, there is a defect in the upgrade step that will be dealt 
> with in #11306
>
> However, since that won't get fixed until at least trac.1.4.2, you'll need 
>> a different solution.
>>
>> Unfortunately it's also tr[ue] that "trac-admin $env config remove 
>> mainnav" does not remove the mainnav section.
>>
>> Instead, you'll have to remove each option:
>>
>> for opt in wiki ticket newticket timeline roadmap browser search admin
>> do
>> trac-admin $env config remove mainnav $opt.order
>> done
>>
>> When the last section option is removed, the section header [mainnav] 
>> will also be removed.
>>
>> * https://trac.edgewall.org/ticket/13305
>> * https://trac.edgewall.org/ticket/13306 
>>
>
Thank you for the for loop above and the comment below it. I added such a 
thing after the upgrade in order to "corrrect" my project specific ini 
files.
- I just tested this process on one of my projects and it works as 
advertised...

Thank you kindly!
Aikido Guy

-- 
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/83d86000-ea4d-4125-9bfc-5435d5891928%40googlegroups.com.


[Trac] Re: trac.ini upgrade to Trac 1.4.1 results in new [mainnav] ordering

2020-05-29 Thread RjOllos


On Friday, May 29, 2020 at 7:45:08 PM UTC-7, RjOllos wrote:

A few clarifications.

On Friday, May 29, 2020 at 7:00:37 PM UTC-7, Aikido Guy wrote:
>>
>> Hi,
>>
>> I have a global trac.ini file that contains [mainnav] information. This 
>> global ini file is read-only.
>>
>> I also have a project specfic trac.ini file that is read-and-writable for 
>> an older version of Trac that inherits the global ini file.
>>
>> When I perform a trac-admin upgrade of the project specific file, the 
>> process adds a new [mainnav] section (and a new [metanav] section) to the 
>> project specific trac.ini file
>> - the new [mainnav] section contains different *.order values than my 
>> global [mainnav] file
>> - this results in an unexpected tab ordering when I load it in my browser
>>
>> Work around:
>> - If I comment out this new [mainnav] section in my project trac.ini file 
>> then my project is displayed with the tabs in the expected order as per my 
>> global trac.ini file
>> - No other changes are needed to get it to work properly
>>
>> Question:
>> Is there a way to upgrade all of my 60 projects and keep my [mainnav] 
>> items in the correct order as per my global trac.ini file?
>>
>> Kindly,
>> Aikido Guy
>>
>
> In Trac < 1.2, the order is configured through the [trac] mainnav and 
> [trac] metanav entries:
> https://trac.edgewall.org/wiki/1.0/TracNavigation#nav-order
>
> The db41 upgrade steps writes these to [mainnav] and [metanav] sections:
> https://trac.edgewall.org/browser/tags/trac-1.4.1/trac/upgrades/db41.py
>
> If you are upgrading from Trac < 1.2 your mainnav and metanav ordering 
> should be configured in the [trac] mainnav and [trac] metanav options
>

Meaning, the inherited config file you used with Trac < 1.0 should have 
defined the ordering using the [trac] mainnav and [trac] metanav options
 

> It likely fails to account for the possibility that [trac] mainnav and 
> [trac] metanav are configured in an inherited config file. In that case, it 
> should issue a warning message and not modify the env trac.ini file.
>
 
To the point, there is a defect in the upgrade step that will be dealt with 
in #11306

However, since that won't get fixed until at least trac.1.4.2, you'll need 
> a different solution.
>
> Unfortunately it's also tr[ue] that "trac-admin $env config remove 
> mainnav" does not remove the mainnav section.
>
> Instead, you'll have to remove each option:
>
> for opt in wiki ticket newticket timeline roadmap browser search admin
> do
> trac-admin $env config remove mainnav $opt.order
> done
>
> When the last section option is removed, the section header [mainnav] will 
> also be removed.
>
> * https://trac.edgewall.org/ticket/13305
> * https://trac.edgewall.org/ticket/13306 
>

-- 
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/45275fbe-504d-4dc6-88c6-43da6ef2190e%40googlegroups.com.


[Trac] Re: trac.ini upgrade to Trac 1.4.1 results in new [mainnav] ordering

2020-05-29 Thread RjOllos
On Friday, May 29, 2020 at 7:00:37 PM UTC-7, Aikido Guy wrote:
>
> Hi,
>
> I have a global trac.ini file that contains [mainnav] information. This 
> global ini file is read-only.
>
> I also have a project specfic trac.ini file that is read-and-writable for 
> an older version of Trac that inherits the global ini file.
>
> When I perform a trac-admin upgrade of the project specific file, the 
> process adds a new [mainnav] section (and a new [metanav] section) to the 
> project specific trac.ini file
> - the new [mainnav] section contains different *.order values than my 
> global [mainnav] file
> - this results in an unexpected tab ordering when I load it in my browser
>
> Work around:
> - If I comment out this new [mainnav] section in my project trac.ini file 
> then my project is displayed with the tabs in the expected order as per my 
> global trac.ini file
> - No other changes are needed to get it to work properly
>
> Question:
> Is there a way to upgrade all of my 60 projects and keep my [mainnav] 
> items in the correct order as per my global trac.ini file?
>
> Kindly,
> Aikido Guy
>

In Trac < 1.2, the order is configured through the [trac] mainnav and 
[trac] metanav entries:
https://trac.edgewall.org/wiki/1.0/TracNavigation#nav-order

The db41 upgrade steps writes these to [mainnav] and [metanav] sections:
https://trac.edgewall.org/browser/tags/trac-1.4.1/trac/upgrades/db41.py

If you are upgrading from Trac < 1.2 your mainnav and metanav ordering 
should be configured in the [trac] mainnav and [trac] metanav options.

It likely fails to account for the possibility that [trac] mainnav and 
[trac] metanav are configured in an inherited config file. In that case, it 
should issue a warning message and not modify the env trac.ini file.

However, since that won't get fixed until at least trac.1.4.2, you'll need 
a different solution.

Unfortunately it's also try that "trac-admin $env config remove mainnav" 
does not remove the mainnav section.

Instead, you'll have to remove each option:

for opt in wiki ticket newticket timeline roadmap browser search admin
do
trac-admin $env config remove mainnav $opt.order
done

When the last section option is removed, the section header [mainnav] will 
also be removed.

* https://trac.edgewall.org/ticket/13305
* https://trac.edgewall.org/ticket/13306

-- 
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/af663a44-0b77-41de-b073-7d46e4da5f04%40googlegroups.com.


Re: [Trac] Re: Trac.ini

2017-07-11 Thread toto200891
Thank you very much Mark.

Regards,
SF 

On Tuesday, July 11, 2017 at 10:52:17 AM UTC+2, Cooke, Mark wrote:
>
> > -Original Message- 
> > From: trac-...@googlegroups.com  On Behalf Of toto200891 
> > Sent: 11 July 2017 09:42 
> > 
> > I am sorry for not being clear. I will try to explain again, in the 
> current 
> > TRAC installation, in the admin panel we have 4 components: General, 
> > Accounts, Ticket systems, and version control. Similar to that is it 
> possible 
> > to have an another component named "TRAC.ini", So that I can access and 
> edit 
> > the trac.ini file directly within the TRAC environment. 
> > 
> > I hope that I am clear now. 
>
> Much better. 
>
> Check out https://trac-hacks.org for all sorts of useful stuff to extend 
> Trac. 
>
> For your query, a quick google using "trac hacks trac ini" highlighted two 
> plugins: 
>
> 1) TracIniAdminPanelPlugin 
>
> 2) IniAdminPlugin 
>
> (1) includes a comparison with (2) and is also compatible with Trac 1.0+ 
>
> Regards, 
>
> ~ Mark C 
>
> > Regards, 
> > SF 
> > 
> > On Tuesday, July 11, 2017 at 7:53:55 AM UTC+2, hasienda wrote: 
> > 
> > Am 9. Juli 2017 22:13:00 MESZ schrieb toto200891 
> >  >: 
> > 
> > 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 
> > 
> > 
> > 
> > 
> > 
> > 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to trac-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/trac-users. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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

2017-07-11 Thread Cooke, Mark
> -Original Message-
> From: trac-users@googlegroups.com On Behalf Of toto200891
> Sent: 11 July 2017 09:42
> 
> I am sorry for not being clear. I will try to explain again, in the current
> TRAC installation, in the admin panel we have 4 components: General,
> Accounts, Ticket systems, and version control. Similar to that is it possible
> to have an another component named "TRAC.ini", So that I can access and edit
> the trac.ini file directly within the TRAC environment.
> 
> I hope that I am clear now.

Much better.

Check out https://trac-hacks.org for all sorts of useful stuff to extend Trac.

For your query, a quick google using "trac hacks trac ini" highlighted two 
plugins:

1) TracIniAdminPanelPlugin

2) IniAdminPlugin

(1) includes a comparison with (2) and is also compatible with Trac 1.0+

Regards,

~ Mark C

> Regards,
> SF
> 
> On Tuesday, July 11, 2017 at 7:53:55 AM UTC+2, hasienda wrote:
> 
>   Am 9. Juli 2017 22:13:00 MESZ schrieb toto200891
>  >:
> 
>   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
> 
> 
> 
> 
> 
> 
>   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.

-- 
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

2017-07-11 Thread toto200891
I am sorry for not being clear. I will try to explain again, in the current 
TRAC installation, in the admin panel we have 4 components: General, 
Accounts, Ticket systems, and version control. Similar to that is it 
possible to have an another component named "TRAC.ini", So that I can 
access and edit the trac.ini file directly within the TRAC environment. 

I hope that I am clear now.

Regards,
SF

On Tuesday, July 11, 2017 at 7:53:55 AM UTC+2, hasienda wrote:
>
> Am 9. Juli 2017 22:13:00 MESZ schrieb toto200891  >:
>>
>> 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
>>>  
>>>
>>
>
> 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

2017-07-10 Thread Steffen Hoffmann
Am 9. Juli 2017 22:13:00 MESZ schrieb toto200891 :
>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

2017-07-10 Thread Steffen Hoffmann
Am 7. Juli 2017 20:26:30 MESZ schrieb RjOllos :
>
>
>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.


[Trac] Re: Trac.ini

2017-07-10 Thread RjOllos


On Sunday, July 9, 2017 at 4:13:00 PM UTC-4, toto200891 wrote:
>
> Yes. is it possible?
>
> Regards,
> SF
>

I don't know, because I still don't understand what question you are asking.

- 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.


[Trac] Re: Trac.ini

2017-07-09 Thread toto200891
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.


[Trac] Re: Trac.ini

2017-07-07 Thread RjOllos


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.


[Trac] Re: trac.ini Config to Browse SVN with Trac

2009-06-11 Thread mona

Hi,
   This is trac.ini of project which synchronized with SVN
# -*- coding: utf-8 -*-

[attachment]
max_size = 262144
render_unsafe_content = false

[browser]
color_scale = True
downloadable_paths = /trunk, /branches/*, /tags/*
hide_properties = svk:merge
intermediate_color =
intermediate_point =
newest_color = (255, 136, 136)
oldest_color = (136, 136, 255)
oneliner_properties = trac:summary
render_unsafe_content = false
wiki_properties = trac:description

[changeset]
max_diff_bytes = 1000
max_diff_files = 0
wiki_format_messages = true

[datefield]
first_day = 0
format = dmy
separator = /

[header_logo]
alt = (please configure the [header_logo] section in trac.ini)
height = -1
link =
src = site/your_project_logo.png
width = -1

[inherit]
plugins_dir =
templates_dir =

[logging]
log_file = trac.log
log_level = DEBUG
log_type = none

[mastertickets]
dot_path = dot
gs_path = gs
use_gs = False

[milestone]
stats_provider = DefaultTicketGroupStatsProvider

[mimeviewer]
enscript_modes = text/x-dylan:dylan:4
enscript_path = enscript
max_preview_size = 262144
mime_map = text/x-dylan:dylan,text/x-idl:ice,text/x-ada:ads:adb
php_path = php
tab_width = 8

[notification]
admit_domains =
always_notify_owner = true
always_notify_reporter = false
always_notify_updater = true
ignore_domains =
mime_encoding = base64
smtp_always_bcc =
smtp_always_cc =
smtp_default_domain = persistent.co.in
smtp_enabled = true
smtp_from = psltrac_internal
smtp_from_name =
smtp_password =
smtp_port = false
smtp_replyto =
smtp_server = ps0672.persistent.co.in
smtp_subject_prefix = default
smtp_user =
ticket_subject_template = $prefix #$ticket.id: $summary
use_public_cc = false
use_short_addr = false
use_tls = false

[project]
admin =
contact =
descr = My example project
footer = Visit the Trac open source project athttp://trac.edgewall.org/
icon = common/trac.ico
name = console_svn
repository_dir = C:\projects_old\svn\trac_n

[query]
default_anonymous_query = status!=closed&cc~=$USER
default_query = status!=closed&owner=$USER
items_per_page = 100

[report]
items_per_page = 100
items_per_page_rss = 0

[revisionlog]
default_log_limit = 100

[roadmap]
stats_provider = DefaultTicketGroupStatsProvider

[search]
min_query_length = 3

[svn]
branches = trunk,branches/*
tags = tags/*

[theme]
theme = CMTeknik

[ticket]
default_cc =
default_component =
default_description =
default_keywords =
default_milestone =
default_owner =
default_priority = major
default_resolution = fixed
default_severity =
default_summary =
default_type = defect
default_version =
max_comment_size = 262144
max_description_size = 262144
preserve_newlines = default
restrict_owner = false
workflow = ConfigurableTicketWorkflow

[ticket-workflow]
accept = new,assigned,accepted,reopened -> accepted
accept.operations = set_owner_to_self
accept.permissions = TICKET_MODIFY
leave = * -> *
leave.default = 1
leave.operations = leave_status
reassign = new,assigned,accepted,reopened -> assigned
reassign.operations = set_owner
reassign.permissions = TICKET_MODIFY
reopen = closed -> reopened
reopen.operations = del_resolution
reopen.permissions = TICKET_CREATE
resolve = new,assigned,accepted,reopened -> closed
resolve.operations = set_resolution
resolve.permissions = TICKET_MODIFY

[timeline]
abbreviated_messages = True
changeset_collapse_events = false
changeset_long_messages = false
changeset_show_files = 0
default_daysback = 30
max_daysback = 90
newticket_formatter = oneliner
ticket_show_details = false

[trac]
authz_file =
authz_module_name =
auto_reload = False
base_url =
check_auth_ip = false
database = sqlite:db/trac.db
default_charset = iso-8859-15
default_handler = WikiModule
default_timezone =
htdocs_location =
ignore_auth_case = false
mainnav = wiki,timeline,roadmap,browser,tickets,newticket,search
metanav = login,logout,prefs,help,about
permission_policies = DefaultPermissionPolicy, LegacyAttachmentPolicy
permission_store = DefaultPermissionStore
repository_dir = C:\projects_old\svn\trac_new
repository_type = svn
secure_cookies = False
show_email_addresses = false
timeout = 20
use_base_url_for_redirect = False

[wiki]
ignore_missing_pages = false
max_size = 262144
render_unsafe_content = false
split_page_names = false


mona


On Jun 11, 4:40 pm, jm voodoo child  wrote:
> Hi,
>
> Could someone who succeed to browse SVN ( runned with SVNserver) with trac 
> give me his trac.ini ?
>
> I'm desperate. :-)
>
> jm.
>
>
>
> > Date: Thu, 11 Jun 2009 04:12:17 -0700
> > Subject: [Trac] How to set the data globally in Trac system
> > From: prabhakar2...@gmail.com
> > To: trac-users@googlegroups.com
>
> > Hi,
>
> >   i need to set the data globally, means suppose i have set one
> > variable name as "Temp_var" with some data. i want to access that
> > variable in whole Trac.
> > e.g:
> >  "auth.name" is global variable that contains current login user name
> > and it is accessible for whole Trac, similarly i want to set global
> > variable like "auth.name"
>
> > can anybody suggest me
>

[Trac] Re: trac.ini Config to Browse SVN with Trac

2009-06-11 Thread Olemis Lang

On Thu, Jun 11, 2009 at 6:40 AM, jm voodoo child wrote:
>
> Hi,
>

Hi !

> Could someone who succeed to browse SVN ( runned with SVNserver)

AFAIK whether SVNServe is in use or not is not relevant to Trac
itself. You could also try to setup Subversion using Apache Webdav
module.

In trac.ini the only thing needed is to config the path to the repos
folder so that Trac be able to read it's contents (pls see options
help at TracIni wiki page ;)

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:
Diseño: Tema PyTpp, ahora Trac se parece más a Python  -
http://feedproxy.google.com/~r/simelo-es/~3/kqlIJsOiG0g/diseno-tema-pytpp-ahora-trac-se-parece.html

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: trac.ini

2008-05-29 Thread Erik Andersson
You need to restart Trac (apache, tracd or whatever frontend you use) to
make changes load.

Cheers / Erik

On Fri, May 30, 2008 at 12:35 AM, Eric Polino <[EMAIL PROTECTED]>
wrote:

>
> Ahh, what I was playing with isn't right.  It was found somewhere else
> on my drive.  I think I've got it now, there are all kinds of settings
> in it.  When I make changes to this file, nothing happens either.  I'm
> just trying to turn off highlighting of missing pages, which according
> to the TracIni page on the wiki, is available since 0.9 (i'm running
> 0.10).
>
> On Thu, May 29, 2008 at 4:50 PM, Chris Mulligan
> <[EMAIL PROTECTED]> wrote:
> > Your trac.ini should have many lines in it, even if you haven't edited
> it.
> > What are the files/directories in /var/www/localhost/htdocs/trac? It
> should
> > have the standard trac files. On 0.12 that's: attachments, conf, db,
> htdocs,
> > log, plugins, README, templates, VERSION. Find that file and you should
> be
> > good to go.
> >
> > On Thu, May 29, 2008 at 2:59 PM, Aluink <[EMAIL PROTECTED]> wrote:
> >>
> >> I am trying to set some stuff up in my trac.ini but my changes aren't
> >> being reflected on the wiki.  I'm running 0.10.4.  My trac.ini is
> >> found in /var/www/localost/htdocs/trac/conf.  Right now I only have
> >> the following in it.  I'm trying to keep it simple until I can see it
> >> working.
> >>
> >> [wiki]
> >> ignore_missing_pages = enable
> >>
> >> Let me know if there is any information that could better help you
> >> help me.
> >>
> >> TIA,
> >> Eric
> >>
> >>
> >
> >
> > >
> >
>
>
>
> --
> Eric Polino
> Campground Automated Systems
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: trac.ini

2008-05-29 Thread Eric Polino

Ahh, what I was playing with isn't right.  It was found somewhere else
on my drive.  I think I've got it now, there are all kinds of settings
in it.  When I make changes to this file, nothing happens either.  I'm
just trying to turn off highlighting of missing pages, which according
to the TracIni page on the wiki, is available since 0.9 (i'm running
0.10).

On Thu, May 29, 2008 at 4:50 PM, Chris Mulligan
<[EMAIL PROTECTED]> wrote:
> Your trac.ini should have many lines in it, even if you haven't edited it.
> What are the files/directories in /var/www/localhost/htdocs/trac? It should
> have the standard trac files. On 0.12 that's: attachments, conf, db, htdocs,
> log, plugins, README, templates, VERSION. Find that file and you should be
> good to go.
>
> On Thu, May 29, 2008 at 2:59 PM, Aluink <[EMAIL PROTECTED]> wrote:
>>
>> I am trying to set some stuff up in my trac.ini but my changes aren't
>> being reflected on the wiki.  I'm running 0.10.4.  My trac.ini is
>> found in /var/www/localost/htdocs/trac/conf.  Right now I only have
>> the following in it.  I'm trying to keep it simple until I can see it
>> working.
>>
>> [wiki]
>> ignore_missing_pages = enable
>>
>> Let me know if there is any information that could better help you
>> help me.
>>
>> TIA,
>> Eric
>>
>>
>
>
> >
>



-- 
Eric Polino
Campground Automated Systems

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: trac.ini

2008-05-29 Thread Chris Mulligan
Your trac.ini should have many lines in it, even if you haven't edited it.
What are the files/directories in /var/www/localhost/htdocs/trac? It should
have the standard trac files. On 0.12 that's: attachments, conf, db, htdocs,
log, plugins, README, templates, VERSION. Find that file and you should be
good to go.

On Thu, May 29, 2008 at 2:59 PM, Aluink <[EMAIL PROTECTED]> wrote:

>
> I am trying to set some stuff up in my trac.ini but my changes aren't
> being reflected on the wiki.  I'm running 0.10.4.  My trac.ini is
> found in /var/www/localost/htdocs/trac/conf.  Right now I only have
> the following in it.  I'm trying to keep it simple until I can see it
> working.
>
> [wiki]
> ignore_missing_pages = enable
>
> Let me know if there is any information that could better help you
> help me.
>
> TIA,
> Eric
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: Trac.ini inherit options

2008-05-23 Thread Noah Kantrowitz

On May 22, 2008, at 3:55 PM, Jason Winnebeck wrote:
>
> In the inherit section, I can specify a location for shared plugins  
> and
> templates. Is there a shared chrome directory? What I want to do is
> create a template (I already did) that lets me inject a style sheet.
> I've done this already with ${href.chrome('site/style.css')} in a  
> Genshi
> template; however, I have to copy style.css into each Trac instance  
> even
> though the template is inherited. Any suggestions?

I would either 1) make a small plugin to bundle this up or 2) put the  
CSS file somewhere other then env's htdocs folder, though if you use  
tracd this is harder.

--Noah

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: Trac.ini deletes my existing tickets

2008-03-30 Thread Jeroen Ruigrok van der Werven

-On [20080329 12:10], Barrow, Robin ([EMAIL PROTECTED]) wrote:
>When I updated the trac.ini file - all existing tickets were no longer there. I
>could not longer see them or anything. What did I do wrong?
>I want to make updates to the trac.ini file on an existing system - so I cannot
>lose the tickets at all.

Simply editing your .ini file will not delete tickets.

The only reason I can quickly come up with is a wrong database connection
string.

-- 
Jeroen Ruigrok van der Werven  / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
Where can I find a man who has forgotten words? I would like to have a word
with him...

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: Trac.ini deletes my existing tickets

2008-03-30 Thread 胡争辉
Please check your database directly, you can find the name of tables that
related with ticket in the link below:

http://trac.edgewall.org/wiki/TracDev/DatabaseSchema

2008/3/22, Barrow, Robin <[EMAIL PROTECTED]>:
>
>  I am a very new user. Any suggestion for this?
>
>  When I updated the trac.ini file - all existing tickets were no longer
> there. I could not longer see them or anything. What did I do wrong?
> I want to make updates to the trac.ini file on an existing system - so I
> cannot lose the tickets at all.
>
> Thanks,
>
>  
> *Robin Barrow*
> *SEIT SW Configuration Management*
> *AAI Services*
> *(843) 574-5245*
>
>
> --
> This E-mail and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to which they are
> addressed. Please note that any views or opinions presented in this E-mail
> are solely those of the author and do not necessarily represent those of the
> company. Finally, the recipient should check this E-mail and any attachments
> for the presence of viruses. The company accepts no liability for any damage
> caused by any virus transmitted by this E-mail. If you have received this
> E-mail in error please notify the system manager,
> [EMAIL PROTECTED]
>
>
> >
>


-- 
QQ: 443089607
QQ mail: [EMAIL PROTECTED]
Skype: huzhenghui
Gtalk: huzhengh
GMail: [EMAIL PROTECTED]

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: trac.ini global/local question

2007-02-07 Thread Eric \"Shubes\"

Markus Wolf wrote:
> Hi,
> 
> i am not sure about which trac.ini is read for what situation. can someone 
> tell me which is stronger, or how they are used by TRAC?
> 
> Greetings
> Markus
> 
http://trac.edgewall.org/wiki/TracIni

-- 
-Eric 'shubes'

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---