jonescc
commented
10 years ago Adding all the collections on step 1 to the map does affect the results returned when you refresh for some reason. That combined with #646 means that it is possible for the above to happen (It happened for me - I got either the aatams layer or the argo layer displayed). The fix for #646 means that all the layers should be findable at least, but I'll have a look at why the order changes after adding all the collections to the map.
[Portal Build Info] Base URL: http://123.aodn.org.au/aodn123 Build date: 05/11/2013 13:42 Version: 3.6.0-rc1 Instance name: AODN Environment: prerelease
I cannot repeat this and I'm not sure if I am going crazy... but I thought if I report what I think I saw it might be an easy investigation.
Steps to reproduce/what I think I did:
I was adding all of the collections to the map (to check another bug I am about to report), so I clicked the first collection then when taken to step 2 clicked step 1 tab straight away so not waiting until collection loaded.
Repeated for all collections available so all collections are now on the map, then I went through and made each one active to see if it had a subset tab. On a piece of paper I wrote the active collection names as I saw them there were 3 I wrote down.
SOOP XBT Profile data Latest XBT Profile Catami deployments
I then refreshed the portal and went to go and add the collections I had written down again to the map but the first 2 were not in the list. So I added all the SOOP collections I could see in the list as i though maybe the active titles had been altered to appear shorter but in the active list they are all the long titles. So i don't know what happened but I am 99.9% certain I wasn't being lazy and only writing half the active layer titles because you can't see the last bit of the titles in the active layer list to be able to write them.