Long Topic descriptions do not display the "no. of views" count

[aegersz]

A bit petty but i wanted to know if there was a way to sort this:

Long Topic descriptions do not display the "no. of views" count when in and viewing the top of thread.

Is there an easy way to display a second line with that information, please ?

[Antechinus]

Yes, there is. The problem is that by default Curve relies on an image for the header bars, and that image has a restricted height. So during 2.0 dev it was decided to use hidden overflow to deal with the problem of long titles (to avoid breaking the graphics).

Easiest way around it is to use a CSS gradient instead, and remove the height restriction, thereby allowing the text to take as many lines as it needs while maintaining reasonable looks.

This should work (let me know if it doesn't):

Code Select Expand

#forumposts .cat_bar {
    background: linear-gradient(#738599, #a8bace);
    height: auto;
    min-height: 31px;
    border-radius: 5px;
}
#forumposts .catbg {
    background: none;
}

[aegersz]

Cool but what source do i update ? my skills are very rudimentary and I'm not that familiar with the code to display the thread, so it's name eludes me.

[Mick.]

index.css

[aegersz]

Ok, I added the code to the bottom of ./Themes/default/css/index.css and it didn't make any difference.

I do have the right css.index, don't I ?

I cleared the file cache, just in case also.

[Arantor]

Did you clear your browser's cache?

[aegersz]

No but I just did after reading your post, Arantor

That did the trick because i switched to another browser to be sure.

It works !

Thanks guys; love ya's !

(maybe you should consider that the default ?) it looks absolutely fine.

[Antechinus]

It's a bit late to make it default for 2.0.x. 2.1 will not have the same problem.

[aegersz]

what about in the 2.0.16 upgrade ? 

I have now made so many tweaks on top of many mods, i may never be able to retain all my extra functionality on any subsequent release.

I have painted myself into a corner 

[Antechinus]

Lol. Yeah that is always a problem. I did something similar with 1.1.x a few years back. Rewrote so much of it that it was damned near a fork.

Anyway, as far as I know 2.0.16 will just be security and GDPR fixes. The team doesn't do interface customising in patches.

[Arantor]

They do do interface breakage in patches (login bug 2.0.14) and the long term fixes for the same (2.0.16)