Remove cookie-stripping behaviour from Trac Ticket caching

As per previous discussions, can we please remove the Trac Caching that strips the Set-Cookie headers from Trac ticket pages?

As mentioned, this causes failures to comment on tickets –

As discussed, you’ll find a hacky Trac plugin that attempts to avoid setting useless Trac cookies in but it’s mostly untested and may not work as needed.

The Latest trac plugin is in and has been tested well on a standalone trac installation.
The plugin does several things:
– Prevents Cookies being sent on anonymous pageviews
– Prevents anonymous sessions being saved to the DB (as there’s no such thing anymore)
– Blocks access to /prefs for anonymous users
– Expires all trac_* cookies after the user is no longer authenticated, such as to remove the trac_form_token cookie.

#trac #prio1

Can bbPress.trac please get Core’s…

Can bbPress.trac please get Core’s Ticket Workflow enabled for it? Same as Meta/BuddyPress already have.


#prio3 #trac

As per can we…

As per can we update all of the Trac instances to have default_charset = utf-8?

A number of Trac instances are set to default_charset = iso-8859-15.

#prio3 #trac

Remove ‘branch’ functionality from

As reported by #3686-meta the theme ‘Branches’ is appearing as a special item in the code browser.

Could the following rules be added to wp-themes/conf/trac.ini under [svn] to disable Trac’s default svn structure handling which we don’t use on that instance?

(I’ve tested that this works as expected under a local trac)

#prio3 #trac


Hello, can someone please change…

Hello, can someone please change the redirect for * from to Thanks!

Meta ticket: #2029-meta

#prio3 #trac


#1641meta has pointed out that plugins trac wordpress…

#1641meta has pointed out that is missing ~8400 changesets.

Can we do something to import those missing changesets? As we’re running Trac with explicit synchronization, I think it might just be a case of running trac-admin changeset added for each of the missing revisions.

#plugins-trac, #trac

@otto42 can you please give my account access…

@otto42, can you please give my account access to close tickets on themes.trac? I need to test out some i18n changes to the theme upload script and don’t want to clutter the trac w/ a bunch of open test tickets.


What can we do to improve the speed…

What can we do to improve the speed and reliability of Trac? I am seeing two issues in particular: it is terribly slow to complete a request, and web service gets restarted often due to the box maxing out memory.

Possible ideas:

  • We could move from prefork back to threaded mpm to improve memory usage, but then mysql connections become blocking. What’s a possible solution for this?
  • Move Trac from Apache to nginx or using nginx as a frontend proxy, which would include a short-lived cache for reports and for users who aren’t logged in. Or, could we configure the existing load balancers in front of it?

I’m most interested in nginx as a frontend proxy through the existing load balancers, as it seems like it’d be the easiest to set up and give us a decent benefit.


Can a new wp build Trac environment please…

Can a new wp-build Trac environment please be created? No need to configure beyond giving me TRAC_ADMIN. (The associated SVN repository already exists, and I can handle changing the config, templates. etc.)


Can I please have the Virtual Ticket Permissions…

Can I please have the Virtual Ticket Permissions Trac plugin installed? I’ve already added it to deploy (see r4688), it just needs to be run (and whatever else needs to happen for a Trac plugin to be picked up, does it require an Apache restart?). I’ll be configuring it for themes.trac once it is installed.