* Export to TNG

[laz_gen]

A question for Mike regarding his plugins.

I make use of your excellent plugins "Clean Living Individuals" and "Export Gedcom" to prepare my data for my TNG website and have just noticed I now have a few "ToDo" custom facts showing online. These are ToDo facts I created to help me keep track of things within FH that don't add much value to the website and may serve to confuse. Further, one day I may inadvertently enter something "private" into a FH ToDo event and find it online later.

Is there an easy way to remove a single custom fact such as this ToDo fact from my export process before they reach the website?

One last question.

There are a great many options within your Export plugin that need to be set for my exact requirements and my method at present has been to record screenshots to ensure I have all options set consistently. Is there a method of saving these options as a personal config file that I can later load. If not, perhaps this is something you could consider for a future enhancement as I see you do have a "Reset Defaults" button so may be half way to providing that facility already.

[tatewise]

I imagine you follow a process similar to that described in how_to:exporting_gedcom_with_multimedia#export_to_website_without_sensitive_data|> Export to Website Without Sensitive Data.

So you use the Export > GEDCOM File Command and Clean Living Persons Plugin and Export Gedcom File Plugin.
Between those last two is File > Split Tree Helper Command which is the easiest way to delete specific Facts.
Actually, the Export Gedcom File Plugin Help & Advice page makes the same recommendation.

The Export Gedcom File Plugin already does try to save your customised option settings.
The options for each Project or exported GEDCOM Filename and GEDCOM Export Mode are saved separately as stated in the plugins:help:export_gedcom_file:basic_options|> Export Gedcom File ~ Basic Options.
So you should not usually need to re-enter the option settings.
However, in the case of an exported GEDCOM Filename you must use the same Filename each time you export to TNG.
If you are using different Projects and GEDCOM Filenames then the saved options data will not be found.
But you can preserve that by understanding where the options data file is saved.
For example, assume you export your GEDCOM to the Public folder of the Project and use a Filename of say Transfer.
Then that GEDCOM will exists in ...\Public\Transfer.ged and the Plugin options will be in:
...\Public\Transfer.fh_data\Plugin Data\Export Gedcom File.dat
Clearly, if you use a different GEDCOM Filename then the Plugin will not find that options data file.
So rename that Transfer.fh_data folder name or otherwise create a copy of that structure before the export process and the Plugin options should be maintained.

[laz_gen]

Yes following the normal procedure for excluding facts for living individuals etc. before export.

I had not yet explored the Split Tree Helper feature. Just had a look and can see how I can select just that fact and have it removed from the exported gedcom, (not the live working gedcom). I have deleted my ToDo entries manually this time from the website but will have a go with the Split Tree Helper next time.

As for my use of your export plugin yes I have been renaming my saved files adding a date into the filename so unaware of the plugin feature to save the config for me. I will experiment with keeping the same export filename next time to see the difference.

Thanks for your advice.

[tatewise]

So you will probably have a series of ...\Public\<ExportGedcom>.fh_data\Plugin Data\Export Gedcom File.dat structures.
Where <ExportGedcom> is the dated filename of each exported GEDCOM file.
Those folder structures can all be deleted, along with the associated GEDCOM file (that you may already have deleted).

FYI:
Usually Plugins like Export Gedcom File save their settings in the Project's Plugin Data subfolder that sits alongside the Media folder and GEDCOM file.
But for standalone GEDCOM files they instead create a dummy ...\<ExportGedcom>.fh_data\Plugin Data\... structure alongside the GEDCOM file to mimic the Project structure.