Problems with extension manager

[cspalding360]

Using LibreOffice 7.4.5.1 on macOS 10.13.6 (High Sierra), English language:

1. Dictionary extensions are locked for non-administrator users (all are “Bundled with LibreOffice”). Can they be unlocked?
2. Attempt to Add a new version (2023.02.01) of the English dictionary by a non-administrator causes the error: “/Users//Library/Application Support/LibreOffice/4/user/uno_packages/cache/uno_packages/lu30932xrw3f2.tmp_/dict-en-20210501.oxt does not exist.” (The current “bundled” English dictionary is version 2022.05.01, not 2021.05.01.)
3. The English dictionary is not locked for the administrator user, but “bundled” extensions are locked. Can they be unlocked? If they can, would deleting the French & Spanish dictionaries cause a problem?
4. Updating the English dictionary (as administrator user) does not apply to other users. Why not? (The online documentation states that an extension can be added for self only or for all users, but I don’t see that option when I Add. Also, the Options button is always dim.)
5. Attempt to update extensions, either with the Check for Updates button or right-clicking on an extension and selecting Update…, crashes LibreOffice. To update an extension, I have to Remove the old one and Add the new one. (This appears to have been a problem for years!)

[mikekaganski]

As explained on LibreOffice Developer's Guide: Chapter 4 - Extensions - The Document Foundation Wiki, bundled extensions are exclusively managed by installer program. And AFAIK, macOS installer does not provide ways to selectively install/uninstall them.

Your #2 is obviously a bug; but it’s hard to tell which. Normally, it is OK to install a newer version of an extension as a user, when there already is a version of the same extension installed in any repository (user/shared/bundled). The user repository takes precedence over shared and bundled, so it would normally just work; but the installation error needs investigation (looks like your profile has some remnants of an older user-installed extension).

The #4 possibly indicates the same thing: some users might have the extension in user repository, and so the updated shared extension is not used for them.

I’d start with resetting profiles of the affected users. As to the crash on update check … someone on macOS should investigate; it definitely works for me on Windows.