Search
Search titles only
By:
Search titles only
By:
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to Thread
Guest, we'd love to know what you think about the forum! Take the
Diabetes Forum Survey 2024 »
Home
Forums
Off-Topic
General Chat
Forum Bug Reports
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Oldvatr" data-source="post: 2583933" data-attributes="member: 196898"><p>Just had the Oops we ran into a problem notification again. One thing I noticed was that I entered the Forum by clicking on a link in an email to read a notified update. I read the update post ok, and I noted I had two alerts showing on the alarm bell token. I clicked on the bell, and got the Ooops popup. Now, the post #i had originally read was still selected and on my screen. I closed the post, and the alerts token changed to show only 1 unread notification which was just a response notification from Ellie. I was now able to click on the alert token, and it worked correctly. I did not refreah the page as requested, so I must assume that the update of the alert token had done this for me. Ergo, the problem seems to be occurring when a post is first read, but has not been closed, and thus there is a hidden update request queued that blocks access until the updated post is read and closed.</p></blockquote><p></p>
[QUOTE="Oldvatr, post: 2583933, member: 196898"] Just had the Oops we ran into a problem notification again. One thing I noticed was that I entered the Forum by clicking on a link in an email to read a notified update. I read the update post ok, and I noted I had two alerts showing on the alarm bell token. I clicked on the bell, and got the Ooops popup. Now, the post #i had originally read was still selected and on my screen. I closed the post, and the alerts token changed to show only 1 unread notification which was just a response notification from Ellie. I was now able to click on the alert token, and it worked correctly. I did not refreah the page as requested, so I must assume that the update of the alert token had done this for me. Ergo, the problem seems to be occurring when a post is first read, but has not been closed, and thus there is a hidden update request queued that blocks access until the updated post is read and closed. [/QUOTE]
Verification
Post Reply
Home
Forums
Off-Topic
General Chat
Forum Bug Reports
Top
Bottom
Find support, ask questions and share your experiences. Ad free.
Join the community »
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies.
Accept
Learn More.…