email thread confusion

I was looking around for a way to change my email view from threaded to a more normal view, and I found the link below, where it says that you can change from “threaded” to “singleton” pretty easily. But as I was looking at it more, it said that this feature was added in 5.2 and the latest release for the mail app seems to be 5.1.5.
Is the 5.2 email thread just a plan for a future update or do I need to do something to get this feature?
If there is nothing I can do to get this feature, do you guys know any way to get non threaded emails? thanks

The latest docs are generally for the current development branch. 5.2 is currently unreleased. It looks like a 5.2 alpha release was tagged a few weeks back so it’s still in progress.

Thanks for clearing that up. It just seemed a little obtuse to me to upload a manual before all the updates in it are released

That’s why there are different versions of the docs. See https://docs.nextcloud.com for the list - and to make sure you’re looking at the one for the version you’re interested in.

1 Like

You can also bookmark links to specific versions:

https://docs.nextcloud.com/server/30/admin_manual/

https://docs.nextcloud.com/server/31/admin_manual/

…or you can bookmark the link to “stable”, which should always link to latest stable version, which is currently 31.

https://docs.nextcloud.com/server/stable/admin_manual/

EDIT:

It seems that the stable version is linked to 30, and the latest version is linked to 32. Therefore, it is probably best to use a specific version

EDIT 2:

It seems to even more inconherent, and latest and stable seems to be linking to different versions on a page to page basis. So it’s probably best not use stable and latest at all, but only specific version links!

EDIT 3:

It’s different yet again! :wink:

The latest and stable links are consistently linking to specific versions (30 and 32, respectively), but the feature is only mentioned in the docs of 30 and 32, but not in 31.

Link to 32, the feature is mentioned:
https://docs.nextcloud.com/server/32/user_manual/ro/groupware/mail.html#message-display-operation-mode

Link to 31, the feature is not mentioned:
https://docs.nextcloud.com/server/31/user_manual/ro/groupware/mail.html#message-display-operation-mode

Link to 30, the feature is mentioned:
https://docs.nextcloud.com/server/30/user_manual/ro/groupware/mail.html#message-display-operation-mode

Link to latest, the feature is mentioned…
https://docs.nextcloud.com/server/stable/user_manual/ro/groupware/mail.html#message-display-operation-mode

Link to stable, the feature is mentioned…
https://docs.nextcloud.com/server/stable/user_manual/ro/groupware/mail.html#message-display-operation-mode

However, that also means, that stable is linked to 30 instead of 31, which shouldn’t be the case imho…

Kind of confusing the whole thing… :wink:

Oh wow, thank you for laying it out. It kind of seems like an insane way to document, but I guess it works.

Hi,

We are making good progress with Mail 5.2, and there’s only one smaller thing to iron out before we will publish it. I agree, it might be a bit weird to have the documentation out before the release. cc @ChristophWurst

I will try to find out, why the documentation for stable31 is missing the feature. The change as merge also for 31 ([stable31] feat: mail display mode by backportbot[bot] · Pull Request #13221 · nextcloud/documentation · GitHub) and I also see it when building the documentation locally.

Could you log an issue at GitHub · Where software is built for it?

It’s indeed weird that 31 != stable.

Done: "stable" is linking to Nextcloud 30 instead of 31 · Issue #13356 · nextcloud/documentation · GitHub

In this context, I also have a suggestion:

‘Latest’ currently links to the next or upcoming version (currently version 32), which I find kind of confusing.

Would it not make more sense for ‘latest’ to link to the latest released version, and use a different link or tag for the upcoming release, such as ‘upcoming’ or ‘next’?

Fixed, sorry for the inconvenience

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.