BUG REPORTS for new forum software [Thread Now Closed]

[SuperSleeper]

No sockpuppets were harmed during these tests.

Thanks Red... I appreciate the "do no harm" philosophy.  

[SuperSleeper]

This bug has now been resolved:

13.   [RESOLVED] When posting a message, the pop-up table of smilies isn't sized correctly.

[chill]

Has anyone noticed the editor getting really slow while typing?  It appears to be constantly round tripping to the server to check spelling.  When the server gets loaded, I can type several words before they start to appear.  I turned off Check Spelling While Typing and it has been OK since then.

[SuperSleeper]

Howdy Chill,

There is no spell-checker built into our forum software.

Many popular browsers have spell-check built into them, however.    When you type a text message here, no communication between your PC and the server occurs until you click on a button like "Post Reply" or "Preview Post" or click on a "smiley" or formatting button, etc.

There are no queries to the Apnea Board server for spell-check purposes.

[chill]

Well there goes a perfectly good theory dashed on the sharp rocks of reality!  Something really bogs it down.  I will poke further next time.

[MitchS]

This issue has been resolved:

4.  [RESOLVED] When clicking on the "Next Newest" link at the bottom of a thread (or other links that lead to the post ID [PID]), it loads the next newest post incorrectly, cutting off the top few lines in the post, so members must scroll up a bit to see the entire post.

I had to change the header from a scrolling header to a fixed header.  This fixed our issue above, at least temporarily.  When the theme developer comes out with his fixed code for the scrolling header, we can consider going back to that if you all wish to do so.

If you could, I'd like some folks to test this fix for me and report back here.  Now links to individual posts won't be cut off at the top, forcing you to scroll up to see the whole post (at least I hope that it works now).

Please let me know if it works - and also, let me know if you'd like to leave it as a fixed header or go back to a scrolling header, when/if the theme developer fixes that part of the code.

EDIT:  If you're still having problems, make sure and clear your web browser's cache and it should help.  (see this link for instructions on how to do that)

Works with Chrome, Safari and Firefox on MacOS Sierra.

[richb]

This issue has been resolved:

4.  [RESOLVED] When clicking on the "Next Newest" link at the bottom of a thread (or other links that lead to the post ID [PID]), it loads the next newest post incorrectly, cutting off the top few lines in the post, so members must scroll up a bit to see the entire post.

I had to change the header from a scrolling header to a fixed header.  This fixed our issue above, at least temporarily.  When the theme developer comes out with his fixed code for the scrolling header, we can consider going back to that if you all wish to do so.

If you could, I'd like some folks to test this fix for me and report back here.  Now links to individual posts won't be cut off at the top, forcing you to scroll up to see the whole post (at least I hope that it works now).

Please let me know if it works - and also, let me know if you'd like to leave it as a fixed header or go back to a scrolling header, when/if the theme developer fixes that part of the code.

EDIT:  If you're still having problems, make sure and clear your web browser's cache and it should help.  (see this link for instructions on how to do that)

Works with Chrome, Safari and Firefox on MacOS Sierra.

Works with Firefox on Linux Mint 18.3. If I click on the Next Newest button when on the top post I get a 404 page not found error. I guess this is as it should be.

Rich

[MitchS]

This issue has been resolved:

4.  [RESOLVED] When clicking on the "Next Newest" link at the bottom of a thread (or other links that lead to the post ID [PID]), it loads the next newest post incorrectly, cutting off the top few lines in the post, so members must scroll up a bit to see the entire post.

I had to change the header from a scrolling header to a fixed header.  This fixed our issue above, at least temporarily.  When the theme developer comes out with his fixed code for the scrolling header, we can consider going back to that if you all wish to do so.

If you could, I'd like some folks to test this fix for me and report back here.  Now links to individual posts won't be cut off at the top, forcing you to scroll up to see the whole post (at least I hope that it works now).

Please let me know if it works - and also, let me know if you'd like to leave it as a fixed header or go back to a scrolling header, when/if the theme developer fixes that part of the code.

EDIT:  If you're still having problems, make sure and clear your web browser's cache and it should help.  (see this link for instructions on how to do that)

Works with Chrome, Firefox and Safari on iOS 10.2

[OpalRose]

Clicking on "Next Newest" takes me to the next THREAD with a new post, not the next page in the thread I am reading.  In other words, it takes me to a different thread.  Is that the way it's supposed to work?   Sometimes, it takes me to a 404 Error Page.

If clicking on the "next page" button either at top of thread or at bottom, it correctly takes me to the top of next post and is working properly, it doesn't cut off like before.  It seems to be working properly on Desktop windows 10 and IPad.

[OpalRose]

Reply, Reply with Quote, and Quote Multiple Posts all seem to be working fine for me on Desktop Windows 10 and IPad.