Upgrade t-h.o to Trac 1.0

[Ryan J Ollos]

The following plugins needed to be upgraded, tested and possibly fixed to work with the upgraded version of Trac.

Plugin	Status
AccountManagerPlugin	✓
AcronymsPlugin	✓
AutoWikifyPlugin	✓ Version 0.2 has been tested with Trac 1.0dev
ChangeLogMacro	✓
EmailProcessorMacro	✓
FootNoteMacro	✓
IncludeMacro	✓
IniAdminPlugin	Replaced by TracIniAdminPanelPlugin
NewHackMacro	Replaced by NewHackPlugin
NewsFlashMacro
PollMacro	✓
RefMacro	Integrated into core with Trac 0.10, see ​t:TracLinks#Linkanchors
SpamFilterPlugin	✓
SvnAuthzAdminPlugin	Needs lots of work
TagsPlugin	✓
TicketChangePlugin	Integrated into core with Trac 0.12 (permission TICKET_EDIT_COMMENT)
TicketDeletePlugin	Integrated into core as option component with Trac 0.12 (tracopt.ticket.deleter)
TocMacro	✓
TracBlogPlugin	deprecated, use FullBlogPlugin
FullBlogPlugin	✓, even combined with FullBlogNotificationPlugin
TracHacksPlugin	✓
TracPygmentsPlugin	Integrated into core with Trac 0.11. Make sure to install Pygment 1.5
TracRedirect -> ServerSideRedirectPlugin	✓ Version 0.4 has been tested with Trac 1.0dev
WebAdminPlugin	Integrated into core with Trac 0.11
XmlRpcPlugin	✓
WikiReplacePlugin	Not currently used on t-h.o, but may be added.

[Ryan J Ollos]

Fixed-up the AutoWikifyPlugin. It should be good to go, but I'll add some unit tests this evening for good measure.

[Ryan J Ollos]

RefMacro is no longer needed.

[Ryan J Ollos]

Let's plan to replace all calls to TOC macro with [[PageOutline(2-5,Contents,pullout)]] unless:

1. Someone steps up with reasonable objections.
2. Someone steps up to maintain the macro.

Even better than (2), if someone wishes to step-up and maintain TocMacro, why not see if you can get those features pushed to the Trac core? In the future, we can certainly plan to upgrade t-h.o on the release cycle of Trac, so any features pushes to the Trac core will make their way to t-h.o before too long.

[Ryan J Ollos]

Pushed a patch for ServerSideRedirectPlugin this evening in [11890] and did some quick testing with Trac 1.0dev. Seems to be good to go.

[falkb]

What is the news? What are you doing at present?

[Ryan J Ollos]

Replying to falkb:

What is the news? What are you doing at present?

We should have some news in the near future. Everything seems to be moving towards an upgrade and server move, but the details must be working out in the coming days.

[falkb]

• PollMacro
• FullBlogPlugin + FullBlogNotificationPlugin

work for me with 1.0.

I just called python setup.py clean bdist_egg on the current SVN checkout and reloaded Trac with the new plugin egg files, used it for a while, checked the logging.

[falkb]

• IncludeMacro works as well with 1.0
• AcronymsPlugin works only if [acronym] page = AcronymDefinitions` is explicitly set in trac.ini, the default hasn't worked, although I'm not sure if this maybe is a general problem.

[anonymous]

Replying to falkb:

• AcronymsPlugin works only if [acronym] page = AcronymDefinitions is explicitely set in trac.ini

No, I think that was just a caching problem, fully works now after Browser restart and Apache reload. I tag it for 1.0, too.

[Steffen Hoffmann]

description update according to falkb's comments, added my own work on AccountManagerPlugin

[falkb]

Hi hasienda, You can also sign InitAdminPlugin since it works with 1.0 as well

[Steffen Hoffmann]

Replying to falkb:

Hi hasienda, You can also sign InitAdminPlugin since it works with 1.0 as well

You meant IniAdminPlugin, right? Done so now.

[falkb]

What is going on with the TH upgrade?

[Ryan J Ollos]

We all have one or more jobs each and also maintain several plugins. I don't see myself having time to commit to getting the upgrade off the ground until at least the second week of Feb.

[falkb]

Replying to rjollos:

... until at least the second week of Feb.

I'll try to get some more plugins from the list above tested until then

[Ryan J Ollos]

Thanks, that would be great. I'll be looking for when I have most of a weekend clear before embarking on the initial stage of the upgrade, which is to setup a Trac 1.0 version running on a different port, as Michael had done previously for the Trac 0.11 instance. I'll keep you posted as to when I think that might happen. I had hoped to find time over the holidays, but managed to consume myself with other coding tasks.

[falkb]

I'd go for the Bitnami version which is an all-in-one package and easy to install, and as second step replace its Trac sources with the SVN trunk of Trac. And I hope we get rid of that nasty "TimeoutError: Unable to get database connection within 20 seconds" that is getting worse over the last months.

[Ryan J Ollos]

#10939 closed as a duplicate, requesting a Back to Report or Back to Query link after navigating from a report/query to a ticket. I think we get that for free with the Trac 1.0 upgrade.

[Ryan J Ollos]

#10986 closed as a duplicate.

[Ryan J Ollos]

I'm dedicating the entire day of Sat April 6th to getting an instance of trac-hacks running Trac 1.0 on port 8080. Since we have several people offering to help test and fix plugin issues, I'll try to coordinate the effort so that we can get the site deployed asap after that.

[Dirk Stöcker]

Some macro notes:

• TocMacro works with 1.0, so replace is not required for update.
• IniAdminPlugin should be replaced by TracIniAdminPanelPlugin, it is much better (which is why I continue development now).
• SpamFilterPlugin is much better in the 1.0 version than in the 0.10 variant.

[Ryan J Ollos]

Replying to stoecker:

• TocMacro works with 1.0, so replace is not required for update.

True, replacing it is not required, but it seemed to be a good opportunity to get rid of the macro. Of course, we can get rid of it later on too, if it still works with Trac 1.0.

I'm open to keeping the TocMacro if it will be maintained, and someone can describe reasons we need to have it on trac-hacks. However, the last commit was in 2008 and I don't think anyone is giving it attention anymore.

[osimons]

I'm maintaining TocMacro in the sense that I use it in production and will fix serious bugs if found. However, it is definitely in maintenance-mode as I don't spend time adding features or fixing trivial bugs.

My main use for [[TOC]] is that it can build a combined TOC for any number of pages at the same time, typically used for plugins that split information into subpages. [[PageOutline]] macro will of course be a fine option for single-page input.

[Ryan J Ollos]

Replying to osimons:

My main use for [[TOC]] is that it can build a combined TOC for any number of pages at the same time, typically used for plugins that split information into subpages.

That sounds like a good enough use case to keep it around then. The AccountManagerPlugin has a few subpages, and might benefit from using TOC.

[anonymous]

Maybe providing a patch for core, so that this feature gets added as well?

[Ryan J Ollos]

Replying to anonymous:

Maybe providing a patch for core, so that this feature gets added as well?

I had similar thoughts, and I think that enhancing the PageOutline macro in the Trac core is a good idea. I have numerous other issues I'm working on in the Trac core though, so I'm unlikely to get to it soon. Hopefully someone else will :)

[Ryan J Ollos]

Replying to rjollos:

I'm dedicating the entire day of Sat April 6th to getting an instance of trac-hacks running Trac 1.0 on port 8080.

I made a little bit of progress over the weekend, but had some thing come up so didn't get as far as I'd hoped. I will try to make progress during the week. Stay tuned!

[Mitar]

Joining in a bit. I don't know how much time I can have for this but in general I am interested in how to make collaboration on the Internet better. So let's see what we can do here.

[falkb]

Replying to rjollos:

I made a little bit of progress over the weekend, but had some thing come up so didn't get as far as I'd hoped.

What is exactly meant with progress and which things came up? What is the news? :)

[Ryan J Ollos]

Life things came up, and the demands of people that pay my mortgage :)

I have a holiday coming up, so hope to keep that clear to work on the upgrade.

[Ryan J Ollos]

#11078 discusses a workaround for attachments that fail to display, and was closed as a duplicate of this ticket.

[falkb]

Wow! The new version is much faster and looks good :-)

[Dirk Stöcker]

Wow. Finally. Thanks.

After login I get that everywhere.

AttributeError: 'TracHacksHtPasswdStore' object has no attribute 'user_email_verification_requested'

P.S. If I can help with the spamfilter, please ask.

[Ryan J Ollos]

Replying to stoecker:

Wow. Finally. Thanks.

It hasn't come about the way I intended; I had hoped for a smoother process, but I made some mistakes and here we are. At least it's moving along, is my feeling at the end of a long day.

After login I get that everywhere.

AttributeError: 'TracHacksHtPasswdStore' object has no attribute 'user_email_verification_requested'

Thanks. Steffen is going to take a look at the AccountManagerPlugin configuration tomorrow. It was major upgrade, and I'm sure I don't have the configuration right yet.

P.S. If I can help with the spamfilter, please ask.

I grabbed a bunch of entries from the logs and one of them seemed related to the SpamFilter (comment:1:ticket:11149). It looked pretty minor, if even a problem at all. We are running 0.8.0dev-r11796 (latest from the 1.0 branch as of earlier today).

I'm sure I'll have lots of questions for you regarding the configuration of the SpamFilterPlugin soon.

[falkb]

Is it policy or a configuration issue that commenting a blog entry is not permitted, even logged in?

[osimons]

Replying to falkb:

Is it policy or a configuration issue that commenting a blog entry is not permitted, even logged in?

It is a new permission. Just haven't gotten around to adding it before now. Could you please check again and verify?

BTW, I have added it to authenticated users only. I see no particular good reason why we would want anonymous feedback to site issues.

[falkb]

Replying to osimons:

Could you please check again and verify?

Works well

BTW, I have added it to authenticated users only. I see no particular good reason why we would want anonymous feedback to site issues.

This would just result in spam. BTW: I'd suggest to protect it with reCAPTCHA even for authenticated users because a spam robot may simply create a TH user first.

[osimons]

I've also enabled the blog spamfilter support, so all comments should also go through the same verification process as ticket and wiki updates.

Let's hope it works - been a while since I've looked at that particular code. Perhaps stoecker can verify the current implementation? See source:fullblogplugin/0.11/tracfullblog/spamfilter.py​

[Ryan J Ollos]

One other small thing is that we seem to have lost the background with the trac-hacks wording. I'll worry about that when I stop spotting broken features and exceptions!

[osimons]

Replying to rjollos:

One other small thing is that we seem to have lost the background with the trac-hacks wording. I'll worry about that when I stop spotting broken features and exceptions!

Many small things we've lost here, but all is found in the old customization templates - see trac/templates/site_css.cs, site_footer.cs, site_header.cs and friends. I've started a site.html to get this going, and have so far converted site_newticket.cs and site_css.cs into new format. Particularly styles may need to be reviewed with all visual and layout changes since 0.10... At least it loads, so let's tweak it from here.

[osimons]

Replying to osimons:

Let's hope it works - been a while since I've looked at that particular code. Perhaps stoecker can verify the current implementation? See source:fullblogplugin/0.11/tracfullblog/spamfilter.py​

Huh. Should not blog comments appear under spam monitoring in admin?

[Dirk Stöcker]

Replying to osimons:

Replying to osimons:

Let's hope it works - been a while since I've looked at that particular code. Perhaps stoecker can verify the current implementation? See source:fullblogplugin/0.11/tracfullblog/spamfilter.py​

Huh. Should not blog comments appear under spam monitoring in admin?

Hmm, depends on the fact if authenticated users are auto-trusted or not. Default is to trust them fully. Code looks good on first inspection.

[Dirk Stöcker]

Replying to falkb:

BTW, I have added it to authenticated users only. I see no particular good reason why we would want anonymous feedback to site issues.

This would just result in spam. BTW: I'd suggest to protect it with reCAPTCHA even for authenticated users because a spam robot may simply create a TH user first.

With a fine trained filter there is no need for a standard captcha anymore. Captcha only appears if submissions have been detected as SPAM and users get a chance to override it. T.E.O. and my josm site have approx. !one spam entry each 2-5000 spam submissions. Usually hand-entered spam passing valid captchas or stuff which is human-mad crap, but not really spam. Both sites allow unregistered edits.

[Ryan J Ollos]

I moved the repository configuration from trac.ini to the database, and resynced the repository. The configuration is such that the SVN repository URL is now shown in the contextual navigation of the repository browser.

One odd thing is that the resync kept halting, showing no error. Here is the last bit of my shell session:

rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
6072 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
6213 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
6699 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
6762 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
6993 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
7529 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
10111 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
13267 revisions cached.
Done.
rjollos@hacks:~$ sudo /srv/trac-hacks.org/pve/bin/trac-admin /srv/trac-hacks.org/trac repository sync ""
Resyncing repository history for (default)...
13267 revisions cached.
Done.

In the logs, many entries like the following:

2013-06-07 02:04:10,772 Trac[cache] WARNING: Revision 13089 already cached: IntegrityError('duplicate key value violates unique constraint "revision_pk"\n',)
2013-06-07 02:04:13,460 Trac[cache] WARNING: Revision 13204 already cached: IntegrityError('duplicate key value violates unique constraint "revision_pk"\n',)
2013-06-07 02:04:14,328 Trac[cache] WARNING: Revision 13240 already cached: IntegrityError('duplicate key value violates unique constraint "revision_pk"\n',)
2013-06-07 02:04:14,640 Trac[cache] WARNING: Revision 13253 already cached: IntegrityError('duplicate key value violates unique constraint "revision_pk"\n',)

[Ryan J Ollos]

The hacks are back on WikiStart now, and the styling looks quite a bit better. I haven't looked closely at the code, but I imagine it is due to a combination of the Trac 1.0 theme and the work of otaku42 on the TracHacksPlugin.

[Steffen Hoffmann]

Replying to rjollos:

The hacks are back on WikiStart now, and the styling looks quite a bit better. I haven't looked closely at the code, but I imagine it is due to a combination of the Trac 1.0 theme and the work of otaku42 on the TracHacksPlugin.

Great. OTOH, this slows down the front-page to previous lag-times.

This will finally drive me to look at TracHacksPlugin code. Best possible outcome would be a sub-optimal use of TagsPlugin, so that I could redirect calls towards a faster method for retrieving tagged (wiki) resources too. Using a cached list would be another strong option IMHO. We should really push computing effort and resulting response times towards what we had with the listing disabled, and I'm sure, this is possible.

[falkb]

Replying to rjollos:

The hacks are back on WikiStart now, and the styling looks quite a bit better. I haven't looked closely at the code, but I imagine it is due to a combination of the Trac 1.0 theme and the work of otaku42 on the TracHacksPlugin.

Currently, I don't see that table of hacks (both cases, logged in and out). Just "Show hacks for releases:" with an "Update" button appears but nothing happens when I click it.

[Ryan J Ollos]

Replying to falkb:

Currently, I don't see that table of hacks (both cases, logged in and out). Just "Show hacks for releases:" with an "Update" button appears but nothing happens when I click it.

I hadn't granted TAGS_VIEW. Sorry about that. You should see it now.

[falkb]

Wow! Even the main menu item "Tags" suddenly appeared. Thanks.

[falkb]

The tag cloud doesn't contain plugin names. Correct or not?

[falkb]

Now the main menu offers "Wiki", "Timeline", "Browse Source", "View Tickets", "New Ticket", "Search", "Tags", "Blog". Everything on board now or do we still miss some other VIEW permissions?

"Roadmap" for instance is not shown, maybe it's a good idea to create milestones there for tickets regarding to the improvements of trac-hacks.org itself or related tickets (e.g. TracHacksPlugin). This would likely increase the transparency of the TH project.

[Steffen Hoffmann]

Replying to falkb:

The tag cloud doesn't contain plugin names. Correct or not?

How could that be? Hack names are Components here (that cannot be tagged directly by now - pending enhancement), and tags named after plugins are possible but not planned as a general rule yet. Tagging if wiki pages will have to be converted from TagIt macro (old way).

[Steffen Hoffmann]

Replying to falkb:

Now the main menu offers "Wiki", "Timeline", "Browse Source", "View Tickets", "New Ticket", "Search", "Tags", "Blog". Everything on board now or do we still miss some other VIEW permissions?

Looks ok, so far. Probably we'll want to hide the /newticket direct link in favor of the per-hack default link in each hack's wiki page, or at least change the link to /newticket?component=TracHacksPlugin as a sensible default for issues not coming from specific plugins.

"Roadmap" for instance is not shown, maybe it's a good idea to create milestones there for tickets regarding to the improvements of trac-hacks.org itself or related tickets (e.g. TracHacksPlugin). This would likely increase the transparency of the TH project.

Doing it just because it could be done is not a hot idea. We have missed something like the roadmap to triage tickets for some plugins, sure. But we've not decided on how to approach it now. I.e. we can't do it without a having real per-hack-milestones and a per-hack-milestone admin interface. Let's go further on that road only after carefully examining the real benefit and after having prepared the required infrastructure.

Please note, that progress bars are no longer tied to the roadmap, and could be embedded in every text-area supporting WikiFormatting:

[[TicketQuery(component=TracHacksPlugin,format=progress)]]

renders as

79%

Total number of tickets: 53 - closed: 42 - active: 11

Many possibilities with Trac 1.0, you see?

[Ryan J Ollos]

Replying to hasienda:

Hack names are Components here (that cannot be tagged directly by now - pending enhancement),

Did you have in mind the ability to add tags to Components, or to use the component table as a tag provider with the name column providing the tags? The latter would be somewhat similar to the [tags] ticket_fields option, except that the component table would be the direct source of tags rather than the component field of each ticket.

[anonymous]

Replying to hasienda:

Replying to falkb:

The tag cloud doesn't contain plugin names. Correct or not?

How could that be? Hack names are Components here (that cannot be tagged directly by now - pending enhancement), and tags named after plugins are possible but not planned as a general rule yet. Tagging if wiki pages will have to be converted from TagIt macro (old way).

Sorry, I was not clear enough. I just remembered, with the old Trac version, I've seen e.g. TracJsGanttPlugin with a certain font size on the tag cloud page, but now it's vanished there. I just thought it might be due a permission problem.

[Ryan J Ollos]

Replying to hasienda:

Please note, that progress bars are no longer tied to the roadmap, and could be embedded in every text-area supporting WikiFormatting:

[[TicketQuery(component=TracHacksPlugin,format=progress)]]

renders as

79%

Total number of tickets: 53 - closed: 42 - active: 11

That might be a good modification to make to the NewHack template.

How does this look?: BookmarkPlugin#BugsFeatureRequests. The change makes the link to all tickets, including closed ticket, immediately available to the user, so hopefully more users will take advantage of this to read closed tickets as well before opening a new ticket. As part of the change in #10510, I'll make report {10} group tickets by status, though we might be better off using a custom query rather than a report so that a user can easily do further filtering.

[Ryan J Ollos]

Replying to anonymous:

Sorry, I was not clear enough. I just remembered, with the old Trac version, I've seen e.g. TracJsGanttPlugin with a certain font size on the tag cloud page, but now it's vanished there. I just thought it might be due a permission problem.

I'm not sure what would cause it to appear on the tag cloud page. The first guess I had was that some tickets had TracJsGanttPlugin as a keyword, but a query yields no results.

[Ryan J Ollos]

Replying to rjollos:

I hadn't granted TAGS_VIEW. Sorry about that. You should see it now.

Note that I also granted TAGS_MODIFY at that time.

[Ryan J Ollos]

Replying to stoecker:

After login I get that everywhere.

AttributeError: 'TracHacksHtPasswdStore' object has no attribute 'user_email_verification_requested'

I think we've fixed this now in #11154, but please let me know if you find that's not the case.

[Steffen Hoffmann]

Replying to rjollos:

That might be a good modification to make to the NewHack template.

How does this look?

+1, looks great, provides intuitive links to resolved as well as open issues, and an overall impression on plugin status even before looking at a ticket listings.

Minor nit-pick: For some plugin's I'd like to have a miniature representation to be able to show a bundle of progress bars - on bar per ticket type. When there are 10 issues, it matters if 8 of them are bugs ore enhancement requests.

[Ryan J Ollos]

Replying to hasienda:

Minor nit-pick: For some plugin's I'd like to have a miniature representation to be able to show a bundle of progress bars - on bar per ticket type. When there are 10 issues, it matters if 8 of them are bugs ore enhancement requests.

It might be possible to even show all the different ticket types in one bar (probably an enhancement to Trac is needed), similar to TracIni#milestone-groups-section, and have closed / defects / enhancements / tasks as colored segments of the bar and query links below the bar. That would provide all the information I need, because like you I care to see how many open defects vs enhancements vs tasks there are, but I don't really need to see the closed tickets categorized by ticket type.

Your edits to AccountManagerPlugin#BugsFeatureRequests look good though. The bars are only lacking a title, which is another possible enhancement to the TicketQuery macro, though we can probably just add it through wiki markup, or even WikiHtml if we want it to look really nice (e.g. adjust the font and font size) (see also #11045).

[Steffen Hoffmann]

Replying to rjollos:

It might be possible to even show all the different ticket types in one bar (probably an enhancement to Trac is needed), similar to TracIni#milestone-groups-section, and have closed / defects / enhancements / tasks as colored segments of the bar and query links below the bar. That would provide all the information I need, because like you I care to see how many open defects vs enhancements vs tasks there are, but I don't really need to see the closed tickets categorized by ticket type.

Agreed, feeling the same. It will definitely need an enhancement to get ticket grouped by status and - at the same time - open tickets by type. Because there are so many possible use-cases, that having closes/defects/enhancements/tasks would be not enough. I know of some instances with more than 20 ticket types.

IMHO it would be valuable to just switch the criterion for grouping from ticket status to type and have two bars: an overall status + open ones grouped by type. An have a scaling attribute for miniature progress bar image, probably auto-popup-n-grow to 100% onMouseOver and go back to miniature when the pointer is dragged away from the image?

[falkb]

Still something deep in my mind warns me the progress thingy is a bit odd here. For a while I was thinking why and I think I detected the reason now: It's the percent number. That makes it more look like you're aiming a certain date (on a roadmap), but it is not. What you want to display is just a coloured ticket type overview chart not chained to an aim. Maybe this is a bit captious but I bet some users will accociate it with the state until the next plugin version... probably it helps to mask out the percent value.

[Ryan J Ollos]

Replying to stoecker:

P.S. If I can help with the spamfilter, please ask.

I would like to take you up on this offer as much as possible. I'll contact you by email.

[Ryan J Ollos]

In 13283:

Refs #10193: Update links in ThemeEnginePluugin README for Trac 1.0 raw attachment link format.

[falkb]

Uhmm... I can't vote tickets and wiki anymore (?).

[Ryan J Ollos]

Replying to falkb:

Uhmm... I can't vote tickets and wiki anymore (?).

Removed to avoid an error that resulted in a traceback. Maybe one of the errors documented in #11149, but I don't remember. It will be reinstalled once we have sorted out what the problem is.

Installation of VotePlugin is being tracked in #8717.

[anonymous]

stoecker has pointed out that TracIniAdminPanelPlugin needs to be reinstalled because i18n translations aren't enabled.

[Steffen Hoffmann]

Replying to anonymous:

stoecker has pointed out that TracIniAdminPanelPlugin needs to be reinstalled because i18n translations aren't enabled.

Right, but this is true for every plugin packaged in the virtual environment before we installed Babel. I noticed this for AcctMgr and TagsPlugin too, but no need to hurry from my point of view. It will come with next update automatically, and I hope to roll a lot of improvements in due time.

[Steffen Hoffmann]

Been bitten by ​genshi:ticket:566 same way as mentioned in ​t:#11184 - another Genshi issue for the 0.7 release.

I wonder, if we should roll-back to 0.6 for a while, because I can't see much pushing to get Genshi issues fixed in a timely manner, and I cannot do it myself. Another option would be to maintain a version with published patches meanwhile, what might actually encourage fixing it upstream a bit more. Thoughts?

[falkb]

Realizing blog and news ticker at wiki start page is not sync'ed I wonder if it's a good idea to use

{{{
#!div class=blogflash
[[BlogList(recent=2, heading=News)]]
}}}

[Steffen Hoffmann]

Replying to falkb:

Realizing blog and news ticker at wiki start page is not sync'ed

This is on purpose. We use tagging to mark blog posts for WikiStart, and I decided to not add the German developer meeting post, but announce it at out mailing-list instead.

[Jun Omae]

Hi, it seems NewHack page currently doesn't work. I have a new hack....

[Ryan J Ollos]

I've been feeling a bit guilty about not getting that working yet. The TracHacksPlugin seems to need a bit of work still. I'll take a look tomorrow and try to figure out what needs to be done still, and report back.

[Ryan J Ollos]

I've installed the ServerSideRedirectPlugin as a replacement for TracRedirect. The latter hadn't been reinstalled after the upgrade, so pages such as GoogleAnalyticsPlugin and AccountManager weren't redirecting.

Sorry the progress on the upgrade is moving so slow lately. I'll try to find time this week to finish up the major issues.

[Ryan J Ollos]

After ​this mailing list post, I searched for ?format=raw strings and made the following changes to each URL to fix the links:

• removed ?format=raw
• replaced attachment with raw-attachment

Please fix or let me know if you spot any I missed.

[Matthew Carlson]

I also have a new hack, but the NewHack page doesn't work, presumably related to the NewHackMacro not being checked off in this ticket. I'm not in any hurry to upload, but thought I'd share a small LDAP Sync plugin I wrote to fill a gap between SSPI authentication and email notifications.

[Ryan J Ollos]

Sorry for the continued delay on resurrecting the New Hack form. I will try to find some time to work on it this coming weekend.

If anyone is interested in contributing to that effort, the TracHacksPlugin provides the New Hack form now, and if I remember correctly there are some major issues that will quickly be discovered once you start testing. The NewHackMacro is deprecated.

[Ryan J Ollos]

Minor issue: The ListTagged macro is displaying No resources found. See wiki:experimentalut? for an example. We probably want to suppress this on user pages.

[falkb]

Hi! I cannot attach files to TH tickets anymore. Look at #11289 where I reported the internal TH server error.

[falkb]

Replying to falkb:

Hi! I cannot attach files to TH tickets anymore. Look at #11289 where I reported the internal TH server error.

yes, rjollos is right, changing the language to "English (US)" is a workaround (tracked at ​t:#11184, already)

[falkb]

Hi! I noticed that CC adding uses my email address for the CC field but I don't want that, even not with a cut address string. falkb should be used. Please, could you make it that way again?

[Mitar]

This plugin can be used for that.

[Jun Omae]

I created patch, trachacksplugin-t10193-r13419.diff​.

• New Hack works well.
• Shows the hint for focused input.
• Clicking tag in cloud adds or removes the tag.
• Uses /usr/bin/svn instead of /usr/bin/op command cause the command is missing in my environment.
• Need to replace download:${LCNAME} with export:${LCNAME} in NewHackTemplate.

The patch needs more testing. Could somebody please try it?

[Jun Omae]

Any progress?

[Ryan J Ollos]

Sorry for the delay. I will try to make time to test it out by the weekend. Thanks for providing the patch!

[Ryan J Ollos]

Replying to jun66j5:

I created patch, trachacksplugin-t10193-r13419.diff​.

• New Hack works well.
• Shows the hint for focused input.
• Clicking tag in cloud adds or removes the tag.
• Uses /usr/bin/svn instead of /usr/bin/op command cause the command is missing in my environment.

It is working much better. I added a few more changes, and the latest can be found in ​t10193. There are a few things I noticed that I haven't fixed yet:

• After filling out all the fields, the Create Hack button is still disabled, until the user does a Preview. Maybe this was intended, but it could be confusing, so we should probably at least have some sort of hint. Similarly, when the form doesn't submit due to failing a validation condition we should provide hints, but that can be done later.
• Nothing is done with the Installation Instructions that are entered. They aren't inserted into the template.

• Need to replace download:${LCNAME} with export:${LCNAME} in NewHackTemplate.

Done in this change.

[Jun Omae]

• After filling out all the fields, the Create Hack button is still disabled, until the user does a Preview. Maybe this was intended, but it could be confusing, so we should probably at least have some sort of hint. Similarly, when the form doesn't submit due to failing a validation condition we should provide hints, but that can be done later.
• Nothing is done with the Installation Instructions that are entered. They aren't inserted into the template.

I fixed these things and some issues, see ​https://github.com/jun66j5/trachacksplugin/commits/t10193.

[Ryan J Ollos]

Thanks. I'm testing it out and will try to get it installed by tomorrow if no other issues are found.

[Ryan J Ollos]

In 13483:

Fixes for New Hack form and display of tooltips. Patch by Jun Omae. Refs #10193.

• Avoid error when no types are defined.
• Normalize indentation in CSS file to 1 character.
• The stylesheet wiki.css is needed for rendering the preview.
• Open links to types and release in new tabs so that the user doesn't inadvertently navigate away from the page.
• Don't hide hints even if browser's window is narrow.
• Use box-sizing: border-box in order to be width: 100% for text fields in the form.
• Added a mergin of between newhack form and footer.
• Enable Create Hack button if all required inputs are filled.
• Show hints when focusing input and entering container because don't show hints for checkbox and radio button.
• Added --config-dir option for svn mkdir and retreives the configuration file from TRACHACKS_SVN_CONFIG_DIR environment
• Prevent directory traversal attack using hack name, e.g. NewHack/../../../../../etc/passwd.
• Added checks for existence of [trac] authz_file configuration option.
• Fixed unbound variable umask.

[Ryan J Ollos]

I've installed the r13483 of the plugin and I'm testing it out. I'll make some comments in #11436 about the issue encountered.

[Michael Renzmann]

In 13510:

Captured content from www/htdocs/site directory. Refs #10193.

[Ryan J Ollos]

With [13510], we should be able to restore the styling to the site. I'm hoping the site styling can be packaged with the TracHacksPlugin, since that would make it easier to maintain.

There is also a snippet in site.html that osimons added right after the 1.0 version of trac-hacks went live:

<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:py="http://genshi.edgewall.org/"
      py:strip="">

<!--! Add site-specific style sheet -->
<head py:match="head" py:attrs="select('@*')">
  ${select('*|comment()|text()')}
  <link rel="stylesheet" type="text/css"
        href="${href.chrome('site/style.css')}" />
</head>

<!--! Word of warning for creating new tickets -->
<form py:match="div[@id='content' and @class='ticket']/form[@id='propertyform']" py:attrs="select('@*')">
  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
    <div id="newticketguide">
      <h1>Stop!</h1>
      <hr />
      <p>Be sure to set the <strong>component</strong> of your ticket to the name of
         the hack you have a grievance with. Most hack pages will have a link
         specifically for creating new tickets against them. Use it.
      </p>
      <p>If you do not do this it is highly likely that the hack author <strong>will not be
        aware of your ticket and it will be ignored</strong>.</p>
      <hr />
      <p>Support and <a href="http://trac.edgewall.org/wiki/TracPlugins">installation</a> questions
         should be asked on the <a href="http://trac.edgewall.org/wiki/MailingList">mailing
         list</a> or <a href="http://trac.edgewall.org/wiki/IrcChannel">IRC channel</a>,
         not filed as tickets.
      </p>
    </div>
  </py:if>
  ${select('*')}
</form>

</html>

[Ryan J Ollos]

Pygments has been updated today from 1.3.1 to the latest (1.6), which fixes some minor issues I've noticed around the site.

[Ryan J Ollos]

Replying to mitar:

This plugin can be used for that.

Thanks. I'll look into whether that is suitable for integration to Trac.

[Ryan J Ollos]

#11949 has been created to tackle remaining issues with the upgrade. Please add anything I may have missed to that ticket. See also #11678.

[Ryan J Ollos]

Replying to rjollos:

• Need to replace download:${LCNAME} with export:${LCNAME} in NewHackTemplate.

Done in this change.

Did a site-wide replacement of download: with export: today and removed the download TracLink in InterMapTxt@25. The general procedure is described in ​trac:comment:7:ticket:12240, along with:

find wiki-dump/ -type f -exec sed -i "s/\[download:/\[export:/g" {} \;

[Ryan J Ollos]

Additional global search and replace operations will be recorded in #11949.