I'm not sure if anyone else has this problem --- such as letting a bunch of records stack up you don't know what to do with, (Links needs a category '0' that is ignored by the build routine, but links pending action can be stuffed into it).
It also needs a way to page through the Validate screens.
Anyway, one very simple way to get to the newest records is to change the order in which the records are displayed. The autoincrement field (ID) comes to the rescue.
In Admin.html, in the: sub html_validate_form
Make the following change to the $to_validate parameter:
$to_validate = $val->query ( { mh => 10, so => 'DESC', sb => 'ID', Mode => 'Validate' } );
so => 'DESC' means to show the records in reverse order, and
sb => 'ID' is to use that field to order by.
The newest inserted records will be displayed first, so you can get to them.
It's not elegant, it's not pretty, but it works until a more global navigational solution is made.
It's also only 1 edit that doesn't actually change the program.
It also needs a way to page through the Validate screens.
Anyway, one very simple way to get to the newest records is to change the order in which the records are displayed. The autoincrement field (ID) comes to the rescue.
In Admin.html, in the: sub html_validate_form
Make the following change to the $to_validate parameter:
$to_validate = $val->query ( { mh => 10, so => 'DESC', sb => 'ID', Mode => 'Validate' } );
so => 'DESC' means to show the records in reverse order, and
sb => 'ID' is to use that field to order by.
The newest inserted records will be displayed first, so you can get to them.
It's not elegant, it's not pretty, but it works until a more global navigational solution is made.
It's also only 1 edit that doesn't actually change the program.
