Edgewall Software

Ticket #80 (closed defect: fixed)

Opened 8 years ago

Last modified 2 years ago

<xi:fallback> content always shown

Reported by: cboos Owned by: cmlenz
Priority: major Milestone: 0.4
Component: Template processing Version: devel
Keywords: xi:include xi:fallback Cc:

Description

With latest trunk (r462), I've noticed that the <xi:fallback> content is always shown, regardless of whether the <xi:include> target was found or not.

This is visible e.g. in Trac's report template.

Attachments

unit_test_xi_fallback-r462.diff Download (1.8 KB) - added by cboos 8 years ago.
Unit-test demonstrating the issue
fix_xi_fallback-r462.diff Download (1.4 KB) - added by cboos 8 years ago.
Potential fix for the issue
fix_xi_fallback-r462.2.diff Download (1.3 KB) - added by cboos 8 years ago.
Simplified a bit the previous fix

Change History

Changed 8 years ago by cboos

Unit-test demonstrating the issue

Changed 8 years ago by cboos

Potential fix for the issue

Changed 8 years ago by cboos

  • keywords changed from xi:include xi:fallback to xi:include xi:fallback

With attachment:fix_xi_fallback-r462.diff Download, the problem is solved, i.e. the first unit test added in attachment:unit_test_xi_fallback-r462.diff Download now succeeds and my original issue with Trac's Report template is also fixed. All the other unit-tests still pass.

Changed 8 years ago by cboos

Simplified a bit the previous fix

Changed 8 years ago by cboos

  • version changed from 0.3.3 to devel

Changed 8 years ago by cmlenz

  • status changed from new to assigned

Thanks for the patches!

Changed 8 years ago by cmlenz

  • status changed from assigned to closed
  • resolution set to fixed

Should be fixed in [463]. I expanded your patch a bit so that we can now support nested fallback content.

Add/Change #80 (<xi:fallback> content always shown)

Author


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


Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.