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 addons-en.txt [ recte: addons-en.json file which is the default and fallback for other language users ] file?
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.
1 Like
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 listings and download folders containing the .json and .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.
1 Like
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.
How can the 6.0.6 be hacked to have such an indicator?
I just tried downloading a GitHub generated ZIP of the Isotammi addon repository (which includes listings for 5.0, 5.1, 5.2, and 6.0) and extracted it to the desktop of a Windows 10 box.
I have (apparently) been unable to successfully touch the .json in the listings subdirectory. I’m not confident of where the failure lay. The only feedback is “There are no available addons of this type” (twice, once in the title and again in the body) followed by “Checked for ‘update’ and ‘new’”. So I don’t know if it actually found the folder, found the json, read the json successfully, or had a valid compare.
Used the Preferences Family Tree tab’s Backup path: field to navigate to the isotmmi-addons\addons\gramps60 listings folder and then harvest that path. Then converted the delimiters as indicated in the wiki. (screen capture shown in thread “Need linux and mac examples tested for local Addon Manager projects”)
So there is no idea whether the problem was with the file scheme, the delimiters, the path, the delimiter between the project and the appended component, and the listings/addons-en.json portion, the data in the json, or somewhere else.
