6.0.0
Don’t know if I’m doing something wrong but when I add roles to a citation and then go to the citation tab, the event is shown but not the role or Name unless Principle is selected. Is there a way to have other roles and names show when look at references?
I don’t understand. Roles are for Events, not citations.
While 6.0 enhanced the References (Backlinks) tab to some degree, @SteveY has an array of enhancements for it in the works. You might want to patch your Gramps 6.0 to try it out.
Sorry was in hurry when writing that. What I meant is when I open the citations window and select references, it brings up all the events sharing that citation. For a census event, it shows the primary persons name, for all the rest it just says census with no name or role unless I make each family person a primary also.
This is a known problem in Gramps. You will see the same problem if you run a text report that lists events. If the role is not ‘Primary’ the event will not appear in the report (or ‘Family’ for events added to family records.
This is really silly, especially because the code contains two methods for creating event lists - one method that filters on ‘Primary’, and one method that will include all events.
To solve this you have two options - either change all event roles to ‘Primary’ (or ‘Family’ for family events), or you can do a hack in the code.
If you choose to hack look for a function called “get_primary_event_ref_list()” and change it to “get_event_ref_list()”.
There are 11 files that have that reference, do I need to make that change in all of them or a specific file?
When I drag and drop a Census record, the Role is changed to “unknown”, which I have to change each time. If the record was not the Primary for that person I would not be doing the D&D. I wish it would just make the copy without making any changes. The event then is flagged as Unknown in reports, however the report never shows Primary.
Strange behaviour.
You only need to hack the files, you use. If you never run text reports, then don’t touch them.
BUT BEFORE YOU DO ANY EDITING MAKE A BACKUP OF THE FILES
There might be unexpected side effects, so you want to be able to go back to the original.
Also be aware, that if you do these kinds of hacks, you must redo them if/when you update Gramps.
I changed everywhere in the code the recommendation you made and it didn’t work. Right now I’m using the role of Primary and adding the role as a description to get around it. Maybe someone will make a pull that fixes this sometime in the future.