[Plugin: rootsPersona] New genealogy plugin

Notice the /.xml at the end – it should be soemthing like i403.xml.

Is this happenign for all persons, or just some?

Somehow it looke slike they ar emissing an ID.

It only seems to be happening on some. Actually one at the moment which is pretty near the top of the tree – around 1218 – parents showing as unknown.
It was happening to more entries before so I deleted everything, including the rootspersona directory (which is not deleted automatically when deinstalling and nor are the pages by the way) as well as all the pages before reinstalling completely. Now I am trying to add one page at a time to see if I can get any more to break.

Just had another one come up:
Warning: XSLTProcessor::transformToXml() [xsltprocessor.transformtoxml]: I/O warning : failed to load external entity “/kunden/267559_78609/webseiten/engelking/wp-content/rootsPersonaData/.xml” in /kunden/267559_78609/webseiten/engelking/wp-content/plugins/rootspersona/php/personUtility.php on line 579.
This person does have ancestors

Not deleting teh rootswersonaData directory automatically was intentional. The same with not deleting the pages (though I may add a utility to do that, sicne there are so many pages generated).

I didn’t want the plugin blowing away the data if a perons deactivated unintentionally.

However, if you had so much trouble withthe older version, you might WANT to do that, then reinstall.

For the case above, edit the page and look at the shortcode – if the personId is empty in the shortcode, that would explain the behavior.

I guessed that would be the reason for not deleting automatically but an option would be neat.
The person id is there:
[rootsPersona personId=’i937’/]

Hmmm.

Can you tell me if there is an entry in idMap.xml for i937? And is there an i937.xml file? (both in rootsPersona)

>>but an option would be neat.

yeah, I’m tryng to figure out how to have a popup during teh activate/deactivate process, but not sure WP gives you a hook for that.

in rootspersonadata there is an i937.xml file in in the directory a file idMap.xml

Is it also intentional that one cannot edit the name field of a person?

>> Is it also intentional that one cannot edit the name field of a person?

For now.

The current implementation assumes that the GEDCOM is the system of record. That means the [plugin doesn’t ‘own’ the data, it just dislays it. Any changes have to be made to the gedcom (or in the source program that generates the gedcom).

Anytime the gedcom is reloaded, it would overwrite any changes to name if it was allowed.

The plugin is more a display tool than a full fledged geanealogy program – others are better at writing those than I. That doesn’t mean I won’t be adding maintenanince and data gathering func tionality, just that its not top of the list right now.

That seem a fair enough concept. When reimporting a file, how does it know whether to overwrite or add persons?

Based on the ID. The ID has to remain the same. Most gen programs handle that fine.

>>Warning: XSLTProcessor::transformToXml() [xsltprocessor.transformtoxml]: I/O warning : failed to load external entity

I just recrated that with a sample file I loaded off the web. Will get back to you with an update.

Thanks Ed. I know all this is a lot of programming effort but I think you are on to a good plugin here.
I will not plague you with the wish list at this stage. Important is to get all the basics stable.

Wish list is fine! In fact, I started a forum over at ed4becky.net to collect them! Suggest away!

Why am I coding instead of researching my roots? Actually I am waiting from a letter from Boston that MIGHT close a missing link. So while I wait, I code.

I have fixed the issue we discussed – it will be in the next upgrade. The condition was person with no FAMC entry in the gedcom, so generally it hits first person in a branch.

I am actually a council member of the Sack’sche Family Foundation in Germany and we have the biggest forward running data bank in the world with some 17,500 entries. But I only want to take a small piece out for my branch of the family so your tool looks like a good approach because it can easily be updated.
What would be very useful would be some kind of display switch to hide any living members. Doing this manually is hard work. The data protection laws here are really strict.
I hope you find your missing link.

That would be an easy edition IF I knew how to define ‘living’. Thoughts?

(Also, do you have interest in helping me internationalize this, for example, by supplying a german language file? If so, I’ll see what it would take on my end.)