I would like to make sites popular by using admin to say "yes" but when I run the "build pages", it reverts back to "no" because the hits are not high enough. Is there a way to override the "hits=" for some sites and keep the "hits=" valid for all others?
Jan 7, 1999, 3:31 PM
Administrator (9387 posts)
Jan 7, 1999, 3:31 PM
Post #2 of 4
Views: 436
Hi,
In nph-build.cgi, in sub build_update_newpop just comment out:
# Check to see if the record is popular...
#if ($values[$db_hits] >= $cutoff) {
#$output .= "\tUpdating record: $id, marking as popular ($values[$db_hits]).\n";
#$values[$db_ispop] = "Yes";
#}
#else {
#$values[$db_ispop] = "No";
#}
and then you should be fine. It won't overwrite your settings.
Hope this helps,
Alex
In nph-build.cgi, in sub build_update_newpop just comment out:
# Check to see if the record is popular...
#if ($values[$db_hits] >= $cutoff) {
#$output .= "\tUpdating record: $id, marking as popular ($values[$db_hits]).\n";
#$values[$db_ispop] = "Yes";
#}
#else {
#$values[$db_ispop] = "No";
#}
and then you should be fine. It won't overwrite your settings.
Hope this helps,
Alex
Jan 11, 1999, 1:26 PM
Novice (33 posts)
Jan 11, 1999, 1:26 PM
Post #4 of 4
Views: 436
Actually, stubbing out the else statement only is what I needed. I still want the check for popularity for those links that are over the required number. Thanks.
Found a different problem tho. I went into the Links Manager and lowered the hits on a couple links to put them below the popularity count and the manager showed they had changed. When I ran the build pages, the html pages kept the old counts. I checked this more than once. What is happening is that the Links.db is updating, but the url.db is not updating. This may need to be looked into.
John
Found a different problem tho. I went into the Links Manager and lowered the hits on a couple links to put them below the popularity count and the manager showed they had changed. When I ran the build pages, the html pages kept the old counts. I checked this more than once. What is happening is that the Links.db is updating, but the url.db is not updating. This may need to be looked into.
John

