# Dealing with long titles (of assets, logs, etc) **URL:** \ **Category:** Using farmOS\ **Tags:** feature-request\ **Created:** [March 31, 2025, 11:48am UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264 "2025-03-31T11:48:20Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![BOTLFarm](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/botlfarm/32/74_2.png) [@BOTLFarm](https://farmos.discourse.group/u/BOTLFarm)\ **Post date:** [March 31, 2025, 11:48am UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/1 "2025-03-31T11:48:20Z")
> [@Planting quickform ideas](https://farmos.discourse.group/t/planting-quickform-ideas/2263/2): > > > [@Planting quickform ideas](https://farmos.discourse.group/t/planting-quickform-ideas/2263/1): > > > > As an extra help, in all tables show the full item name on hover. > > đź’Ż Agree! I actually had this same thought the other day. We should absolutely implement this. +1 for this. The log name length is actually a large pain on mobile also. To view the whole log name on a small screen you not only have to open the log but open the edit view. ---
**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\ **Post date:** [March 31, 2025, 12:02pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/2 "2025-03-31T12:02:48Z")
> [@BOTLFarm](#): > > The log name length is actually a large pain on mobile also. To view the whole log name on a small screen you not only have to open the log but open the edit view. Oof yea that’s rough. Curious how we might solve that… there’s no “hover” on mobile. 🤔 ---
**Author:** ![BOTLFarm](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/botlfarm/32/74_2.png) [@BOTLFarm](https://farmos.discourse.group/u/BOTLFarm)\ **Post date:** [March 31, 2025, 12:21pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/3 "2025-03-31T12:21:02Z")
I’m not sure in tables how to solve that, maybe allowing adjustable colomn widths? They could be dragged larger when needed. On the actual log view could you just allow that field to wrap? ---
**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\ **Post date:** [March 31, 2025, 12:42pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/4 "2025-03-31T12:42:35Z")
> [@BOTLFarm](#): > > On the actual log view could you just allow that field to wrap? Looks like this was intentional by the maintainers of Gin (the theme that farmOS uses): [https://www.drupal.org/project/gin/issues/3167928](https://www.drupal.org/project/gin/issues/3167928) > When you have a long title it gets abbreviated > … > Instead of chopping it off and letting it “hide” behind the save button make it visible on more lines. > This is intentional, because the title is sticky so it needs a limitation otherwise the sticky part can grow too big. We might be able to force it to wrap, but the more we go against the grain of Gin, the more likely we are to break things (or be forced to maintain hacks/overrides as things change upstream). So best to go with the flow as much as possible, and think of alternatives, IMO. One alternative solution (for the log page) might be to add the full untruncated title to the content itself (eg: above the “Timestamp: …”). In either case, it probably makes sense to move this to a separate thread. We’re getting a bit off of the original topic. 🙂 ---
**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\ **Post date:** [March 31, 2025, 12:44pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/5 "2025-03-31T12:44:55Z")
> [@mstenta](#): > > it probably makes sense to move this to a separate thread Ah right! Discourse has an option to do this! I’ve split this to it’s own topic. 🙂 ---
**Author:** ![gbathree](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/gbathree/32/286_2.png) [@gbathree](https://farmos.discourse.group/u/gbathree)\ **Post date:** [March 31, 2025, 3:39pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/6 "2025-03-31T15:39:27Z")
IMO I like defaulting ellipsis - that’s smart. I just think (see other thread) we should improve search to include location and eliminate (by default at least) inclusion of the field name in the planting. It would help all these issues. Tables are really important, and the little details matter for usability! ---
**Author:** ![Symbioquine](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/symbioquine/32/284_2.png) [@Symbioquine](https://farmos.discourse.group/u/Symbioquine)\ **Post date:** [March 31, 2025, 4:12pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/7 "2025-03-31T16:12:19Z")
I’m not sure I know what “defaulting ellipsis” are, but it makes me think that there are some ways to deal with the lack of hover on mobile… The ellipsis could be a button/tappable to reveal the full title (either inline or as something like a tooltip). Alternatively (and probably less intuitively), the hover tooltip could be triggered by a long press on mobile. (This is how [XKCD](https://xkcd.com/2141/) gets around the need to expose the hover text for the comics to fully make sense on mobile.) ---
**Author:** ![gbathree](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/gbathree/32/286_2.png) [@gbathree](https://farmos.discourse.group/u/gbathree)\ **Post date:** [April 3, 2025, 12:23pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/8 "2025-04-03T12:23:58Z")
Mike said: > We might be able to force it to wrap, but the more we go against the grain of Gin, the more likely we are to break things (or be forced to maintain hacks/overrides as things change upstream). = me saying “default ellipsis” – I assumed he meant there is a decision in Gin theme to use them. So I like that decision was my point 🙂 I just think you need a reasonable way to also see the full thing when needed quickly without leaving the page (etc etc as in my previous answer). ---
**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\ **Post date:** [April 3, 2025, 1:20pm UTC](https://farmos.discourse.group/t/dealing-with-long-titles-of-assets-logs-etc/2264/9 "2025-04-03T13:20:47Z")
> [@mstenta](#): > > the more we go against the grain of Gin, the more likely we are to break things (or be forced to maintain hacks/overrides as things change upstream) I forgot to highlight what’s implied by this… we can open issues (and search for existing ones) in the upstream [Gin issue queue](https://www.drupal.org/project/issues/gin?categories=All). Some of these things are general to anyone using the Gin theme, not just farmOS, and it might make sense to propose changes/fixes there, which everyone will benefit from.