Custom Query (298 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 298)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#22 fixed No validation of input geodata Dominic Hargreaves IVORW@…
Description

Sun Oct 23 11:14:08 2005 IVORW - Ticket created [Reply] [Comment]

Subject: No validation of input metadata

OpenGuides allows anything to be passed in as Lat and Long. They are not checked or parsed for being valid numbers. Similarly for the website address - this is not checked and could result in invalid XML for another system trying to read RDF feeds.

Download (untitled) 248b

#23 fixed Ignore null changes tgj Dominic Hargreaves
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.

#24 fixed Search results should exclude #REDIRECT pages Earle Martin IVORW@…
Description

Mon Oct 24 02:28:52 2005 IVORW - Ticket created [Reply] [Comment]

Subject: Search results should exclude #REDIRECT pages

Andrew Black raised this on the London mailing list:

http://openguides.org/mail/openguides-london/2005-October/000464.html

I don't know how easy it would be to filter the output from SuperSearch? - do we need to tag the pages in the database somehow? Alternatively, we could exclude/remove #REDIRECT pages from the index on the input side.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.