j.tweedie's picture

Unread reports

Prior to the site design being changed, when I view someone's report then clicked on Unread the item in particular will have disappeared from the view as it would no longer be "unread". However, I've noticed this morning that after viewing something it is still appearing in the "Unread" section - has anyone else noticed this?

Reply

Comments

j.tweedie's picture

Is it really not possible for

Is it really not possible for someone from the iSpot team to comment on this? The Unread section simply isn't working, time and again items I've read, commented on or agreed with observations are coming up as Unread, and it's making it difficult to navigate through and find things I haven't already read.

Has anyone else had this problem?

I'm using Safari on a Mac, and it worked before the site changed.

Dioctria's picture

Didn't work for me either.

Didn't work for me either. Looked at an unread item, agreed it, navigated to the Unread page again (not 'go back'), the item was still displayed.

(Firefox on PC.)

David

Dioctria's picture

Not Real Time?

Interestingly, I just had another look and the item has now been cleared from my Unread list.

I think that there is a timing issue here. We are assuming that the site was written to update in real time, but some things at least seem to be done by a scheduled check. You can see the same thing with the My Spot page. It says that there is nothing new to see but you go straight to observations and find agreements have been added to identifications you have made.

David

gardener's picture

I'm having the same problem

I'm having the same problem with 'read' posts not clearing from my 'Unread' list, and its a nuisance as I end up reading some twice and missing others.....
(Using XP and Mozilla Firefox)

richard's picture

caching changed

Hi John,

Due to the site becoming more popular we've introduced caching to some pages which means you may not see changes straight away.

However, the unread page is a page which could do with being updated straight away, so with this is mind we've altered the caching to allow this.

Hope this solves your problem.

Apologies for taking time to respond.

Richard G - iSpot technical team