Trying to navigate to a specific post in a filtered topic fails.
-
- Open a topic.
- Filter on a single user.
- Click on the "green whatever" scrollbar thing.
- Enter a post number you'd like to visit in the range that is suggested by the widget.
- Click 'Go'.
- Observe that where you end up is nowhere near where you'd expect to end up.
- AFAICT, it's still expecting input in the range of the unfiltered thread.
- Fail.
-
I'm pretty sure this has been around since pre-1.0. And it's still not been fixed
-
Yet another example of why Discourse should still be in Beta.
-
-
-
-
WONT_FIX WORKS_AS_DISCOSIGNED APPARENTLY THE BODY OF THIS POST IS INVALID BUT NOT IF I PUT A LOWERCASE CHARACTEr
-
-
Yes, we're running a beta version, but you know what I was getting at.
-
technically, the first beta after the 1.2 release.
even if stable is more close to AE2's "stable" builds than chrome's "stable".
-
But has there actually been a new beta? Even when we were on tests-passed, it would say we were on some beta. That reported version requires discosalt.
-
Discobeta?
-
-
Nice.
I am citation.
-
You coin the word, you get citation ;)
-
technically, the first beta after the 1.3 release.
I thought it was 1.2 that had been released...
-
gah, you're right!
Also, the version reported in the dashboard is on two tracks (beta, stable) instead of three. That's why it always reports as a beta.
Could change it to be a git hash
-
It would be useful to say something like, "beta X +" to indicate that we were at the beta plus some stuff.
-
$ git describe v1.2.0.beta6-91-gecb9112 $ git checkout v1.2.0.beta6 $ git describe v1.2.0.beta6Sounds like a plan.
-
Yeah, that would actually be helpful around here, where we're actually on latest (or whatever they're calling it these days) but we're trying to only upgrade to actual beta releases.
I know there's additional stuff that actual admins see on the admin dashboard, but that's not really a good excuse to LIE about it.
