Modify

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#12991 closed enhancement (fixed)

Adapt to Trac 1.0 database API

Reported by: Ryan J Ollos Owned by: Ryan J Ollos
Priority: normal Component: ComponentHierarchyPlugin
Severity: normal Keywords:
Cc: falkb Trac Release:

Description

The plugin will need to be made compatible with the Trac 1.0 database API to be compatible with 1.3.1 or later, possibly to be compatible with Trac 1.2 or later. I haven't tested yet with Trac 1.2.

Attachments (0)

Change History (6)

comment:1 Changed 5 years ago by Ryan J Ollos

Owner: changed from falkb to Ryan J Ollos
Status: newaccepted

comment:2 Changed 5 years ago by Ryan J Ollos

In 16130:

Branch for Trac 1.2

Refs #12991.

comment:3 Changed 5 years ago by Ryan J Ollos

Let me know if you find any issues with the changes. I branches for Trac 1.2 support because there were so many changes that it looked to be difficult to support back to Trac 0.12 in a single codebranch.

comment:4 Changed 5 years ago by Ryan J Ollos

Resolution: fixed
Status: acceptedclosed

In 16131:

1.2.0dev: Make compatible with Trac 1.2

  • Use Trac 1.0 database API
  • Adapt to change in id of form element on Manage Components page.
  • Move ComponentHierarchyEnvironmentSetupParticipant to model.py
  • Use html from trac.util.html, which indirectly imports tag from genshi.builder (for forward compatibility with future Jinja2 changes)
  • Drop support for IE < 8

Fixes #12991.

comment:5 Changed 5 years ago by Ryan J Ollos

Cc: falkb added

comment:6 Changed 4 years ago by Ryan J Ollos

In 16968:

TracComponentHierarchy 1.2.0dev: Rename plugin in preparation for publishing to PyPI

Uninstall the old plugin before installing this version:

pip uninstall ComponentHierarchy
pip install TracComponentHierarchy

Refs #12991.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.