Step mother showing in web report individuals>ancestors as parent

I’m running Gramps 6.0.5 on server 2025.

For two step-children, their step-mother seems to be stuck showing as their mother when I export a web page and go to individuals>step-child>ancestors.

Their biological parents are set, and above the step-relationship under Relationships.

I’ve checked everything I can think to and found nothing that looks wrong.

As a test, I deleted both the step-family and then the step-mother, and the step-mother still shows instead of the biological mother when I re-generate the site

Can anyone suggest what I might be missing please?

Thanks in advance.

Two things to look at.

In the step-family record, are the relationships to the step-mother set at Birth or Stepchild?

The Child will have two sets of parent families. Is the Birth mother family listed as the first family? If not go to menu >> Edit >> Reorder. This is easily seen in the Relationships view.

Thanks.

The relationship with the step-mother’s set to step-child.
The biological/birth parents are the first family.

A few minutes after asking my question, I saw something that completely throws what I’ve been looking at.

The sites being exported into a folder that’s served by a copy of nginx.
I’ve just found that if I browse to it directly, the step-kids biological parents are shown just fine.

If I access it through Organizr (used as a ‘homepage’ for various services I have running on the machine) - the stopmother shows instead of the biological mother.

Clearing any caches involved hasn’t made any difference. I’ve no idea why it’s happening.

Changing Organizr from showing the gramps page within an iframe to opening it as an external page means it shows the biological mother OK.

To help in the advanced triage efforts, what are you using to build the web pages? If you are not using the Narrated Web what is the source used to build the pages; GEDCOM, XML or something else.

I’m using the Reports>Web pages>Narrated web site, in the Gramps app.

It’s creating the web page files, that nginx is then serving as domain/gramps

If I get at it using domain/gramps, all is good. Get at it within organizr and the biological mother swaps for the step mother. I haven’t seen anything else that looks wrong this way round, but havent checked everything.

Sorry but I’m not sure what you mean by the source to build the pages.

I’ve just found that when I changed File extension from .html to .php in the narrated web site options (and changed my nginx config to match), it displayed OK through organizr.

Changed it back to html and re-created the web page files again, and the step-mothers back.

I’m not sure why that makes the difference, but I’m cool with just having it set in a way that works.

Edit: I spoke too soon.

With it using .php, one of the two step-kids show the correct mother, but the other still shows the step-mother.

Since you are using the Narrative Web it uses the database directly. Using a gedcom or xml file would be information needed if you were using another program for web page creation.

Gotcha. It’s all within/coming from Gramps.

(cos we replied at similar times) I spoke too soon.

With it using .php, one of the two step-kids show the correct mother, but the other still shows the step-mother.

The 2nd step-kid was my fault, I had the order of the parents set wrong for them.

Using .php, everything seems OK.

The narrated website generates a webpage for each family.

You said that you deleted the stepmother and the Family where she was a spouse. Did you delete the destination folder that the Narrated Website used as the destination folder AND that ftp destination folder on the server? BEFORE generating the new report?

Just as a guess, you just regenerated the report into the same destination without clearing it. And that left the outdated webpages related to the (now deleted in Gramps) stepfamily. (The page filenaming is based on the FamilyID.)

If you had updated that family instead deleting it, the Narrated Web Report would have just overwritten the outdated page.

And you said that you flushed “any caches involved”. Just to be explicit, besides browser caches, you cleared the server caches (including Organizr and whatever caching tool your hosting service uses to “intelligently” reduce load serving dynamic content and bot traffic), right?

I tried updating the step family before I tried deleting it and the stepmother. I deleted them as a last resort tbh.

I’d removed the family and person, removed all web site files previously generated by Gramps, and generated them fresh, then restarted nginx.

The new web site files can’t have still included the stepmother (and she wasn’t showing when accessing domain/gramps)

The only cache I know is involved is my browser. Afaik organizr doesn’t cache anything… but what I’ve seen suggests otherwise, at least when using .html

Nginx is my own install on my own machine, same install that’s serving both gramps and organizr, so theres no host smarts involved.

Try this experiment. Load the html page that shows the stepfamily. Copy the URL and paste it here. (You can change the domain portion to anonimize a bit.) We need to understand the path and filename.

This should identify the Family ID in the URL.

Create a dummy family with that Family ID (John 1Smith and Mary 2Jones as safe placeholders. You aren’t going to have any other surnames with numbers.)

Generate a new Narrated Web Report. See if that overwrote the stepfamily.

When loaded through an iframe in organizr (as when I was having the problem), you dont see the full URL. It just shows domain/#gramps whichever tab/page I navigate to.

Then right-click the link to the problematic page. You should be able to copy (or share) the link.

If not, there won’t be much where we can help. It almost certainly sounds like Organizr is caching content if it is also hiding addresses.

I get the same link to the step family before and after replacing it:

https://domain.com/gramps/fam/e/3/ee91075d9ac69ff2900d48be03e.html

The stepmother still shows when looking at the step-child through organizr. The new family shows just fine, and I see no mention of the step family other than when looking at the step kids.:man_shrugging:

I’m not sure exactly whats going on with .html through organizr, but .php seems to work a treat so I’m happy.

Thanks for your time

OK. I know you’re done and find the php an acceptable solution.

But you should able to be able to navigate to that html file path and manually flush the file. Both locally and on the server.

You needn’t respond. I’m just beating the dead horse a little more.

Is the .html through organizr using the same css files as the setup that displays correctly?

At least we know it is not a GRAMPS issue.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.