Instead of cluttering up an already full thread, I figure it's best to start a fresh mess... Continuing from:
http://gossamer-threads.com/p/104671
I don't fully understand how values are being passed within the program (that should be obvious), but here are a couple of things I've noticed.
If I search my db for "mileage," I get two results in the Short display. Clicking directly on either one or using the prev/next links from within the Long display for either will successfully update the counter. These links would take the form of:
http://run-down.com/...records=View+Records
http://run-down.com/...ds&mh=1&nh=2
I have a feeling that's going to stretch off the screen...
It appears mh and nh are reset based on the number of results in the "query." The first link has maxhits set to 15, and there is no nh (next hit) option from the main results list. The second link is the long display (maxhits=1) and the second of 2 results (next hit=2). That much I understand.
One thing that confuses me is how that actually works? In sub html_record_long, the line that opens up the appropriate counter file is:
$count_up= "$counter_dir/$rec{$db_key}";
where $db_key = 'ID';
If there is no ID string on the search results links, how does it know the value? Does it go backtrack to find what ID corresponds to the search result query string? It obviously does work, I'm just curious why so as to better understand the part that doesn't work.
Which brings us to... the part that doesn't work! The following
http://run-down.com/...*&nh=14&mh=1
which is a Long record display after a List All query (record 14 in a single result display), does not update the couter. Other than the search field values, the only differences appear to be the presence of ID=* (which I would have thought the working examples would need in some manner to work) and view_records=1 vs. view_records=View+Records.
Still, I don't see how that's affecting whether or not the count is updated... Any ideas?
Thanks,
Dan
http://gossamer-threads.com/p/104671
I don't fully understand how values are being passed within the program (that should be obvious), but here are a couple of things I've noticed.
If I search my db for "mileage," I get two results in the Short display. Clicking directly on either one or using the prev/next links from within the Long display for either will successfully update the counter. These links would take the form of:
http://run-down.com/...records=View+Records
http://run-down.com/...ds&mh=1&nh=2
I have a feeling that's going to stretch off the screen...
It appears mh and nh are reset based on the number of results in the "query." The first link has maxhits set to 15, and there is no nh (next hit) option from the main results list. The second link is the long display (maxhits=1) and the second of 2 results (next hit=2). That much I understand.
One thing that confuses me is how that actually works? In sub html_record_long, the line that opens up the appropriate counter file is:
$count_up= "$counter_dir/$rec{$db_key}";
where $db_key = 'ID';
If there is no ID string on the search results links, how does it know the value? Does it go backtrack to find what ID corresponds to the search result query string? It obviously does work, I'm just curious why so as to better understand the part that doesn't work.
Which brings us to... the part that doesn't work! The following
http://run-down.com/...*&nh=14&mh=1
which is a Long record display after a List All query (record 14 in a single result display), does not update the couter. Other than the search field values, the only differences appear to be the presence of ID=* (which I would have thought the working examples would need in some manner to work) and view_records=1 vs. view_records=View+Records.
Still, I don't see how that's affecting whether or not the count is updated... Any ideas?
Thanks,
Dan