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
Bug: personal facts module #4853
Comments
Presumably, the same is true of events of relatives/associates. |
No, they are never merged with anything else, it's only the individual facts that get the others merged
I've made a simple fix in #4854, just add this line before the merge |
BTW maybe a good idea to merge into a more appropriate name ($all_facts?) Later, I've just realised the meaning of your original question, yes you're right content in any of the other collections will affect the outcome (senior moment) |
Has this been done or is it obsolete? |
The purpose of this text is simply to prevent a completely empty tab - which could be confusing.
We only show historic events that occur between the first and last personal event with a date. So there should never be historic events and no personal events. If this is happening, then it should be a separate bug report. |
If the historic facts module has content and is enabled and an individual has no personal facts recorded then the message "There are no facts for this individual." should be displayed.
This doesn't happen because the historic events are included in the personal facts collection.
See this commit
The text was updated successfully, but these errors were encountered: