Kalkendotters

Nothing you can do a thing about :-( There are currently two problems with bookmarks: (see a lot of other forumtopics) A ) The paging within the bookmarklists does not work correctly, i.e. you cant go to the next/previous page B ) If you do anything on the bookmarkpage it tries to add the bookmark in the rightupper corner. Since that is default set to GCXXXX and that cache is unpublished you get the 'cannot add unpublished' error. So deleting the list and rebuilding wil not help you.

It happens to me too. A quick guess would be that is is caused by the GCXXXX 'add bookmark' button also on this screen. Since the caches are now already numbering at GCXZxx the GCXXXX is now a valid cachenumber. Somehow it interprets every click on this screen as an addrequest for the cache GCXXXX. Like to see what happens when GCXXXX becomes published.. []

Thanks As long as its consistent, I can live with it.

And just why are you refreshing the page so many times?? (Markwell's point) The problem is that showing the second page is like doing a refresh on the page and the second page doesnt show the rest that coulnt fit on page one. You could get e.g. page1: cache1 cache2 cache3 (invisible page2: cache4 cache5 cache6) If you now click through to page 2 you could get: (invisible page1: cache3 cache2 cache5) page2: cache6 cache1 cache4 Missing cache 5, and seeing cache1 two times. I hope this example makes it clear.

You have seemd to miss MY point... The link above will give the most recent caches sorted by date, but just by date. So any cache activated on the same day can be either on the top or on the bottom of the caches for that day. This means that if you jump to page 2, you might see some caches you already saw on page 1; and miss other completely. Try to refresh the page a couple of times, you will be amazed

Yes I know. I can also write down the caches on a piece of paper in the order I would like... It is just that when I request information via a webpage it should be consistent in the way it is presented, and not use some arbitrary/non-repeatable sort. Causing users to sometimes mis a cache.

When I request a cachelist, this is sorted on de date; however in some circumstances this leads to problems in the sorting: when you request the list a second time the order of the caches is different. As long as all the caches with the same date stay on one page it is not really a problem, however if they are split on pagebounderies you will get part of the caches from the first page also on the second page; missing caches that should be on the second page, but are now on the first page. See for example the list of new caches in the Netherlands where 29 caches are added on the 19th of july: http://www.geocaching.com/seek/nearest.asp...&submit3=GO Go there and refresh the page a few times, you will see the caches change place. This also seems to happen on other cachelists based on dates, like found-by-cacher and placed-by-cacher Simple solution would be to also sort it on GC-code or on the guid.