I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing I am testing
SB, as per above test, line wrapping between words seems to be working as it should (but I haven't checked the generated code).
FYI, I just noticed that one af the ?problems seems to be that when press <quote>, then have to switch to the Advanced Editor & often what looked OK in the Simple Post Editor is now often mangled in the Advanced Editor.
Whereas in BLF's previous incarnation we could pre-select Advanced Post Editor for posting in threads (in Settings).
Yeah, I’m really sorry about that, it’s another one of the missing features in this new version. I would strongly suggest that everyone use the Simple Post Editor for almost everything except for complicated reviews or posts that need heavy formatting.
Whenever I click on a new discussion thread, it opens up on the second post and I have to scroll back up to see the OP. :SICK: Am I doing something wrong (need to reconfigure my setup in some way)?
Hang me for this,its ok… Theres quite some functionality just taken away in this release and stuff that just does not work. I appreciate your effort SB, but my honest opinion is that I prefer the previous version. I must admit, Im not sure why this release was pushed, might be good reason though.
They are discontinuing security updates for the old version. Meaning if you tried to stay on the old version it would become vulnerable to hacking. Sb put off updating as long as he could.
I have noticed, that with some frequency when clicking a post and having it open in a new tab that the page will not load. I never had this problem with the old server. I am running Firefox and Chrome on Windows 7 with multiple machines and have seen the behavior on multiple machines as well as Android. I have also seen this across multiple network providers.
It could be a bandwidth problem or a problem with the initial page request or part of the initial handshake being eaten somewhere.