Author: Tom Holden

Updating to WordPress 5.4.1

I’m going to attempt an update from WordPress 4.9.14 to 5.4.1 sometime today. The disruption will either be minimal or disastrous. I’ve made a backup of the files and database. But I’m no WP expert and things may get broken. I think all the plugins have been tested to the higher level. Wish me luck!

Aargh! Systemic Error re: GroupID

I’ve just discovered that I caused a systemic error in several scripts dealing with Groups in relating the LabelTable.LabelID to the GroupTable.GroupID when the latter is actually related to LabelTable.LabelValue. It’s of no consequence when groups are consecutively created but not deleted because the LabelID and LabelValue match. The problem arises when a group before…

Read the full article

Backup database open in both SQLite and RootsMagic #backup

Problem Neither the RootsMagic File>Backup nor File>Copy can proceed because the database file “is being used by another process” (RootsMagic’s own or your SQLite manager or other outboard SQLite connection). And if you’ve chosen Backup, RM gracelessly blocks you from further work with an always-on-top fake news message window “Creating backup file…” requiring closure of…

Read the full article

Updates responding to TreeShare

Working out the wrinkles in a new script addressing some TreeShare issues, I was using some other scripts to help me understand what was going on and ran into a couple of issues that I’ve fixed: RM7_5_WaymarksViews.sql was not reporting family events (e.g., Marriage) and that affected other views which relied on the EventWay view. DeletePhantoms3.sql did…

Read the full article

DAT File Question #ancestrycom #treeshare #database

I found some discrepancies in RootsMagic and posted a question. This was in an answer: C:Users\Tom\AppData\Roaming\RootsMagic\AMT (change the “Tom ” to your Windows username). In this folder is a .DAT file for each connected Ancestry Member Tree (AMT), named “AT-AncestryTreeID.DAT”, where AncestryTreeID is an integer. This file is a SQLite database containing tables named identically…

Read the full article

GEDCOM & DnD transfer losses #gedcom

Background RootsMagic Drag’n’Drop between the windows of two databases is a background GEDCOM export-import process. Both Drag’n’Drop and the explicit File>Export and Import process fail to fully transfer everything from one database to another. Drag’n’Drop and GEDCOM are governed by the settings for Export in Lists>Fact Type List so any fact type that is not…

Read the full article