Ticket #23 (new defect)
Ignore null changes
| Reported by: | dom | Owned by: | Nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | openguides | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Mon Oct 17 03:20:56 2005 IVORW - Ticket created [Reply] [Comment]
Subject: Ignore null changes
Currently, OpenGuides will faithfully create a new version of a page if you ask it to, even when the contents and metadata are identical.
If both content and metadata are identical to the previous version, don't save the change or up the version number. The existing redirect logic will take the user back to the page - unaltered.
The present situation leads to RecentChanges getting polluted, both with automatic robot requests, and newbie edits.
Download (untitled) 449b
Fri Nov 11 07:33:03 2005 guest - Correspondence added [Reply] [Comment]
[IVORW - Mon Oct 17 03:20:56 2005]:
If both content and metadata are identical to the previous version, don't save the change or up the version number. The existing redirect logic will take the user back to the page - unaltered.
We already have a checksum mechanism, this would seem to be a bug in that it is not being called.
Download (untitled) 340b
Mon Nov 14 19:47:35 2005 6bed-rgew@… - Comments added [Reply] [Comment]
Date: Tue, 15 Nov 2005 00:54:02 +0000 From: 6bed-rgew@… To: comment-OpenGuides@… Subject: Re: [cpan #15092] Ignore null changes RT-Send-Cc:
Guest via RT wrote:
[IVORW - Mon Oct 17 03:20:56 2005]:
If both content and metadata are identical to the previous version, don't save the change or up the version number. The existing redirect logic will take the user back to the page - unaltered.
We already have a checksum mechanism, this would seem to be a bug in that it is not being called.
I think the problem could be that the checksum is including certain irrelevant metadata fields in the data, such as contributor/IP address, minor change, etc. Don't have time to verify this, but it's a thought.
