pressing delete link in ticket comments ticks the wrong comment

[moo]

when there's a ticket comment deleted in the middle, say. 1 2 3 4, and 2 is deleted already (i guess) if i press "delete" on 3, it ticks the wrong comment in the admin page.

ticking the "change at *" also won't ticks the fields

[Ryan J Ollos]

I think this may be related to #6535. I'll take a look.

[Ryan J Ollos]

0.10 is no longer supported.

[Chris Nelson]

Replying to rjollos:

0.10 is no longer supported.

OK. But I still see this in 0.11.6 (using plugin version 2.0). Was there a similar ticket against 0.11? Is this fixed in 3.0?

[Ryan J Ollos]

Replying to ChrisNelson:

OK. But I still see this in 0.11.6 (using plugin version 2.0). Was there a similar ticket against 0.11? Is this fixed in 3.0?

I had thought the issue was fixed in [6924]. I haven't been able to reproduce. There were several revs of version 2.0, which is why I started tagging the egg builds with the SVN revision. Do you know what SVN revision you are currently running?

If you can test with 3.0dev and reproduce the issue, I'll get it fixed.

[Chris Nelson]

Replying to rjollos:

Replying to ChrisNelson:

OK. But I still see this in 0.11.6 (using plugin version 2.0). Was there a similar ticket against 0.11? Is this fixed in 3.0?

I had thought the issue was fixed in [6924].

That diff doesn't seem to relate to this issue. The problem is that Trac doesn't number at least attachments and maybe edits of the description and the deletion is invoked with "&cnum=n" but instead of looking for 'n' in the oldvalue field where comments are numbered, it looks for the nth group of ticket changes so unnumbered changes (like attachments) throw the delete plugin off.

I haven't been able to reproduce.

• Create a ticket
• Add a comment
• Edit the description
• Attach a file
• Add a comment
• Respond to one of the comments
• Delete one of the comments

So far, so good.

• Try to delete on of the other comments

The wrong one is checked on the delete preview. (It may matter which one you comment on and which one you delete first. I'll verify when I test this.)

There were several revs of version 2.0, which is why I started tagging the egg builds with the SVN revision. Do you know what SVN revision you are currently running?

No, sorry.

If you can test with 3.0dev and reproduce the issue, I'll get it fixed.

I'll try to do this today or tomorrow.

[Chris Nelson]

Downloaded the .zip from the plugin page and installed. It says it's "3.0.0dev". For me, this behaves worse than 2.0. I don't like the reverse chronological sort of changes. But apropos of this ticket, the wrong change is checked. Let me know if the sequence above isn't enough to reproduce it.

[Ryan J Ollos]

Replying to ChrisNelson:

Downloaded the .zip from the plugin page and installed. It says it's "3.0.0dev". For me, this behaves worse than 2.0. I don't like the reverse chronological sort of changes.

There were so pretty major changes in [11802], which dropped all of the JavaScript and implemented everything in Python via Genshi. This should have resolved several possible plugin conflicts, see comment:35:ticket:1749. However, I'm not surprised that there might be some behavior changes that I didn't notice when modifying and applying the patch.

I'm happy to fix any specific behavior change you don't like if you open a ticket for the issue.

But apropos of this ticket, the wrong change is checked. Let me know if the sequence above isn't enough to reproduce it.

I'll focus on fixing this issue first.

[Ryan J Ollos]

Replying to ChrisNelson:

It says it's "3.0.0dev". For me, this behaves worse than 2.0. I don't like the reverse chronological sort of changes.

Do you want the most recent change at the bottom of the page, or at the top of the page?

[Chris Nelson]

Replying to rjollos:

Replying to ChrisNelson:

It says it's "3.0.0dev". For me, this behaves worse than 2.0. I don't like the reverse chronological sort of changes.

Do you want the most recent change at the bottom of the page, or at the top of the page?

I want the most recent change at the bottom, same order as in the ticket. (Unless Trac 1.0 implemented a last at the top ordering or something, then it gets ugly.)

[Ryan J Ollos]

Replying to ChrisNelson:

I want the most recent change at the bottom, same order as in the ticket. (Unless Trac 1.0 implemented a last at the top ordering or something, then it gets ugly.)

In Trac 1.0 you can reverse the sorting with a radiobutton selection, but this plugin is not needed with Trac 0.12 and later, so it won't be an issue for us.

[Ryan J Ollos]

(In [12098]) Refs #840, #10263:

• Added check of Trac version. The plugin won't install in Trac 0.12 and later. In Trac 0.12 and later, enable the equivalent functionality by setting tracopt.ticket.deleter = enabled.
• When a "change" checkbox is selected, all of the child "field" checkboxes will be selected.
• Improved warning that is issued when an invalid ticket ID is entered. The left # characters in case the user enters #100 for a ticket ID, rather than 100.
• Fixed some regressions introduced in #840, when migrating from the javascript version of the plugin, to the genshi version.
  • Alert confirmation dialog has been restored.
  • Changes sort chronlogically.

Please test and report back, if you can.

[Ryan J Ollos]

Note that I haven't yet addressed the issue in comment:7.

[Ryan J Ollos]

(In [12099]) Refs #840, #10263: FIX: the reply buttons were redirecting to the delete page as well.

[Ryan J Ollos]

Most likely, nothing will happen with this ticket unless someone provides a patch. Following #10263, we have a version of TicketDeletePlugin that utilizes ITemplateStreamFilter to modify the Genshi template. Since Trac 0.12 supports ticket deletion, I have little motivation to do additional work on this plugin. I'd welcome a patch though!

[Ryan J Ollos]

Closing tickets for deprecated plugin.