[Libreoffice-ux-advise] [Bug 132352] "Show all updates" tickbox in extension manager not working as expected

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=132352

--- Comment #6 from sergio.callegari at gmail.com ---
As the original reporter of the bug:

my issue is not with the presence of the "show all updates" button that makes
sense and that I would not touch. My issue is what happens /after/ you press
that button.

In my case, the system invariably:

1. shows a list of extensions (typically Zotero and TeXmaths) that are /not/
disabled on my system
2. manual checks reveal that these extensions /are/ at the latest release, so
there cannot be anything to update about them
3. for these extensions the description field rather than providing a
description shows an error message. This is typically something like "An error
occurred: Document is empty Line: 1 Column: 1"

Hence, my bug report, that goes with this questions:

- Why the "show all updates" show extensions that are not disabled and not
update-able being already at the latest release? Shouldn't it show something
just in case there are extensions that are disabled or otherwise not set for
automatic updates?

- Why is there no description in the description field? Should one not
recognize the extension by name, how is the description field useful in helping
him/her? Being that the extension is actually installed and that the
description is shown in the extension list pane, why cannot it be retrieved at
this point?

- Why the error "document is empty"?

My guess is that when LibO interrogates the extension database at LibO
something goes wrong for some reason. Either LibO misinterprets some records or
the database contains some wrong or stale records. This causes LibO to see in
the database some extension releases for which it cannot properly read data.
Because of these, LibO chooses to consider these as "releases to ignore"... and
these get shown in the "show all updates" panel.

It is this last part that should not happen. If LibO fails to understand some
records that should be fixed or if the upstream extension database has
incorrect entries of records those should be fixed. Otherwise, the behavior is
just rather confusing.

What I expect from "show all extensions" is to show:

- If there are updates to extensions that I have manually disabled (maybe
precisely because they have issue, but I have an interest in checking if
updated versions exist that may fix the issue);

- If for some extensions there are updates that have been marked by the
developer as to be ignored for automatic updates (e.g. because of a beta or
pre-release status).

-- 
You are receiving this mail because:
You are on the CC list for the bug.