Show page numbers in list of threads?
-
darjeeling -
11. Juli 2017 um 16:46 -
Erledigt
-
-
I doubt that will work properly since every user can set the number of posts per page. And then it would be a performance nightmare to check for every user how many posts are set per page and then calculate the page numbers.
-
-
Ah ok, that's a single thread.
-
Correct an that is per user different based on the custom settings or default.
-
-
- Offizieller Beitrag
-
haha
Oh well I didn't think it was there yet.
Then its even better Thanks Alex
-
That's great, thank you. (Is there any way to put all breakpoints on the same line? I have had to repeat the entire structure=, once for each breakpoint).
Identifying the CSS to use is proving problematic. How for example can I find out what to use if I want to un-hide the author of the last post in a thread, in the thread list view?
And the "thread contains your own posts" mini-avatar?
I'm sure once I know where you are getting the classes from it should be straightforward for me to find the rest myself.
Is it just inspection of the page using Chrome's developer tools, or do you need deeper knowledge of the system?
-
- Offizieller Beitrag
(Is there any way to put all breakpoints on the same line?
Absolutely, you can nest things and put more stuff into the same instruction:
CSS
Alles anzeigen@include screen-md { .firstClass .someElement { color: red; } body[data-page-id="123"] p { content: "I'm a paragraph!"; > small { color: #999; } } }
Line 6-12 are somewhat interesting because it is literally the same as if you wrote:
CSS@include screen-md { body[data-page-id="123"] p { content: "I'm a paragraph!"; } body[data-page-id="123"] p > small { color: #999; } }
Might save you some time, you can of course write the full selector at any time, the compiler doesn't mind either.
I'm sure once I know where you are getting the classes from it should be straightforward for me to find the rest myself.
Is it just inspection of the page using Chrome's developer tools, or do you need deeper knowledge of the system?I've replied to your ticket while you were writing this message, check your inbox for a guide
-
Thank you
I was meaning more like
CSS@include screen-md-down screen-xs screen-sm screen-sm-down screen-sm-up screen-sm-md screen-md screen-md-up screen-lg { .paginationTop { display: block !important; margin-top: 20px; /* wastes slightly less space than the default */ } }
but this doesn't seem to work so I have had to do them all in a block each.
-
- Offizieller Beitrag
Oh, okay. Well, actually you don't really need to, because the breakpoints can overlap. If you use the same selector, things like
will target everything that is not a desktop device. Since the desktop view should already match your expectations, there should be no need to add screen-lg to. So if you're willing to use the !important sledgehammer from time by time, you should get away with the above media query only.
The available list of breakpoint, and when they apply, can be found here: https://docs.woltlab.com/view_css.html#available-breakpoints
-
This doesn't work, for some reason. Not to worry too much though as separate blocks is fine.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!