I updated http://drupal.org/node/143089 and can see my update if I select the specific revision, but if navigate away and then come back, I see the old version.
If it matters, I am on the Doc team.
I updated http://drupal.org/node/143089 and can see my update if I select the specific revision, but if navigate away and then come back, I see the old version.
If it matters, I am on the Doc team.
Comments
Comment #1
Anonymous (not verified) commented3rd attempt
OK there is something going wrong i just typed out a reply , and was told this page was not found. I saw the same when i fisrst opened your issue a few secconds after it appeared in recent posts.
As to you link I got the latest version on first selection, but like yourself navigate away and back and we get the January version. Also if you go to revisions , Todays version is listed , but select it and you get January's
Comment #2
Anonymous (not verified) commentedFuther followup after the page finally saved IE crashed, but on return to Drupal the latest recent post showing was over 2 hours previous
Comment #3
WorldFallz commentedSomething's definitely amiss-- probably with caching. I keep getting "page not found" when clicking on topic in the "new forum topics" box. When I try to reply to a thread through the forums, it allows me to click reply but then I get 'page not found' when i submit the topic. Also, i keep getting different views of the forum pages each time i return or refresh the page-- sometimes topics that are very old are showing as 'unread'.
Also search gets 'page not found' as well.
At first I thought maybe it was a browser issue, but it happens regardless of which browser I use.
Comment #4
Anonymous (not verified) commentedI found this thread that appears associated
http://drupal.org/node/271215
Looking at the Recent posts , i just saw one posted 11 times probably for the same reason
Comment #5
Jeff Burnz commentedI'm getting "updated" and "new" on posts I've already read - when I view my tracker and, so far only once, in "My Projects" page.
Comment #6
nancydruFrom what I could see, it looks like maybe one of the servers may have had a clock problem.
Comment #7
vm commentedQueue cleanup:
This is fixed?
Comment #8
nancydruAFAICT