You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The functionality "copy/paste mechanism for source citations in the individual and family view" requires the 'Hit counters' footer module to be enabled (additionally, the tree preference "Hit counters" must be set to "show"), otherwise the copy icon isn't displayed.
This is caused by checking specific session parameters, here and a few lines later. These session parameters are only set in the 'Hit counters' footer module, here.
The easiest way to remove this dependency is probably to duplicate these Session parameters under different names and set them within the custom module.
The text was updated successfully, but these errors were encountered:
Thank you for this important hint to the dependency.
The background is that I was facing difficulties to get the context of a fact's gedcom to be shown with "fact-gedcom-fields.phtml". In fact-gedcom-fields.phtml, only the Gedcom and the parent tags are handed over and it is not known to which individual or family they belong. The mentioned session parameters are a nice workaround to get this context information, but I agree that there should not be a dependency.
At the moment, I do not know how to solve this. I will check the 'Hit counters' footer module and try to learn how it sets the session variables. Maybe, I can use a simular approach.
The functionality "copy/paste mechanism for source citations in the individual and family view" requires the 'Hit counters' footer module to be enabled (additionally, the tree preference "Hit counters" must be set to "show"), otherwise the copy icon isn't displayed.
This is caused by checking specific session parameters, here and a few lines later. These session parameters are only set in the 'Hit counters' footer module, here.
The easiest way to remove this dependency is probably to duplicate these Session parameters under different names and set them within the custom module.
The text was updated successfully, but these errors were encountered: