Code

Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#10704 closed (fixed)

ifchanged-else documentation lost in r8506

Reported by: Tarken Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

With the reorganization of the docs in r8506, the addition for the {% else %} tag on {% ifchanged %} from r8095 was left out. Attached is a patch created against the 1.0.X branch, r10368. It does, however, apply cleanly to trunk as well.

This is simply a recreation of the doc portion of the patch provided with #4534.

Attachments (1)

ifchanged-else-docs.diff (738 bytes) - added by Tarken 5 years ago.

Download all attachments as: .zip

Change History (6)

Changed 5 years ago by Tarken

comment:1 Changed 5 years ago by Alex

  • milestone set to 1.1
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 5 years ago by Alex

  • Triage Stage changed from Accepted to Ready for checkin

comment:3 Changed 5 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(In [10563]) Fixed #10704 -- Resurrected documentation for {% else %} clause on {% ifchanged %}, lost during docs refactor. Thanks to Tarken for the report.

comment:4 Changed 5 years ago by russellm

(In [10569]) [1.0.X] Fixed #10704 -- Resurrected documentation for {% else %} clause on {% ifchanged %}, lost during docs refactor. Thanks to Tarken for the report.

Merge of r10563 from trunk.

comment:5 Changed 3 years ago by jacob

  • milestone 1.1 deleted

Milestone 1.1 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


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

 
Note: See TracTickets for help on using tickets.