Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pedigree tree module base individual is not connected to its family tree #4051

Closed
ardhtu opened this issue Sep 28, 2021 · 2 comments
Closed

Comments

@ardhtu
Copy link

ardhtu commented Sep 28, 2021

I have two family trees in my webtrees installation.
I have set up a pedigree tree module in in front pages of of both family trees. There is only one parameter to set up the module, the base person. When I change the base person in one tree's module also the other tree's base person in that module changes probably to the same index number.
It looks like the base person for that module is not saved into the database with information into which tree it belongs to.

  • Hannu
@fisharebest
Copy link
Owner

I have set up a pedigree tree module in in front pages of of both family trees.

You have added it to your "user" home page - not to the "tree" home pages.

If you add it to the trees's home pages, then you will have two copies of the block, and two copies of the configuration settings.

I guess this block should not be allowed on "user" pages.

@JustCarmen
Copy link
Contributor

JustCarmen commented Dec 30, 2021

I guess this block should not be allowed on "user" pages.

I don't agree. As the "user" page is the starting point for each member of a tree (they are redirected to that page after login and not redirected to the homepage), I think this block certainly belongs there, because it is the only block on the page that give them a quick insight in the connections between individuals and is very handy for newbies who can get lost easily in the jumble of data on a webtrees website.

Why not make a distinction in the database between userpage blocks and tree blocks? I hope you would reconsider this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants