Modify ↓
Opened 7 years ago
Last modified 8 weeks ago
#12681 assigned defect
Restore the t.e.o specific customization after the switch to Jinja2
| Reported by: | Christian Boos | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | high | Milestone: | 1.6.1 |
| Component: | project | Version: | 1.3dev |
| Severity: | normal | Keywords: | jinja2 |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Attachments (0)
Change History (19)
comment:1 by , 7 years ago
follow-up: 3 comment:2 by , 7 years ago
Related to the 1.3.2dev upgrade, the SpamFilter admin pages are all giving errors.
comment:3 by , 7 years ago
Replying to Ryan J Ollos:
Related to the 1.3.2dev upgrade, the SpamFilter admin pages are all giving errors.
Right! It was still the spam-filter-trunk version, not the spam-filter-trunk-jinja one.
comment:4 by , 7 years ago
| Milestone: | → 1.3.2 |
|---|
Moving to milestone:1.3.2, as fixing this in a satisfying way will probably involve adding an overridable site.html template.
comment:5 by , 7 years ago
| Milestone: | 1.3.2 → 1.3.3 |
|---|
comment:6 by , 7 years ago
| Milestone: | 1.3.3 → 1.4 |
|---|
comment:10 by , 5 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
… and other pages, like 1.3/TracInterfaceCustomization.
Version 0, edited 5 years ago by (next)
comment:11 by , 5 years ago
| Milestone: | 1.4 → 1.4.1 |
|---|
comment:12 by , 5 years ago
Also need to review/update the email template: TracNotification#Customizingtheemailcontent.
comment:14 by , 4 years ago
| Milestone: | 1.4.1 → 1.4.2 |
|---|
comment:15 by , 4 years ago
| Milestone: | 1.4.2 → 1.4.3 |
|---|
comment:16 by , 3 years ago
| Milestone: | 1.4.3 → 1.4.4 |
|---|
comment:17 by , 3 years ago
| Milestone: | 1.4.4 → 1.4.5 |
|---|
comment:18 by , 7 months ago
| Milestone: | 1.4.5 → 1.6.1 |
|---|
Note:
See TracTickets
for help on using tickets.
Ok, it's more or less business as usual now… feel free to point out anything I could have left out.
However, I'm not satisfied with the current way of implementing this, as the content of site_header.html and site_footer.html are each incomplete HTML fragments. There must be a better way using a single site.html file.