Bug 166942 - Published Appearance theme extensions for 25.2 will no longer work at 25.8 release
Summary: Published Appearance theme extensions for 25.2 will no longer work at 25.8 re...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
25.8.0.0 alpha0+
Hardware: All All
: high normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 167014 (view as bug list)
Depends on:
Blocks: LibreOffice-Themes 164970 166657
  Show dependency treegraph
 
Reported: 2025-06-10 14:31 UTC by V Stuart Foote
Modified: 2025-08-02 21:23 UTC (History)
12 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description V Stuart Foote 2025-06-10 14:31:58 UTC
As noted https://bugs.documentfoundation.org/show_bug.cgi?id=164970#c46 internal format for Appearance themes published for 25.2 will not work at the 25.8 release.

Those Appearance theme extensions probably need to be annotated to be 25.2 only, and new Appearance theme schema made available so designers can publish to the revised format.
Comment 1 V Stuart Foote 2025-06-10 15:11:46 UTC
@Rafael, will you be reworking your ThemeCreator pkg for the 25.8 revisions?
Comment 2 Rafael Lima 2025-06-10 21:11:26 UTC
(In reply to V Stuart Foote from comment #1)
> @Rafael, will you be reworking your ThemeCreator pkg for the 25.8 revisions?

I wasn't aware of that change.

I will take a look into it and see what needs to be adapted in the ThemeCreator.
Comment 3 m_a_riosv 2025-06-11 00:21:34 UTC
Seems in relation to my reported tdf#166657
Reproducible.
Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 389325166a3357d7a4e557dc4c223fe0bb7aeadd
CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
Comment 4 m_a_riosv 2025-06-14 10:39:37 UTC
*** Bug 167014 has been marked as a duplicate of this bug. ***
Comment 5 m_a_riosv 2025-06-24 22:24:23 UTC
*** Bug 166979 has been marked as a duplicate of this bug. ***
Comment 6 m_a_riosv 2025-06-24 22:25:00 UTC
*** Bug 167191 has been marked as a duplicate of this bug. ***
Comment 7 m_a_riosv 2025-06-24 22:25:20 UTC
*** Bug 167190 has been marked as a duplicate of this bug. ***
Comment 8 V Stuart Foote 2025-06-24 23:07:48 UTC Comment hidden (obsolete)
Comment 9 V Stuart Foote 2025-07-13 10:52:48 UTC
@Sahil, Heiko  in the mini 'Add more themes' button widget could we have some means to filter out appearance themes when the 'Required version' does not match the release build, e.g. to not shows ">= 25.2" appearance theme extensions for a > 25.8 build.

At a minimum, don't the "original" dual-mode Extensions still offered on the server need to be marked "25.2 only" in their compatibility field, and read that into the widget?

Folks migrating from 25.2 -> 25.8 are going to need to clear profile and reinstall appearance theme extension(s), don't want them to try to reapply a theme we know won't work.
Comment 10 m_a_riosv 2025-07-13 11:16:46 UTC
In fact, with a clean installation, and installing those that come with LO, some seem to work and others do not.

Those that do not appear to work:

OceanBlue
Lime Theme
Light Application Color
Comment 11 Heiko Tietze 2025-08-01 09:09:14 UTC
We cannot filter the extensions in this widget for a certain release. But since we have only a few submissions from two people, Mihai and Sahil, it should be easy to archive the outdated versions.
Comment 12 V Stuart Foote 2025-08-01 11:28:07 UTC
(In reply to Heiko Tietze from comment #11)
> We cannot filter the extensions in this widget for a certain release. But
> since we have only a few submissions from two people, Mihai and Sahil, it
> should be easy to archive the outdated versions.

Well, maybe not "archive" (25.2 release will be around for some time yet and still need the "Light Application Theme" and "Lime" themes.)

Couldn't their entry on the Extension server be marked '= 25.2' or 'only 25.2'?
Comment 13 V Stuart Foote 2025-08-01 11:31:35 UTC
(In reply to V Stuart Foote from comment #12)
> (In reply to Heiko Tietze from comment #11)
> > We cannot filter the extensions in this widget for a certain release. But
> > since we have only a few submissions from two people, Mihai and Sahil, it
> > should be easy to archive the outdated versions.
> 
> Well, maybe not "archive" (25.2 release will be around for some time yet and
> still need the "Light Application Theme" and "Lime" themes.)
> 
> Couldn't their entry on the Extension server be marked '= 25.2' or 'only
> 25.2'?

Those for 25.2 only should have been 'Light Application Colors' and 'Lime Theme'. The Lime theme could go away, but the Light Application Colors has been mentioned repeatedly in help and BZ responses for adjusting Dark background.
Comment 14 Mihai Vasiliu 2025-08-01 14:21:29 UTC
What I would have expected is that LO will select the newest compatible version of an extension. So if there is a version of the Extension compatible with the current LO version, that will be installed.
Comment 15 V Stuart Foote 2025-08-01 17:23:21 UTC
(In reply to Mihai Vasiliu from comment #14)
> What I would have expected is that LO will select the newest compatible
> version of an extension. So if there is a version of the Extension
> compatible with the current LO version, that will be installed.

Unfortunately I don't think there is any "version" logic built into the Appearance panel's link to the extension manager server. IIANM the user is presented with *all* extensions matching the query for 'Themes' category [1] to populate the 'Add more themes' pop-up dialog. 

If it is in that extension category, it is shown in the UI.

=-ref-=
[1] https://opengrok.libreoffice.org/xref/core/cui/source/options/appearance.cxx?a=true&r=fc741371fa283036cdbd12be59c769c7cac39437&h=416#416
Comment 16 Heiko Tietze 2025-08-02 07:25:09 UTC
The request returns one item per extension and not many per release. But Mihai's hope for a well sorted procedure should be verified. A piece of cake for the mighty JJ.

(In any case, the latest version will not work with older program versions.)
Comment 17 m_a_riosv 2025-08-02 21:23:10 UTC
IMHO, if no action is taken in this regard, we must be prepared to receive numerous user reports about these issues when the new version 25.8 is officially released.

Every version has its cross, :)