🌳 Trees Management Guide for LineagePress
The Trees section (accessible via WordPress Admin → LineagePress → Trees) is the organizational core of LineagePress, allowing administrators to create, manage, and separate distinct family lineages or genealogical datasets.
1. Overview and Core Concept
A Tree is the top-level container for your data. Each tree is completely separate and contains its own: Individuals, Families, Events, Sources, Media, and Notes.
License Limitations
| Version | Tree Limit |
| Free Version | Limited to 1 Tree. You must delete an existing tree to create a new one. |
| Pro Version | Unlimited trees. |
2. Browse Trees Tab
This area provides a master list and tools for bulk management.
Tree List Table
Displays key metrics and information for all existing trees:
- Tree ID: The unique, permanent identifier (Click to edit the tree).
- Tree Name: The display name.
- People/Families: Real-time record counts.
- Last Import: Date of the most recent GEDCOM file upload.
- Created: Tree creation date.
Bulk Actions
| Action | Effect | Use Case |
| Delete Selected | Permanently removes the selected tree definitions AND all their associated data (individuals, families, events, etc.). Cannot be undone. | Completely removing multiple test or unwanted trees. |
| Clear Selected | Removes all genealogy data from the selected trees, but keeps the tree definitions (ID, name, owner). Cannot be undone. | Preparing multiple trees for re-importing fresh data. |
3. Add Tree Tab
Creating a new tree requires two core fields:
- Tree ID (Required): A unique identifier (letters, numbers, underscores, hyphens only). It cannot be changed after creation and is used in the database and plugin logic. Example:
smith_family - Tree Name (Required): The display name shown to users. It can be changed later. Example: “Smith Family Tree”
Optional fields include a descriptive text, and contact information for the Tree Owner.
4. Edit Tree Tab
Select a tree ID from the Browse tab to access this area.
- Tree Statistics Card: Displays real-time record counts specific to the selected tree (People, Families, Events, Media, etc.).
- GEDCOM Information: Shows metadata from the original import file (Version, Source software, Encoding, etc.).
- Edit Form: Allows modification of the Tree Name and optional owner fields. The Tree ID is read-only.
Dangerous Actions Section
⚠️ Warning: These actions are permanent and cannot be undone.
| Action | Effect | Use Case |
| Clear Tree Data | Deletes all individuals, families, events, sources, and media within the tree. The Tree Definition (ID, Name) remains intact. | To start over with a fresh GEDCOM import for the same tree ID. |
| Delete Tree | Permanently removes the tree definition AND all its data. The Tree ID is freed up for reuse. | Completely removing a research or test tree from the system. |
Best Practices
| Area | Recommendation |
| Tree ID Naming | Use descriptive, unique IDs (e.g., jones_ancestors). Avoid spaces, special characters, and generic names. |
| Organization | Use a Single Tree Approach for highly interconnected families; use Multiple Tree Approach for distinct, unrelated family lines or separate research projects. |
| Before Deleting | Always Export a GEDCOM backup and download any associated media files before clearing or deleting a tree. |
| After Import | Verify Tree Statistics and check the frontend display to ensure the import was successful. |