I don't know how I missed this for so long... possibly because I don't do a lot of modification of links.

But, when a link is moved from the Validate to the Links database, the values for Hits, Ratings, etc stored in the Validate record (on the date it was moved there) are used.

That means, if it takes you a week or two to make any modification changes, the record you move back to the Links database will be missing the "hits" data.

The only way around this that I can think of, is to add a check box to the "dynamic" fields, such as Hits, Ratings, Votes, etc, and only update those fields if they are checked, otherwise, use the "current" values.

http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/

I simply use hidden form fields in the modify template files.

Regards,

Eliot Lee

That won't get around it.

A link that is "modified" goes to the Validate database.

The data that is stored in the Validate database "ages" out of sync with the Links database.

When the link is finally "approved" or re-validated, the data is "aged" compared to the data in the Links database.

http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/

Actually, I use the UPDATE function in MySQL to automatically update the record in the Links table without passing the record to the Validate table. This has caused minor problems in terms of people trying to modify their links automatically to top-level categories, but I am working on a method that excludes top-level categories when submitting/modifying sites. I have set up a flag variable in the Links.pm that controls whether to automatically update the record in the Links table or send to the Validate table. Then I set-up some conditions in the modify.cgi that either adds the record into the Validate table or updates the record in the Links table.

I don't quite follow you here...do you mean the Hits, Votes, Rating, etc.

I do see what you mean, I think...that what would be nice is that data from the Links table is used for fields like Hits, Rating, etc. rather being overwritten by the Validate table values, right? Okay...that does seem to be a bit buggy...but again, I found a workaround that does keep the records "in-sync", with minimal problems...

Regards,

Eliot Lee