Loomio bugs, issues and feedback

@Robert Guthrie OK thanks

@Sam Rossiter Sorry, it's not currently possible to remove the "Threads" panel from the interface, but you can stop members from creating threads.

It's on the roadmap to show current proposals on front of the group page, however.

As a self-hosted instance admin I would like to remove the 'threads' functionality from the user interface completely. Is that possible?

yes, it helps but's it's not a sure thing because our threads are variously active.

@Julie Nevin thanks for the feedback. They are not easy fixes, so I'll have a think about it. Does ordering by Newest usually help to bring open threads first?

A request for searching threads: when I search threads for a key word, the results aren't actually that helpful. It's usually quicker for me to scroll manually through the group to find what I want. I'd like it to:

• Have an option to only search open threads (maybe have that by default, and enable us to include closed threads if we want)

• Give extra weight to the thread's title when determining 'best match'

@Julie Nevin thanks. Fixed this just now.

Minor bug: When I edit a thread, and I let people know what's changed, the new comment in the thread gives the date of the thread itself, not the date I edited it. Here's a screenshot of one from today:

@Julie Nevin ok fixed now. Refresh before clicking "Make a copy"

@Julie Nevin ahh... I saw the error come through earlier but did not understand how it was happening. Thanks for reporting - fix is ready and will be deployed within 30 minutes.

A new bug: When I click 'make a copy' at the bottom of a thread, I get a blank screen.

@Julie Nevin thanks. Will change "close thread" so that it does not create an entry within the thread that needs to be read. We're also going to disable comments and modifications to the thread when it is closed.

I've seen the mark as read behavior you describe - i'll try to fix it soon.

Similarly, when I choose 'mark as read' in the inbox for a long thread like this one, something isn't working. When I later open it up to make a comment, I still have a lot of yellow on the right hand side and it appears in my inbox again and a (1) appears by the group, until I click 'mark as read' all over again. Not a major issue, but a pain.

OK, here's a minor thing that bugs me: when a thread is closed, it seems to be marked unread in the system (perhaps because there's a new comment that says it has been closed). The group gets a (1) next to it, showing me I have an unread thread, but it's not in my inbox (which presumably filters out closed threads), so I have to go searching for it - or ignore the (1). It's either a task I don't need or a distraction, depending on my choice.

Either closed threads need to not be marked unread n the first place, or they need to appear in the inbox. I'd prefer the first option - after all, I can still find and reopen the thread if I want to.

@Julie Nevin thanks for the screenshot. Fixed now. (be sure to refresh your browser)

@Robert Guthrie weirdly just means the shape of the letter is different depending on whether it has a macron. Here's a screenshot of my post:

@Julie Nevin - thanks for reporting this issue. Could you please share a screenshot of how you're seeing the macrons - ie: what "weirdly" is for you? I'm not sure I'm experiencing the same thing.

(On Chrome at least,) macrons display weirdly - like they are using a different font. Given the prevalence of macrons in te reo Māori, it would be good to resolve this inconsistency.

aā eē iī oō uū AĀ EĒ IĪ OŌ UŪ

Is there any way to manually mark a thread as unread?

@Robert Guthrie

thanks for that...

i have often wondered (but never got to asking) how this informative metric worked.

provided members do do not paranoidedly have images barred...some providers seem to do this by proxy. i know that yahoo does if it ends up in spam and then is disinterred.

@Adam Hardy we do track email opens (when users permit their email client to open images) as well as reads via the app.

The number is total number of users, not visits/opens, which would be more.

A email summary will track all it's content as being opened.

The notification emails do not contain any mechanism to tracks openings.
(I open the mails within Thunderbird and I should be aware that a mail tries to to communicate “in my back”.)

Anyway, even if there was such a system, you never could be sure that Loomio knows a reader has opened a notification mail. From me, for instance, you shouldn't know it.

I don't know what happens when a reader answers by mail.

Hi All, quick question: when a thread title says "Seen by 613" does that mean that 613 have visited Loomio and read the thread online, or does the notification email track email openings, so 613 people have actually opened the notification email?

@Matthew Cropp thanks for mentioning this.

So it was our intention that Sense Check replaces Check.

However, if you wish for Check, you can recreate it with the Edit Template feature.

I've recorded a video showing how you might do this. Sorry it's slow - I'm slow today :)

Popping in to say I miss check polls, and am not sure of quite how to replicate them in the new system.

@Julie Nevin Sorry about this. I'll fix it this week.

All the templates we use appear to have vanished. Now we only have 'New thread' and 'New template' options to choose from when we start a new thread.

Hi @robertguthrie

I just discover the new version and have edited my original post about this to see what happens. It seems the issue with the > … quotes in Markdown is still there.

Not a big problem. Just to say or as a reminder.

I try it again to be sure…

> This should be a quote.

@Fran67 Thanks for reporting this. I'll add it to my list and look into it when I can.

And I see now another problem (see the first version of my post above):

In the line where I wrote…

The quote tag in the code part has been replaced by >

the “>” has been replaced by “& >”.

I suspect a problem in the handling of special characters in Markdown. I didn't notice any problem when using WYSIWYG. This reply has been written in WYSIWYG, as you can see (the quote line is O.K., here).

Problem still present in version 2.17.3

This is what I wrote in Markdown:

The preview was O.K.:



And you can see above (in my original post) how it looks after publishing it.
- The quote line appears as it must be tagged in Markdown and…
- The quote tag in the code part has been replaced by >

Also strange: as I edit my post to correct it, > appears in both places:

Sorry if I come up with a known (and solved) issue.

In Framavox (presently running Loomio version 2.15.5), quotes in Markdown (> …) are not rendered. They are in WYSIWYG and, strangely, also in preview mode, but not anymore when published…

So I make a little trial here:

> This should be a quote.

@david rayner actually, it seems to happen to me sometimes. I can't name how though. 😬

@Robert Guthrie yes...it seems to have gone away to the subway.

maybe the team fixed it in the mutual dreamscape? thanks, team.

again...thanks, team. ✅

@david rayner do you think it's possible to give me some specific instructions on how to reproduce this issue?

A few months ago I fixed similar behavior and made a fairly good improvement. Now, I can't reliably get it to incorrectly prompt me like before.

oh...ff 113 but on win 8.1(reinstalled)

a heads up...

today...almost every time i want to go somewhere else, i am asked if i want to discard choices...

this is not always pertinent (sometimes a welcome reminder...)

sometimes if i cancel...it just does what i was wanting to. (especially in the non-pert cases.)

this behaviour has been escalating in the last week or so. {8^(#

and i still miss the searchable emoji...

@Robert Guthrie YES, it's working! Bold is back for me! Well done, Rob!

@Ulrich Schur should be fixed now. Shift + Refresh please

@Ulrich Schur I found the issue! Thanks for your help. See this font-face declaration inside roboto.css

@font-face {
  font-family: 'Roboto';
  font-style: normal;
  font-weight: 500;
  src: local("Roboto"), url('/fonts/roboto-v29-latin-500.woff2') format("woff2");
}

I have "local" as the first place to look to find the font. Your browser is correctly looking at the local font cache and using Roboto. I should probably put "Roboto Bold" in this case, and i think it would cause a "miss", and continue to load the webfont.

@Ulrich Schur - I think it's worth investigating, I like to try to resolve everything that is reported. I'll send you a DM about a time.

@Robert Guthrie Yes, I opened the dev tool, refresh the page (I see all the many requests), filter for "robo*", nothing.

If I am the only person in the world with this problem, it's not worth investigating. But I'd be more than happy to go into a Zoom call and let you take a look at any time.

I am so surpised it's both my web browsers, so it seems a more fundamental issue. However, when I get the email notifications, I can see bold fine. I am also at a lose what is going on here.

@Ulrich Schur this is beyond my comprehension! .. almost.. Did you open dev tools before pressing refresh?

@Robert Guthrie I don't get any Roboto font loaded. Also, after reboot, it's still broken (which surprises me the most).

@Ulrich Schur can you show me.. The dev tools panel, open on the network tab, with the filter "roboto" after you refresh the page? Should look something like this:

@Robert Guthrie It won't show bold for me neither on Firefox 112.0.2 (64bit) or Microsoft Edge 113.0.1774.35 (64-Bit) - all on Windows 10. Last week or just even just a few days ago it was still fine. Or maybe I just need a reboot. Will report back again after the next reboot. Current screenshot below. I should maybe specify more clearly: I can select text and make it bold, but it just won't show up as bold. Across all posts and threads.

Can confirm that bold is working on Firefox on MacOS, as well as Chrome on Windows.

@Ulrich Schur - thanks for reporting. It does work for me:

I wonder what the difference is.

Anyone else missing bold?

It seems no longer possible to make text bold.