Provide mechanism to apply wiki macros to all wiki pages

[ilias@…]

In order to customize trac wiki contents, wiki macros can be used.

Several macros are used in every wiki page, but it is inconvenient to add the macro-call to every page.

A solution would be to provide an trac.ini section, where the global wiki macro's statements can be placed.

[global_wiki_macros]
AutoNav = ""
TracNav = "MyToc"

or simpler

[wiki]
global_wiki_macros = AutoNav, TracNav(MyToc)

Alternatively, an mechanism could be provided, thus plugin developers can serve users with the ability to switch macros globally on/off.

See ​this thread describing an example implementation (based on a workaround).

[Christian Boos]

Quoting the linked mail:

I would like to provide a wiki template in order to include the TracNav Macro (and some others) by default.

You can use PageTemplates to achieve this.

owner changed from jonas to cboos.

… and please, refrain from setting the owner yourself, that's the responsibility of the Trac developers.

[ilias@…]

Replying to cboos:

Quoting the linked mail:

I would like to provide a wiki template in order to include the TracNav Macro (and some others) by default.

You can use PageTemplates to achieve this.

No I can't.

Thats a static solution.

My suggestion subjects a dynamic one (e.g. ability to switch global wiki macros on/off)

owner changed from jonas to cboos.

… and please, refrain from setting the owner yourself, that's the responsibility of the Trac developers.

No, it isn't (see TracTicketTriage).

(You should possibly change the t.e.o configuration, to use 'undecided' or instead of 'jonas'.)

[Matthew Good]

Replying to ilias@lazaridis.com:

Replying to cboos:

Quoting the linked mail:

I would like to provide a wiki template in order to include the TracNav Macro (and some others) by default.

You can use PageTemplates to achieve this.

No I can't.

Thats a static solution.

My suggestion subjects a dynamic one (e.g. ability to switch global wiki macros on/off)

Ok, so this is a duplicate of #4423.

owner changed from jonas to cboos.

… and please, refrain from setting the owner yourself, that's the responsibility of the Trac developers.

No, it isn't (see TracTicketTriage).

TracTicketTriage at no point mentions that users should change the owner of a ticket. This is not the first time you've been asked not to change the owner of a ticket. So, you can stop playing dumb and either follow the requests of the developers or stop using this site.

[ilias@…]

Replying to mgood:

Replying to ilias@lazaridis.com:

Replying to cboos:

Quoting the linked mail:

I would like to provide a wiki template in order to include the TracNav Macro (and some others) by default.

You can use PageTemplates to achieve this.

No I can't.

Thats a static solution.

My suggestion subjects a dynamic one (e.g. ability to switch global wiki macros on/off)

Ok, so this is a duplicate of #4423.

No, it's not.

Just review the 2 tickets (or ask for more information if something is unclear).

owner changed from jonas to cboos.

… and please, refrain from setting the owner yourself, that's the responsibility of the Trac developers.

No, it isn't (see TracTicketTriage).

TracTicketTriage at no point mentions that users should change the owner of a ticket. This is not the first time you've been asked not to change the owner of a ticket. So, you can stop playing dumb and either follow the requests of the developers or stop using this site.

Please get serious.

I will change any field that this software allows me to change, except a written policy states the opposite.

[Christian Boos]

The written policy is the following:

The TracTeam has lost enough time dealing with Mr. Lazaridis, and it won't accept to loose any further time. So Mr. Ilias Lazaridis is explicitely forbidden to participate to Trac developement by modifying anything in this Trac instance, including creating new tickets, writing comments or modifying wiki pages.
In other words, thanks, we're done with you, go harass some other project if you really can't help being a nuisance.

— ChristianBoos, on behalf of the TracTeam.

Any violation of this written policy will be followed by a formal banning of Mr. Lazaridis from this Trac and any Trac related resource we manage.

So, please, stand by your decision (quoting ​your mail on Trac-Dev):

I will not come back to trac, because the low-evolution-speed of this project.

Our "low evolution speed"(sic) project has no need to be slowed down even more thanks to your pestering attitude.

[Markus Tacker <m@…>]

Word!

To Mr. Ilias Lazaridis: You are always free to take the projects code and modify it to your needs. Or at least pay someone to do it. Arguing with the developers in teh way you did is always a bad idea. Be proactive and do something for them before you ask them a favour.

[Christian Boos]

Sadly, as expected, Mr. Lazaridis didn't take into consideration the policy corresponding to his "contributions" (his last comments here were deleted).

His new submissions are going to be blocked automatically. This is not about censorship, merely spam prevention: one would censor ideas or opinions, but not rants and other blatant trolling.

For reference:

• ​http://www.zenspider.com/Languages/Ruby/IliasIsCrazy.html
• ​http://www.answers.com/topic/ilias-lazaridis
• … and thousands more evidence in the Internet and (unfortunately) in this Trac and on Trac related mailing lists

[ilias@…]

Replying to cboos:

Sadly, as expected, Mr. Lazaridis didn't take into consideration the policy corresponding to his "contributions" (his last comments here were deleted).

His new submissions are going to be blocked automatically. This is not about censorship, merely spam prevention: one would censor ideas or opinions, but not rants and other blatant trolling.

this is censorship.

resend of my message:

"

I don't understand why you've set 'wontfix' for this ticket, as this functionality would be usable, especially for larger installments. anyway.

I depend for some time on trac, but i've decided to not 'come back' to full-time-development, thus minimizing efforts to the minimal.

Thus, please take your lessons subjecting 'policies' from e.g. the "Apache Foundation", as I'll not invest time to explain you the obvious. Of course, I could change the [​http://case.lazaridis.com/ticket/40 identified strength] of the trac project.

"

[ilias@…]

Replying to Markus Tacker <m@tacker.org>:

Word!

To Mr. Ilias Lazaridis: You are always free to take the projects code and modify it to your needs. Or at least pay someone to do it. Arguing with the developers in teh way you did is always a bad idea. Be proactive and do something for them before you ask them a favour.

RESEND:

"

I am not asking them for a favour.

Some ​further notes subjecting my efforts.

And the main reason for the teams hostility:

​http://case.lazaridis.com/wiki/TracAudit

"