Updating Ticket fails in 4.2.0 using IE9

We’ve been slowly moving from an outdated ticket system to Request Tracker, and were pleased that it worked just fine in IE, Chrome, and Firefox. We’ve updated RT to 4.2.0 just recently and noticed that when trying to update a ticket, it no longer works in IE. Clicking the “Update Ticket” button only reloads the page. We’ve also seen this odd behavior on the search page, clicking “Add these terms and Search” simply reloads the page (However does add the terms to the current search, it just won’t switch to the results page).

I tried changing the theme from the new ‘rudder’ to both ‘aileron’ and ‘ballard’ to see if it was a theme problem, but to no avail.
These problems don’t appear in Firefox or Chrome, but we have seen them in both IE9 and IE10 on Windows 7. Has anyone else seen this? Does anyone have any fixes?

Thanks!

We’ve been slowly moving from an outdated ticket system to Request
Tracker, and were pleased that it worked just fine in IE, Chrome, and
Firefox. We’ve updated RT to 4.2.0 just recently and noticed that when
trying to update a ticket, it no longer works in IE. Clicking the
“Update Ticket” button only reloads the page. We’ve also seen this odd
behavior on the search page, clicking “Add these terms and Search”
simply reloads the page (However does add the terms to the current
search, it just won’t switch to the results page).

Try the attached patch, which will be in 4.2.1.

  • Alex

0001-Insert-hidden-name-value-input-after-button-not-insi.patch (1.48 KB)

We’ve been slowly moving from an outdated ticket system to Request
Tracker, and were pleased that it worked just fine in IE, Chrome, and
Firefox. We’ve updated RT to 4.2.0 just recently and noticed that when
trying to update a ticket, it no longer works in IE. Clicking the
“Update Ticket” button only reloads the page. We’ve also seen this odd
behavior on the search page, clicking “Add these terms and Search”
simply reloads the page (However does add the terms to the current
search, it just won’t switch to the results page).

Try the attached patch, which will be in 4.2.1.

  • Alex

That fixes it! Thank you very much!

-Sweet