DigitalPulse Family Archive

A free, open-source WordPress plugin for the stories, photographs and people that connect generations. Explore relatives in a responsive oak-inspired family tree, open a person in a detailed modal, and manage the archive through familiar WordPress posts.

Version 1.4.0 · WordPress 6.5+ · Tested up to WordPress 7.1 · PHP 7.4+ · GPL-3.0-or-later
Developed by Raivis Kalnins, web developer at DigitalPulse.
Project and support: DigitalPulse

Free plugin: all included features are available free of charge, with no paid plugin license or subscription required. Source code is included under GPL-3.0-or-later. Optional hCaptcha and Polylang integrations are documented separately and follow their providers' terms.

The package is prepared for free distribution through the WordPress.org Plugin Directory submission process. Directory publication remains subject to review. A reusable submission description and reviewer notes are included in docs/wordpress-org.md.

The screenshot contains fictional demonstration records and illustrated portraits. No private family records or photographs are included in this plugin.

What is new in 1.4.0

• WordPress.org review preparation. The public plugin identity is now DigitalPulse Family Archive, with the installable folder, main plugin file and text domain aligned to digitalpulse-family-archive.
• Safer rendered titles. The title-guard callback now escapes the translated replacement before returning content that WordPress may render.
• Cleaner WordPress administration. The optional demo editor no longer forces a top-level menu into position 2; it uses a normal plugin-area menu position instead.
• Directory translation workflow. Compiled and source gettext translation files are no longer bundled for WordPress.org distribution. The plugin remains internationalized and WordPress.org can provide community translation packages through translate.wordpress.org.
• Release metadata synchronized. The plugin header, stable tag and documentation identify version 1.4.0, requiring WordPress 6.5+ and PHP 7.4+, and declaring testing through WordPress 7.1.
• Existing data remains compatible. Person posts, relationships, settings, media, shortcodes, saved blocks and the existing internal wpmft_* identifiers are retained so the review-focused rename does not require a database migration.

Install the complete digitalpulse-family-archive-1.4.0.zip package through WordPress. When updating from an earlier digitalpulse-family-archive/ release, use Replace current with uploaded. When migrating from an older differently named plugin folder, follow the migration instructions below and do not keep both copies active.

Previous 1.2.8 improvements

• Portraits stay visible after refresh. Completed small images keep their loaded state when pages are cached or person panels reopen. Changing or removing a photograph also resets the correct image state.
• Missing thumbnails recover safely. The authenticated media endpoint can use a readable original when an ordinary display copy is missing. Private access and actual image MIME types remain enforced.
• Optimization continues past a problem photo. Each request prepares one photograph. Failed or busy attachments are reported by ID while later photographs can finish; partial completion is clearly distinguished from a fully successful run.
• Counts reflect the current archive. The settings screen reads the actual pending total after reload, without encoding images. Missing optimized files can be detected and rebuilt with Prepare existing family photographs.

Version 1.2.7 improvements

• Optional WhatsApp contacts. Add an administrator number in Contact settings and a separate number for each person. Buttons open WhatsApp only after a click, with no embedded chat script. Administrator contact is hidden during public demo sharing.
• A story for every photograph. Each selected gallery photo has its own description and flexible date, such as “Summer 1980”. Stories belong to that person’s gallery; a shared attachment’s captions on other pages remain independent.
• Smoother gallery loading. Responsive previews, lazy loading, reserved image space, restrained loading animation and error recovery make slow connections easier to use. The lightbox loads its current image and limits nearby preloading.
• Modern image formats. Automatic AVIF or WebP display copies use the server’s available WordPress image editor. Quality defaults to 82 and is adjustable from 60–92. Existing images can be prepared in small, pausable batches. Original files and animated formats are retained, and protected photographs continue through authenticated delivery.
• Children beneath their parents. Child groups align with recorded parents; a single child sits closer underneath where card and connector spacing permit. Current partners remain together without being treated as a child’s parent unless that relationship is recorded.
• A familiar demo editor. The demo uses the same details-first visual structure, with safe personal/contact/photo-story editing and a matching settings overview. Daily reset includes those fields. Demo setup appears for an empty first installation; later the Demo tab is enabled through General. An active demo always keeps its stop-sharing control available.

Configure the new options

In Family Tree → Contact & hCaptcha, enable the administrator WhatsApp button and enter a full international number with its country code. This optional administrator link is shown on the public sign-in screen as well as the unlocked tree. In a person’s Contact details, enter their WhatsApp number or leave it blank to hide the icon.

In a person’s Photo gallery, fill When / date and Photo story / description, then click Update. Unsaved stories remain with their photographs when you add or reorder images. These fields accept plain text, including approximate dates; they do not require invented calendar dates.

In Performance & cache, choose automatic image optimization, save the settings, and use Prepare existing family photographs for the existing archive. The screen reports which encoders are available. New person edits queue background preparation. Conversion is never performed while a visitor waits for a photo, and browsers retain ordinary image fallbacks. AVIF generation requires server support: WordPress AVIF documentation.

In General, enable Show the Demo tab for sample content and demo sharing when you need the optional Demo tab. Hiding the tools does not silently change active sharing or its daily reset. The public demo remains restricted to its owned sample records; site settings, relationships and media ownership are protected.

Version 1.2.6 improvements

• The saved gallery matches the frontend. Only the selected photographs appear, in their saved order. Removing every photograph keeps the gallery empty; old attachments do not reappear.
• A separate profile portrait. The portrait stays in the profile header and is included in a saved gallery only when selected there.
• Editable inherited and legacy galleries. The person editor shows the same effective photo list as the frontend. Saving a translated person's selection respects that selection without merging photographs back from another language.
• Private photographs remain protected. Media detection, viewing permissions and encryption still cover portraits and other referenced or attached images outside the visible gallery.

Version 1.2.5 improvements

• Gallery additions keep existing photographs. Use Add photographs to append images without replacing the current selection. Reorder photographs loads the complete gallery before opening the ordering dialog; cancellation or a loading failure leaves the gallery unchanged.
• A clearer portrait removal button. The secondary red button has matching spacing, a removal icon, a visible keyboard focus state and a mobile-friendly size. Removing a portrait keeps its original media attachment.
• Flags in the language switch. Local SVG flags and readable language names replace the outlined native select. The menu supports touch and keyboard navigation, preserves Polylang page links, and gives custom languages a neutral fallback icon.
• Person names in the dashboard. Posts are labeled Persons, All persons, Add person and Edit person, with Latvian equivalents. New-person links open the person form. Sites that also publish news can turn off person labels in the General settings.
• A fuller demo dashboard. Shared visitors can add, edit and remove demo persons and pages, open the public tree, and inspect a read-only overview of the main plugin settings. The daily reset restores the original samples and removes visitor-created records.

Version 1.2.4 improvements

• Current WordPress compatibility metadata. The directory readme declares Tested up to: 7.1, with verification performed against the official WordPress 7.1.3 release.
• Release consistency. The plugin header, stable tag, asset version, block metadata and translation catalog metadata identify version 1.2.4.
• Free distribution information. The descriptions, FAQ and submission notes explain that the complete plugin is free and open source under GPL-3.0-or-later.

Version 1.2.3 improvements

• Updated public name. The plugin is now DigitalPulse Family Archive, packaged in digitalpulse-family-archive/ with a matching translation domain and a digitalpulse-family-archive.php entry point. The new ZIP addresses the directory reviewer's name objection; acceptance and the final directory permalink remain subject to review.
• Existing archive compatibility. Family records, settings, shortcodes and saved blocks retain their existing identifiers. Follow the rename migration below once when updating from the old wp-my-family-tree folder.

Version 1.2.2 improvements

• Restored footer contact form. Contact us (Pieteikties in Latvian) opens the existing form for sending the family administrator a description and an optional photo. The same button is available to signed-out and signed-in visitors whenever contact is enabled.

Version 1.2.1 improvements

• Daily demo reset. Shared demo content returns to its saved starting state every 24 hours. The plugin handles scheduling and recovery without a backup plugin.
• Clearer family connections. Tree connectors and relationship highlighting make dense family views easier to follow.
• A tighter footer. The optional developer credit sits directly below the left-hand motto. Email, the contact-form button and device installation controls remain together.

Version 1.2.0 improvements

• Swipe through person galleries. Touch gestures move between photographs, with arrows, keyboard controls, larger dot targets and zoom retained. Vertical scrolling and panning a zoomed photograph do not change slides.
• A fullscreen tree. Expand just the tree panel, exit with the close button or Escape, and keep person details usable inside fullscreen. Browsers without element fullscreen use an in-page alternative. PNG exports and printing contain only the selected tree branch, without the site header or contact footer.
• Edit in a new tab. Authorized editors can open a person's editor while keeping their place in the tree.
• Object-cache support and a toolbar tool. Choose automatic, WordPress-transient or persistent object-cache storage. Administrators can clear only the Family Tree cache from the WordPress toolbar; the clean icon rotates while the request runs.
• Fourteen language presets and custom languages. English is the default for new installations. Add or edit any number of interface languages in settings, with optional Polylang content translations and English fallback for untranslated labels.
• An optional realistic heritage-family demo. Import eight fictional Morgan-family records, public-domain archival photographs and two English pages after confirmation. Existing content is preserved. A separate, explicitly enabled demo-sharing mode provides a restricted sample editor and a front-end demo password only when no real family records exist.
• A compact footer. Email is a mail button beside the contact form and optional Android / iPhone installation controls, with a mobile layout and an optional credit beneath the motto.
• Public distribution documentation. A WordPress.org-format readme, external-service disclosures, readable source, build instructions and review notes are included.

The existing private-media, contact-photo, relationship-status, mobile tree-gesture and performance-cleanup features are retained.

Features at a glance

Area	Included
Tree	Fluid oak layout, leaf portraits, pan, zoom, relative navigation, search and people directory
Person modal	Portrait, biography, dates, places, relationships, contact information, social links and gallery lightbox
WordPress content	Ordinary posts for people; a Family Tree block and [wp_my_family_tree] shortcode for the page
Theme integration	Optional full-window page with its own H1, header and contact footer; embedded mode for a theme layout
Languages	Fourteen bundled frontend interfaces, unlimited custom languages, editable labels, English fallback and optional Polylang page/content translations
Privacy	Optional family password, remembered viewing access up to 30 days, server access checks and no-store responses
Photographs	Top-aligned portraits and optional encrypted family-media delivery
Contact	Independent recipient settings, optional hCaptcha, private single-photo attachment and WordPress mail delivery
Installation	Oak favicon, Apple touch icon, web-app manifest and Android / Apple footer help
Sharing	Fullscreen tree panel, tree-only PNG export and printing
Performance	Server-side relationship index, optional persistent object cache, scoped animated toolbar clearing, minified assets, full-window HTML compaction and configurable WordPress cleanup
Demo	Additive fictional content import and an isolated, restricted shared editor available only after administrator opt-in

Update an existing installation

Update DigitalPulse Family Archive 1.2.3 or later

Back up the site, upload the complete digitalpulse-family-archive-1.4.0.zip through Plugins → Add New Plugin → Upload Plugin, and choose Replace current with uploaded. Keep the digitalpulse-family-archive/ folder name, then verify the tree page, photographs and contact form. Existing data and settings are retained.

Migrate from WP DigitalPulse Family Archive 1.2.2 or earlier

The package now uses digitalpulse-family-archive/. WordPress treats this folder as a separate plugin; uploading it does not replace the old wp-my-family-tree/ copy.

1. Back up the site's database and uploads together. If the archive contains private published content, enable independent site access protection for the switch because deactivating the old plugin stops its access checks.
2. Open Plugins and deactivate WP DigitalPulse Family Archive. If it is network-active, deactivate it in Network Admin first.
3. Open Plugins → Add New Plugin → Upload Plugin, select the complete digitalpulse-family-archive-1.4.0.zip, and click Install Now.
4. Activate DigitalPulse Family Archive. Keep the old copy inactive; the new entry point blocks activation while the previous copy is active.
5. Open the tree page and verify the privacy gate, photographs, person editor and Contact us / Pieteikties form. Review Family Tree → Settings & help, then clear the Family Tree cache and any applicable page cache.
6. After verifying the new version, delete the inactive WP DigitalPulse Family Archive copy from the Plugins screen. Its bundled code has no uninstall data-deletion routine. Leave DigitalPulse Family Archive active.

Your person posts, relationships, uploaded photographs, stored password, settings and media-encryption key remain in the site's existing data. Existing [wp_my_family_tree], [family-tree] and [family-members] shortcodes and saved wp-digitalpulse-family-archive/tree blocks remain valid. No database import, theme replacement or backup restore is required.

Deactivating the old plugin revokes the public demo account and sessions. On an isolated demonstration site, explicitly enable shared demo mode again if needed. Imported samples and the saved reset baseline are retained.

Later updates to DigitalPulse Family Archive

Once installed in digitalpulse-family-archive/, subsequent complete packages using that same folder can use WordPress's Replace current with uploaded option. Use the complete installable ZIP; a package containing only changed files is not suitable for the WordPress plugin uploader. Keep your usual site backup before updating, particularly when the site uses encrypted photographs.

First-time setup

1. Install and activate DigitalPulse Family Archive.
2. If the original WP Family Tree plugin is active, deactivate it to avoid competing shortcodes and older public endpoints. Retain its people and media.
3. Open Family Tree → Settings & help. Select the category containing family posts and choose a starting person.
4. Use Create a tree page, or put the Family Tree block / shortcode on an existing page and select it as the tree page.
5. Under Privacy & access, set a family password, or deliberately switch password protection off for a public tree. New private installations remain locked until a password is configured.
6. Under Appearance, set the title, introduction, colours and optional installation controls. Use Languages for translated titles and interface labels.
7. Under Contact & hCaptcha, enter the family administrator's name and recipient email address. Review photo uploads and optional hCaptcha.
8. Open the page in a signed-out browser window to check the visitor experience.

The original WP Family Tree category is detected when available. Existing father, mother, spouse, born, died and gender metadata are reused; people do not have to be moved to another post type or assigned new IDs.

Block and shortcodes

Insert the Family Tree block on a WordPress page. Its starting-person option accepts the person's post ID. The equivalent shortcodes are:

[wp_my_family_tree]
[wp_my_family_tree root="123"]
[wp_my_family_tree view="list"]

Legacy [family-tree] and [family-members] shortcodes are supported for migration. A configured starting person removes the need for a name-based legacy shortcode.

Full-window mode supplies the tree page's complete layout, including its H1, header and footer, independently of the theme. Turn that setting off to place the tree inside the active theme's normal page. The page block remains available even when Gutenberg is disabled for person records.

Move around the tree

On a phone or tablet, swipe anywhere inside the tree, including a portrait, name or branch button, to move it. Tap a person without dragging to open their details, or tap the branch button to explore their relatives. Pinch with two fingers to zoom; lifting one finger lets the remaining finger continue moving the tree. Scroll outside the tree area to move down the page.

On a computer, drag the tree or use the on-screen zoom and fit controls. With the tree area focused, arrow keys move it, + / − zoom and Home fits the tree. The person and branch buttons remain keyboard accessible.

Add and edit people

Use Persons → Add person, Family Tree → Settings & help → Add a person, or edit an existing family record. The title is the person's full name. The Persons menu uses ordinary WordPress posts internally, so existing records, IDs, categories and links are retained. Turn off person labels in Family Tree → Settings & help → General to restore the usual Posts menu on a site that also publishes news.

With the default editor setting, the person form appears immediately below the title. It includes:

• A portrait chooser using the post's featured image.
• Gender, birth and death dates, birth / maiden name, birthplace, place of death, location and occupation.
• Father / parent 1, mother / parent 2, primary and additional partners, and explicit partner statuses.
• Email, telephone, mobile phone, postal address and website.
• Facebook, Instagram, LinkedIn, X / Twitter, YouTube and TikTok profile URLs.
• Separate Add photographs and Reorder photographs controls.

The biography editor follows the form. Save or publish the WordPress post to save its details. The plugin retains an existing biography, including its block markup, when you only change person fields. If you edit the biography itself in the classic editor, it is saved using that editor's normal behaviour.

For a block-based biography workflow, enable General → Enable the WordPress block editor for family people. The person fields then appear as a metabox in the block editor. This setting does not change the editor used by unrelated posts or pages.

Dates, contact details and photographs

Dates accept YYYY, YYYY-MM or YYYY-MM-DD. Leave the date of death blank for a living person. Existing legacy date text remains intact unless it is changed. Birth dates of living people can be hidden under Privacy & access.

Use full https:// or http:// URLs for websites and social profiles. Contact details are visible to everyone who can view the tree, including public visitors when password protection is off. Add details with the person's agreement. Empty fields do not produce empty contact cards in the modal.

Portraits and gallery previews align to the top of the available photograph. The lightbox shows the full image. If the original file was already cropped, upload an uncropped source to restore the missing area. Removing a photograph from a gallery removes its gallery reference; it does not delete the original media file.

Add photographs appends selected images to the existing gallery and ignores duplicates. Use Reorder photographs to change the order or remove items in the gallery dialog, or use the remove button on a preview. Cancelling a dialog keeps the current gallery. Save or update the person after making changes.

The saved selection controls the frontend gallery, including an empty selection. The profile portrait is separate unless selected in the gallery. If an older person has never had an explicit gallery saved, the editor displays the imported or inherited photographs currently used by the frontend; remove unwanted previews and update the person to save the desired list. A translated person's saved selection takes precedence over an inherited gallery. Removing gallery entries retains the media files and their existing privacy protection.

Current and former partners

In Partner relationships, select the other person and choose Together, Divorced, Separated or Former partner. Use Together for a current partner. The paired-rings icon means a current relationship and does not assume marriage.

Recorded relationship	Tree behaviour
Together	Current partner appears beside the selected person, with paired rings
Divorced / separated / former	Former partner is excluded from the selected person's partner branch
Shared child after separation	Selecting that child still shows both recorded parents and their parent-to-child lines
Shared child without an explicit status	Parents remain neutral co-parents; no current-partner rings are inferred
New current partner	Does not become a child's parent unless explicitly selected in that child's parent fields

A status recorded on either person applies to the pair. Saving one person does not silently edit the other person's post. If both records contain conflicting explicit statuses, a former status takes precedence; review both records and make them agree. Legacy spouse links without an explicit current status remain neutral.

Edit from a person modal

A WordPress user who can edit the displayed person sees a small Edit button in the modal. It opens the appropriate post editor in a new browser tab and preserves the selected plugin language. A shared family password only grants viewing access; it does not grant editing permissions or expose an edit link.

Interface languages and optional Polylang

New installations start in English. Existing installations retain their saved language. The Languages tab includes these ready-to-use frontend presets:

Language	Code	Language	Code
English	en	Latvian	lv
Spanish	es	Lithuanian	lt
Polish	pl	Estonian	et
French	fr	Danish	da
German	de	Swedish	sv
Norwegian Bokmål	nb	Norwegian Nynorsk	nn
Finnish	fi	Icelandic	is

Enable the languages you want, select the default, and save. The public language menu scales to the configured languages rather than displaying a fixed pair of buttons. Dates and numbers use the selected locale. English remains available as the fallback.

Use Add language to add a unique language code, name and locale. There is no fixed limit on the number of languages. Supply frontend translations as a JSON object whose keys match languages/interfaces/en.json → frontend; supply administrator labels as a JSON object mapping the original English text to its translation. A partial dictionary is valid: missing labels fall back to English. Preserve placeholders such as {name}, {count} and {days}. Per-language titles and subtitles can also be configured.

For example, a custom frontend override can contain:

{"tree":"Our family connections","contact":"Write to the archive"}

The bundled frontend dictionaries contain the complete interface key set. Administrator translation coverage varies: Latvian includes the existing detailed catalog, while the other presets include common controls and use English for remaining labels. All administrator labels can be overridden or translated further. The WordPress dashboard, theme and core editor use their own language settings.

Translate pages and biographies with Polylang

Polylang is optional. When it is absent, the Languages panel links to its free WordPress.org installation screen; no additional plugin is installed automatically. The family tree and its interface language menu work without it.

1. Install and activate Polylang if you want translated WordPress content.
2. Configure your content languages in Polylang.
3. Create a tree page in each language, insert the same block or shortcode, and connect the pages as translations.
4. Add translations of person posts where needed. Names and biographies remain exactly as entered; this plugin does not machine-translate them or duplicate people.
5. Keep the plugin language switch enabled. With configured Polylang languages, it follows translated page URLs so the theme and tree use the same page language.

A published linked person translation is used when available, with the original record as fallback. Relationship and contact metadata synchronization is described in wpml-config.xml. An old wpmft_lang query parameter does not override Polylang's current page language.

The visitor access/session setup is designed for one site origin. Separate Polylang domains or subdomains require independent access and hosting configuration and are not covered by this release's verified setup.

Plugin labels in the dashboard

The Plugin interface language control changes this plugin's labels without replacing unsaved form values. Person-form labels can follow the person's Polylang language. To change the entire WordPress dashboard, choose the user's WordPress language and install its language pack separately. Changing the content language in the block editor may trigger Polylang's own save/reload workflow.

Demo content and optional shared demo mode

Demo content is never imported on activation. Open Demo in the plugin settings, read the notice, tick its confirmation and choose Import demo content. A second browser confirmation makes the intended import explicit.

The importer adds eight fictional Morgan-family sample people with invented dates, locations, biographies and relationships. Fixed public-domain archival photographs from Wikimedia Commons are imported for portraits and the family-memory gallery; the photographs do not depict the fictional names. All twelve images must download and validate before a refresh replaces existing demo media. A tree page and introduction page demonstrate the plugin.

The importer adds marked records and keeps existing people, relationships, pages, settings and media. Repeating it reuses marked demo items and preserves edits to them. It does not enable shared access, replace your tree page or starting-person setting, change the family password, or create an account. Imported sample people are part of the archive's person data; remove them in WordPress when they are no longer wanted.

Share an isolated demo

On a separate single-site installation containing only demo family records, enable Shared demo mode after its additional confirmation. This creates:

Access	Demo credential
WordPress username	demo
WordPress password	Demo@demo123Editor
Front-end family password	demo

These intentionally public credentials apply only after an administrator enables the mode. No account or demo mode is enabled by default. An existing user named demo is never taken over or assigned a new password; activation stops instead.

The shared account has a custom Family Tree Demo Editor role. It opens a constrained editor for marked demo people and pages, including names/titles, story text and selected person fields. Visitors can create demo records and remove eligible demo records until the next reset. The account is not a standard WordPress Editor; it cannot manage settings, real content, users, plugins, uploads, arbitrary shortcodes or dynamic blocks. Contact sending is disabled while demo sharing is guarded. Visitor changes are public.

After signing in, open Persons to add a demo person or choose Edit person beside an existing one. Save the form to update its name, story, birth date, location or occupation. Demo pages provides the corresponding page actions. Removal requires confirmation and hides the record until reset. The starting person and tree landing page remain available so visitors can always open the demonstration. Up to 50 visitor-created records are allowed per reset cycle.

The dashboard links to the public tree and shows the next reset time. Returning to the person or page list keeps navigation within the restricted demo editor. The tree landing page's title can be edited; its tree shortcode remains intact.

Open Settings overview to see how the tree page, appearance, languages, access, contact and performance options work. These demonstration controls are read-only: shared visitors can inspect the features while only the site administrator can change site settings. Recipient addresses, service keys, password hashes and other private configuration are excluded from the overview.

Enabling shared mode is blocked if real family posts exist, including drafts, private posts and items in the trash. If a real family record is introduced later or the demo's isolation checks fail, shared access is locked and demo sessions are revoked. An administrator must disable the mode to restore the normal privacy configuration. Demo sharing is unavailable on Multisite; importing the sample content remains available.

The demo gate uses its own cookie and session generation. It leaves the normal family password hash and privacy settings intact. Disable demo mode revokes the shared account and sessions while retaining sample posts, pages and media. Plugin deactivation also revokes the shared account. As with all family access controls, independently protect the site before disabling the plugin if it contains private published content.

Automatic reset every 24 hours

Shared demo mode keeps a saved starting copy of the fields visitors can edit: original person/page titles, stories and publication status, birth dates, locations and occupations. Every 24 hours it restores the original records, brings back originals removed by visitors, and deletes records created through the shared demo editor. The starting copy is retained across resets and demo-mode restarts, so visitor changes do not become the new default merely because sharing was switched off and on.

To deliberately replace the starting copy, disable demo sharing, finish the sample edits as an administrator, then use Save current demo as reset baseline and confirm the replacement. Enable sharing again when the saved examples are ready.

The reset affects only records whose plugin-managed demo ownership can still be verified. Relationships, photographs, unrelated posts, real family data and normal site settings are not restored or deleted. UpdraftPlus or another backup plugin is not required. A first upgrade from an already-active 1.2.0 demo without a saved copy uses the original bundled sample fields.

WordPress schedules the daily task. On an idle site, WP-Cron may run after its scheduled time; the plugin also checks for an overdue reset before allowing the next demo access or edit. The Demo settings show the next reset and provide a separately confirmed Reset demo now action. A form opened before a reset must be reloaded before it can save again.

Contact form and photo attachments

The footer's Contact us / Pieteikties button and the private archive's access-help link open the contact modal. Set the recipient in Contact & hCaptcha. The footer contact button works for both signed-out and signed-in visitors; it does not open the WordPress dashboard. The form asks for the visitor's full name, email address, message and an optional photograph. The privacy text has space above the Send button.

Upload settings

Setting	Default	Options
Photo attachment	Enabled	Enable or disable independently of the contact form
Maximum photo size	10 MB	1–100 MB, subject to lower server limits
Allowed formats	JPG, JPEG, PNG, WebP	Optionally GIF and AVIF when the server supports decoding them
Photos per message	One	Single optional attachment

Visitors can drag a photograph onto the upload area or use its keyboard-accessible chooser. The form shows a preview, filename and size, with controls to remove or replace the photo. It retains the selected photo if sending fails.

The effective file limit is the lowest of the plugin setting and the hosting server's upload/request limits, with space reserved for the message and request fields. Raising the plugin setting cannot override a lower PHP or web-server limit. The form advertises the actual effective limit and formats supported by the server.

The server checks real image content, extension, file size and decoder support. SVG, executable files, renamed scripts and invalid images are not allowed. Very large pixel dimensions may be rejected even when a compressed file is below the byte limit.

The original photo is attached privately to the administrator's email. It is not published, added to the WordPress Media Library or automatically attached to a person's gallery. Temporary upload files are removed after processing, including failed sending attempts. The plugin does not save contact messages as family records. The mail provider or a separate mail-logging plugin may retain its own message and attachment copies.

Mail delivery and hCaptcha

Messages use wp_mail() and the site's configured mail transport. A successful response means WordPress accepted the send operation; delivery to the recipient's inbox depends on the mail service. Verify the recipient and use a correctly configured SMTP transport if required by the host.

hCaptcha is optional and disabled by default. Supply your own site key and secret before enabling it on the contact form, password form or both. The browser loads https://js.hcaptcha.com/1/api.js only on enabled challenge forms. Completing a challenge contacts hCaptcha and its asset hosts. The server posts the site key, secret, response token and visitor IP address to https://api.hcaptcha.com/siteverify; the secret is never sent to the browser. Leaving the secret field blank in settings preserves the stored value.

The form also retains server-side origin and CSRF checks, a honeypot, a minimum completion interval and rate limits. Enabling this service requires an hCaptcha account and keys. Review hCaptcha, its privacy policy and terms. The plugin has no analytics or telemetry and makes no call to an author-operated service. Email uses your site's mail provider. Social links and optional author credits open only when a visitor follows them.

Favicon and Home Screen installation

The included forest-green oak icon is supplied as touch.png (180 × 180), SVG, PNG favicons, an ICO file, 192 / 512 px app icons and a maskable Android icon.

Under Appearance, independently enable the oak favicon/touch icons and the footer's Android / Apple installation controls. The favicon changes only on family-tree pages; other pages retain the theme's site icon. The manifest uses the selected language's tree title and starting page, without including people, passwords, contact details or session tokens.

• Android: the footer button opens the browser's install prompt when available. Otherwise it shows instructions for the browser menu's install / Add to Home screen option.
• iPhone / iPad: the footer button shows instructions for opening the page in Safari, using Share → Add to Home Screen, and enabling Open as Web App where offered.
• Already opened as an installed app: the footer reflects the standalone installed state.

Browser installation requires HTTPS on a live site. Browser support and menu wording vary, so a custom native prompt is not available everywhere. This is an installable web view of the family page; it is not an App Store or Google Play package.

No service worker or offline family-data cache is registered. An internet connection is required. The installed app uses the same password protection and server access checks as the website. Apple/browser storage policies can require signing in again; the plugin does not promise that an existing browser session will transfer to a Home Screen installation.

References: MDN installability guide and Apple's Home Screen guide.

Performance, page source and cache tools

Open Family Tree → Settings & help → Performance & cache. The relationship cache, comments cleanup, emoji removal, head cleanup, minified assets and full-window HTML compaction are enabled by default. Each