Family Historian User Group

Hi, I started using the Living flag to help reduced the amount of information published as web output for living individuals (and those assumed still to be living) to just basic details. So far so good when I come to use FH to create simple web output such as indexes.

I use PhpGedView to display the contents of the ~.ged file and am very pleased with its web capabilities.

However I have discovered that the all flags are treated by PhpGedView as errors: I get the message 'Unrecognized GEDCOM Code: _FLGS'. (See http://morte.co.uk/phpgedview.html and search for George Henry)



The '_FLGS' field is definitely produced by FH.

There are two ways round to my way of thinking: strip out the '_FLGS' fields from an export version of the GEDCOM before uploading to the web site or configure PhpGEedView
(somehow) to ignore the '_FLGS' field (or strip it out at import).

The best way seems to be to get FH to produce a 'clean' GEDCOM to upload and I'd like to try that as an initial approach before resorting to other methods. Any ideas how?

Regards,
Ric

ID:3661

From memory you can teach phpgedview about extensions, which are with in the 5.5 standard as they are prefixed with an underline.

So you can either use the split tree helper to remove the flags and lists before exporting (on your web copy of your file), or teach gedview what to do. From memory there is a file to edit to add the additional field definitions, but I can't remember where as I moved to TNG a while ago.

OK, thanks Jane. That gives me two lines of approach. I think I'll post on the PGV forum to see if anyone there knows a work-around. If I find a solution I'll post it back here for the record.
Regards,
Ric

You should also be able to use the privacy.php in phpgedview to take account of the private or living flag, but again I have not done gedview for a while

I have some results for this issue.

First, everything can be configured from within PhpGedView (PGV), which means that the flags can continue to be used within FH for managing facts and other issues.

The fisrt option is to set PGV to ignore all errors. This has it's downside in that it is possible to miss any and all errors; the upside is that all users are presented with a clean display.

Unfortunately it does not seem possible to ignore just the one error (in this case the rror casued by the unrecognised '_FLGS' Code).

The sequence is:

Admin --> Manage GEDCOMs and edit Privacy --> Configuration file --> Edit --> Display and Layout (+) --> Hide and Show --> Hide GEDCOM errors = Yes

The result looks like this:



The alternative is to define the user flag. The following example defines the '_FLGS' field as a 'Custom Flag':

Create a file phpgedview/languages/extra.en.php containing the following:



The result looks like this:



For me it is quite unnecessary to show these flags so the first option is the one for me.

Hope this might be useful to any others using custom fields and flags.

Regards,
Ric

PS: thanks to fisharebest at the PGV forum for pointing these options out to me.

I think a better option might be to use the split file helper, as suggested by Jane, to remove the flags before uploading to PhpGedView. This is a very quick step (but make sure you are working on a copy!)

This would mean you could still find other errors on PhpGedView but you would not need to define (or show) the custom flags either.

Hi Adrian,
Thanks for your reply. Yes, I had passed over Jane's suggestion to split simply because I have never used this facility and believed it sounded way too complex.

In fact the simplest procedure is to Export by query to exclude all private flags then in the export file to remove all flags using the checkbox at the bottom.

You are right about 'Ignore all errors'. I had hoped PGV might have a list of fields I could set to ignore but it does not. Not 'ignoring errors' is very useful because it shows up problems which otherwise I might never be aware of.

Thanks all of you for your help.
Regards,
Ric