Hi,
Gramps 6.0 will be release soon. Of course, Gramps Web will be updated to be based on Gramps 6.0 and all the relevant addons as well, but this will still take some time. So if you are using Gramps Web and synchronizing with Gramps Desktop, please do not upgrade until everything is ready.
You can follow this page to track the progress:
Obviously, any help on beta testing the new Gramps Web is welcome - I’ll post here once it’s ready for testing.
A post was split to a new topic: Targets for improvement
Can the moderator please move the previous post to a new topic in a different category? It is completely unrelated to this thread.
Don’t misunderstand I’m not complaining, trust me I have nothing but deep respect for open source contributes.
I’m trying to understand what needs to get done yet to make Gramps Web compatible with Gramps 6.x.
I see Gramps #2029 got merged, but I don’t see it in the release notes for 6.0.1 (and haven’t dug through the commit history of 6.0.1.) Would it maybe be possible to link github issues to Gramps 6.0 upgrade guide - Gramps Web so that it’s easier to see what still needs to get done and maybe make it easier for people to chip in effort if they have cycles?
This PR references this issue:
0013721: Missing metadata when Gramps crashes before a new database is closed
That is the following bullet item in the 6.0.1 Release notes and 6.0.1 Change Log
- Avoid empty metadata fields. Fixes #13721
Regarding the changes for Gramps Web by @DavidMStraub (and for Betty by @bartfeenstra ) compatibility changes… those are enhancements to help the Gramps engine be more independent of the Gtk GUI dependencies. And as “enhancements”, I believe that they are on the 6.1.0 roadmap.
That means that Gramps Web is probably never going to be 6.0 compatible. So maybe the Gramps 6.0 upgrade guide - Gramps Web should be redesignated as a 6.1 upgrade guide?
No, that’s not correct.
The sub-issues of this issue track what still needs to be done. Adding a link to the upgrade documentation is not a bad idea.
New thread: Gramps Web & Gramps 6.0: Beta Testers Wanted
Gramps Web API 3.0 has been released. Thanks to the beta testers!
The Gramps Web docker images (ghcr.io/gramps-project/grampsweb) will be updated with the next release of the Gramps Web frontend (v25.5.0), today or tomorrow.
Hooray! Thanks, David!
Where are the current release version numbers for Gramps Web API and frontend maintained as a list?
updated:
I was visiting the demo site and wanted to determine how old it was. There is no Gramps Web version history on the wiki. And the Installing Gramps Web for online collaboration" section in the Download wiki page does not list version numbers. There is no version template for Gramps Web either.
From System Information tab in settings on the demo.GrampsWeb.org
Gramps 5.2.4
Gramps Web API 2.8.2
Gramps Web Frontend 25.3.1
Gramps QL 0.3.0
Sifts 1.0.0
locale: en
multi-tree: false
task queue: true
OCR: true
chat: false
Unfortunately it looks like the demo site stopped auto-updating, will fix it tonight.
That there is an “auto-updating” of a Gramps Web installation is intriguing.
Perhaps there could be a Discourse thread describing how you accomplished such a feat? It might inspire some users to build some webmaster site management features.
The script is open source …
From System Information tab in settings on the demo.GrampsWeb.org
Gramps 6.0.1
Gramps Web API 3.1.0
Gramps Web Frontend 25.5.2
Gramps QL 0.4.0
Sifts 1.0.0
locale: en
multi-tree: false
task queue: true
OCR: true
chat: false
Thanks for fixing the auto-updating of the demo site.
But the site still requires Re-indexing after every reset so that you can choose the Home Person.
This seems like an opportunity to fix 2 things.
the Set Home Person gives ZERO feedback that the index needs re-indexing. You have to recognize when there are no options that you need to re-index. If the database has more than zero people and the index it blank, it should give better feedback than nothing showing in the Home Person selector.
The admin settings page says:
Manually updating the search index is usually unnecessary, but it may become necessary after an upgrade.
This message is misleading. There is a reproducible case (of ALWAYS needing to re-index). This should enable either: isolating and eliminating the cause after an update; or, modifying the demo-site rebuild script to also re-index. And either allows adjusting the message on the page so that Gramps Web seems more reliable/predicatable about the re-indexing.
Note that if the user is logged in as an editor, contributor or member, they are stuck. This makes the demo site useless for those user types. I think that only the owner can re-index.
But it is hard to test since I do not know the reset/rebuild schedule. I rebuild the index (to remember how to fix the problem) and know that I need to re-test after the next reset. But get distracted by other issues before the next stage of the isolation testing.
Disturbingly, I realized the reason it was not working was a bug in the search reindex CLI command. Strange that nobody else noticed so far. I guess the CLI is not used very much. Will be fixed in the next release.
I do not have a Gramps Web installation so have not experimented withe installation process.
If there an install/upgrade checklist that includes the re‐index step? The 6.0 Install/Setup list does not include this step.
It would be unfortunate if an admin setup or upgraded and did not remember to reindex, leaving the site unusable for non-owner visitors. (Perhaps GrampsWeb needs an automated “sanity” or “I’m alive!” test? Where it validates that it can deliver data on a scheduled basis?)
And is there a default Home Person setting? It would be nice if the Set Home Person suggested a Person … even when the index was missing.
Indexing is automatic when importing files or using sync. The only scenario where it’s not automatic is if a database directory is copied manually or an import is done manually using Gramps command line. This is anyway not recommended, it just happens to be like that in the reset script of the demo. You’re overthinking this…