Edgewall Software
Modify

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#8835 closed defect (invalid)

Ticket buttons no longer operational after change in site.html

Reported by: hju@… Owned by:
Priority: normal Milestone:
Component: rendering Version: 0.11-stable
Severity: normal Keywords: tickets, templates, customize
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

To enhance usability I added navigation links to tickets just below the Change History.

After following #8135 an related links I inserted this in site.html

  <!-- Copy from theme.html with new id -->
  <py:if test="context and context.resource.realm == 'ticket' and context.resource.id">
    <py:match path="//form[@id='propertyform']" once="true">
      <div py:attrs="select('@*')">
        <div id="ctxtnav3" class="nav">
          <h2>Context Navigation</h2>
            <ul py:if="chrome.ctxtnav">
              <li py:for="i, elm in enumerate(chrome.ctxtnav)"
                  class="${classes(first_last(i, chrome.ctxtnav))}">$elm</li>
            </ul>
          <hr />
        </div>
        ${select('*|text()')}
      </div>
    </py:match>
  </py:if>

The enhancement works fine, but the buttons (preview / Submit changes) are no longer operational. (The new links are operational!)

The log (in DEBUG mode) shows nothing special for me. I observed that the actions are not well formatted (see attachments) which led me to the point it might be an error.

Sorry if I didn't do well in changing site.html - it's my first try.

Attachments (3)

additional_navigation.jpg (16.7 KB ) - added by hju@… 14 years ago.
not_well_formatted_actions.jpg (42.4 KB ) - added by hju@… 14 years ago.
correct_formatted_actions.jpg (36.6 KB ) - added by hju@… 14 years ago.

Download all attachments as: .zip

Change History (5)

by hju@…, 14 years ago

Attachment: additional_navigation.jpg added

by hju@…, 14 years ago

by hju@…, 14 years ago

comment:1 by Remy Blank, 14 years ago

Resolution: invalid
Status: newclosed

The first thing that comes to mind is that you replace a <form> with a <div> in your <py:match> above. That obviously won't work.

Please ask SupportQuestions on the mailing list and/or IrcChannel.

comment:2 by hju@…, 14 years ago

Thx for your hint. Thats it! Correcting this results in a well running enhancement.

Sorry, didn't want to bother you.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.