With a previous beta version, I was using a local addons “Project” filepath to install 5.2 addons. But it doesn’t seem to be working on my re-install. But there is no feedback as to whether the Addon Manager is successfully reading the list of addons.
The “Where to Check” in the General tab of the 5.1 Preferences was similar. You only knew if it was touching the file when it listed addons to install. When Gramps was up-to-date with Addons, you couldn’t tell if it failed to poll or if everything was current.
In Addon manager complains about /addons/master/gramps52/listings/addons-en.txt , @avma was getting reports of 404 errors. Perhaps the Warnings feature of Gramps could report 404s if it isn’t finding the
And another unanswered thread ( How should a gramplet validate a (local, network, internet) file path string? ) asks about the approved way to validate a path in Gramps.
For one thing Gramps 5.2 only looks for addons-??.json files, not .txt files.
That’s true. Sorry, that
.txt expectation is a holdover from a previous set of 5.1 docs… since the 5.2 Project tab only specifies the parent of the
download folders containing the
.tgz files expected by the Addon Manager.
I could just add an error icon to an entry in the projects list if the listings file cannot be parsed.
Would you like a feature request for tracking purposes?
By the way, the re-install is on Windoze. The way that OS expects to handle local paths differently than Fedora might be part of my problem.
It is kinda late for a 5.2 change. And this sounds like a simple but highly visible change. So adding for 5.3 would show evolution is still possible for recently added features.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.