# Gramps Web & Gramps 6.0 **URL:** \ **Category:** Gramps Web\ **Created:** [February 15, 2025, 9:50am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007 "2025-02-15T09:50:53Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [February 15, 2025, 9:50am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/1 "2025-02-15T09:50:53Z")
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: > **[Gramps 6.0 upgrade guide - Gramps Web](https://www.grampsweb.org/install_setup/v3/)** > > Open Source Genealogy Obviously, any help on beta testing the new Gramps Web is welcome - I’ll post here once it’s ready for testing. ---
**Author:** ![hdholm](https://avatars.discourse-cdn.com/v4/letter/h/76d3ee/32.png) [@hdholm](https://gramps.discourse.group/u/hdholm)\ **Post date:** [April 20, 2025, 4:01pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/4 "2025-04-20T16:01:07Z")
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](https://github.com/gramps-project/gramps/pull/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](https://www.grampsweb.org/install_setup/v3/#overview-of-the-release-status) 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? ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [April 20, 2025, 4:27pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/5 "2025-04-20T16:27:57Z")
> [@hdholm](#): > > I see [Gramps #2029](https://github.com/gramps-project/gramps/pull/2029) got merged, but I don’t see it in the release notes for 6.0.1 This PR references this issue: [0013721](https://gramps-project.org/bugs/view.php?id=13721): Missing metadata when Gramps crashes before a new database is closed That is the following bullet item in the [6.0.1 Release](https://github.com/gramps-project/gramps/releases/tag/v6.0.1) notes and [6.0.1 Change Log](https://gramps-project.org/bugs/changelog_page.php?version_id=123) > - Avoid empty metadata fields. Fixes [#13721](https://gramps-project.org/bugs/view.php?id=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](https://www.grampsweb.org/install_setup/v3/#overview-of-the-release-status) should be redesignated as a 6.1 upgrade guide? ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [April 20, 2025, 4:44pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/6 "2025-04-20T16:44:39Z")
> [@emyoulation](#): > > That means that Gramps Web is probably _ **never** _ going to be 6.0 compatible. So maybe the [Gramps 6.0 upgrade guide - Gramps Web](https://www.grampsweb.org/install_setup/v3/#overview-of-the-release-status) should be redesignated as a 6.1 upgrade guide? No, that’s not correct. The sub-issues of [this issue](https://github.com/gramps-project/gramps-web-api/issues/596) track what still needs to be done. Adding a link to the upgrade documentation is not a bad idea. ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [April 25, 2025, 1:55pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/7 "2025-04-25T13:55:59Z")
New thread: [Gramps Web & Gramps 6.0: Beta Testers Wanted](https://gramps.discourse.group/t/gramps-web-gramps-6-0-beta-testers-wanted/7523) ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [May 4, 2025, 12:26pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/8 "2025-05-04T12:26:11Z")
[Gramps Web API 3.0](https://github.com/gramps-project/gramps-web-api/releases/tag/v3.0.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. ---
**Author:** ![ahs3](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/ahs3/32/4195_2.png) [@ahs3](https://gramps.discourse.group/u/ahs3)\ **Post date:** [May 4, 2025, 6:10pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/9 "2025-05-04T18:10:43Z")
Hooray! Thanks, David! ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [May 19, 2025, 9:05pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/10 "2025-05-19T21:05:55Z")
> [@DavidMStraub](#): > > [Gramps Web API 3.0](https://github.com/gramps-project/gramps-web-api/releases/tag/v3.0.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. Where are the current release version numbers for Gramps Web API and frontend maintained as a list? _updated:_ - Gramps Web frontend - [releases on GitHub](https://github.com/gramps-project/gramps-web/releases) - Gramps Web backend API - [releases on GitHub](https://github.com/gramps-project/gramps-web-api/releases) - Gramps 6.0 upgrade guide : [overview of the release status](https://www.grampsweb.org/install_setup/v3/#overview-of-the-release-status) 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](https://gramps-project.org/wiki/index.php/Download#Installing_Gramps_Web_for_online_collaboration) in the **Download** wiki page does not list version numbers. There is no [version template](https://gramps-project.org/wiki/index.php/Category:Versions) for Gramps Web either. From **System Information** tab in [settings](https://demo.grampsweb.org/settings) on the [demo.GrampsWeb.org](http://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 ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [May 20, 2025, 6:27am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/11 "2025-05-20T06:27:25Z")
Unfortunately it looks like the demo site stopped auto-updating, will fix it tonight. ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [May 20, 2025, 10:28am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/12 "2025-05-20T10:28:49Z")
> [@DavidMStraub](#): > > the demo site stopped auto-updating 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. ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [May 20, 2025, 11:07am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/13 "2025-05-20T11:07:05Z")
The script is open source … > **[GitHub - DavidMStraub/gramps-web-demo-script](https://github.com/DavidMStraub/gramps-web-demo-script)** > > Trage zur Entwicklung von DavidMStraub/gramps-web-demo-script bei, indem du ein Konto bei GitHub erstellst. ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [May 30, 2025, 7:41pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/14 "2025-05-30T19:41:44Z")
> [@DavidMStraub](#): > > Unfortunately it looks like the demo site stopped auto-updating, will fix it tonight. From **System Information** tab in [settings](https://demo.grampsweb.org/settings) on the [demo.GrampsWeb.org](http://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. 1. 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. 2. The [admin settings page](https://demo.grampsweb.org/settings/administration) 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. ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [May 31, 2025, 9:43am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/15 "2025-05-31T09:43:03Z")
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. > ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [May 31, 2025, 3:18pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/16 "2025-05-31T15:18:56Z")
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](https://www.grampsweb.org/install_setup/v3/) 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. ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [May 31, 2025, 4:03pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/17 "2025-05-31T16:03:23Z")
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](https://gramps-project.org/wiki/index.php/Gramps_6.0_Wiki_Manual_-_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… ---
**Author:** ![TomGen](https://avatars.discourse-cdn.com/v4/letter/t/6a8cbe/32.png) [@TomGen](https://gramps.discourse.group/u/TomGen)\ **Post date:** [June 22, 2025, 3:15pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/18 "2025-06-22T15:15:08Z")
Hello David, just upgraded server and Desktop without any hassles - thank you very much for the great work! Tom ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [August 1, 2025, 2:38pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/19 "2025-08-01T14:38:48Z")
> [@DavidMStraub](#): > > 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](https://gramps-project.org/wiki/index.php/Gramps_6.0_Wiki_Manual_-_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… The demo site apparently resets at about 2am Berlin time and need to be re-indexed before it is usable again. Thanks for adding the highly visible indicator that the index needs rebuilding. It think it will help admins of Gramps Web. A question… can user-level-access visitors trigger a re-index if the alert appears? Or do they have to wait for an admin to notice? ![Screenshot_20250712_190323_Chrome](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/6/62a445e24e679c9f05a6ad6c3b3f984dfaa2c9ad.jpeg) However, could the script (that triggers the 2 am [Gramps Web demo](https://www.grampsweb.org/features/index.html#demo) site reset) include a re-index? ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [August 1, 2025, 3:06pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/20 "2025-08-01T15:06:56Z")
> [@emyoulation](#): > > A question… can user-level-access visitors trigger a re-index if the alert appears? Or do they have to wait for an admin to notice? They have to wait - non-owners cannot reindex. > However, could the script (that triggers the 2 am [Gramps Web demo](https://www.grampsweb.org/features/index.html#demo) site reset) include a re-index? It _should_ - so it needs debugging why it doesn’t… ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [August 1, 2025, 5:07pm UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/21 "2025-08-01T17:07:03Z")
> [@DavidMStraub](#): > > They have to wait - non-owners cannot reindex. If the admin doesn’t notice right away, that could be a problem. Is there an emergency alert feature where users (or visitors, for when the login/signup system is down) can send an urgent maintenance request to the admin(s)? Or… maybe that “needs to be rebuilt” notification could queue up a maintenance request if the visitor is not the owner? ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [August 3, 2025, 9:06am UTC](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007/22 "2025-08-03T09:06:24Z")
> [@emyoulation](#): > > Is there an emergency alert feature where users (or visitors, for when the login/signup system is down) can send an urgent maintenance request to the admin(s)? This is needed > > > Does Gramps Web need a new enhancement to comply with the DSA requirement requir…ement for online platforms sites to start making it easy to report illegal content on the platforms? > > > \> "Tobias Eigen, post:1, \[Discourse topic:294866\](https://meta.discourse.org/t/new-its-illegal-reason-when-flagging-posts/294866)" > \> The reason for this change is the upcoming 17 February, 2024 Digital Services Act (DSA) requirement for online platforms like Discourse sites to start making it easy to report illegal content on the platforms. [Next page](https://gramps.discourse.group/t/gramps-web-gramps-6-0/7007.md?page=2)