This isn't really a problem, but I was surprised when I encountered it and was wondering if it's intentional.
If you modify links through the admin area, but don't actually make changes (i.e. select one or more links and check them off to modify), then you get an error that the record cannot be found in the database.
When I first noticed this, it was just after setting up a priority field and playing around with a couple of links with priority rankings. I thought it was some bi-product of adding the priority field, but it turned out to happen with any link regardless of priority, but only if no fields are changed.
By the way, what's the best way to add a field for a newly updated Links 2 database? Is there any advantage to first importing with the standard number of fields then adding the priority field vs. adding the priority field first then importing the database into the appropriate fields? The first option sounds the least cumbersome.
Dan
If you modify links through the admin area, but don't actually make changes (i.e. select one or more links and check them off to modify), then you get an error that the record cannot be found in the database.
When I first noticed this, it was just after setting up a priority field and playing around with a couple of links with priority rankings. I thought it was some bi-product of adding the priority field, but it turned out to happen with any link regardless of priority, but only if no fields are changed.
By the way, what's the best way to add a field for a newly updated Links 2 database? Is there any advantage to first importing with the standard number of fields then adding the priority field vs. adding the priority field first then importing the database into the appropriate fields? The first option sounds the least cumbersome.
Dan
Admin Modify Observation