First public release on WordPress.org.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3522119,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3522119,"resolution":"256x256","location":"assets","locale":""}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3522119,"resolution":"1544x500","location":"assets","locale":""},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3522119,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.5.0","1.5.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3522207,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3522119,"resolution":"2","location":"assets","locale":""},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3522212,"resolution":"3","location":"assets","locale":""},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3522162,"resolution":"4","location":"assets","locale":""},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3522162,"resolution":"5","location":"assets","locale":""},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3522207,"resolution":"6","location":"assets","locale":""},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3522207,"resolution":"7","location":"assets","locale":""},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3522207,"resolution":"8","location":"assets","locale":""}},"screenshots":{"1":"Practitioner dashboard, with recent activity feed and per-client progress overview.","2":"Journeys list, where you manage and organise your client programmes.","3":"Milestone editor, with rich text descriptions and video URL embedding.","4":"Client list, with progress overview and one-click resend welcome email.","5":"Backup\/Restore, with nightly auto-snapshots and reversible restore for safe data recovery.","6":"Client portal, a clean dashboard showing assigned journeys with progress.","7":"Client milestone page, with guidance and an inline reflection form.","8":"Branding settings, where you set your portal name, logos, primary colour, and footer credit."},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[17989,9110,156384,261818,10305],"plugin_category":[],"plugin_contributors":[261820],"plugin_business_model":[],"class_list":["post-303166","plugin","type-plugin","status-publish","hentry","plugin_tags-client-portal","plugin_tags-coaching","plugin_tags-mentoring","plugin_tags-personal-trainer","plugin_tags-wellness","plugin_contributors-sprigly","plugin_committers-sprigly"],"banners":{"banner":"https:\/\/ps.w.org\/sprigly\/assets\/banner-772x250.png?rev=3522119","banner_2x":"https:\/\/ps.w.org\/sprigly\/assets\/banner-1544x500.png?rev=3522119","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/sprigly\/assets\/icon-128x128.png?rev=3522119","icon_2x":"https:\/\/ps.w.org\/sprigly\/assets\/icon-256x256.png?rev=3522119","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-1.png?rev=3522207","caption":"Practitioner dashboard, with recent activity feed and per-client progress overview."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-2.png?rev=3522119","caption":"Journeys list, where you manage and organise your client programmes."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-3.png?rev=3522212","caption":"Milestone editor, with rich text descriptions and video URL embedding."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-4.png?rev=3522162","caption":"Client list, with progress overview and one-click resend welcome email."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-5.png?rev=3522162","caption":"Backup\/Restore, with nightly auto-snapshots and reversible restore for safe data recovery."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-6.png?rev=3522207","caption":"Client portal, a clean dashboard showing assigned journeys with progress."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-7.png?rev=3522207","caption":"Client milestone page, with guidance and an inline reflection form."},{"src":"https:\/\/ps.w.org\/sprigly\/assets\/screenshot-8.png?rev=3522207","caption":"Branding settings, where you set your portal name, logos, primary colour, and footer credit."}],"raw_content":"\n
Sprigly gives practitioners a structured way to guide their clients through a journey, and gives clients a beautiful portal where they can see exactly where they are, complete milestones, and write reflections.<\/p>\n\n
Whether you're a life coach, personal trainer, mentor, tutor, instructor, teacher, nutritionist, or any kind of practitioner, Sprigly replaces scattered emails and spreadsheets with a clear, trackable progress experience your clients will love.<\/p>\n\n
How it works:<\/strong><\/p>\n\n What's included in Sprigly (free, uncapped):<\/strong><\/p>\n\n Built for:<\/strong><\/p>\n\n Available as a paid upgrade (Sprigly Pro, sold separately):<\/strong><\/p>\n\n Sprigly Pro is a separate plugin available from sprigly.co that adds the practitioner toolkit on top of Sprigly Lite:<\/p>\n\n Pro requires Sprigly to be installed and active. Learn more at https:\/\/sprigly.co\/pricing\/.<\/p>\n\n Sprigly is designed to keep your client data on your own WordPress installation. Plugin emails are sent through your site's own There are two narrow exceptions where the plugin reaches out to a third party. Both are documented below.<\/p>\n\n When a practitioner pastes a YouTube or Vimeo video URL into a milestone's \"Video URL\" field, Sprigly uses WordPress's built-in oEmbed system ( The feature is opt-in by behaviour: pasting a video URL into a milestone is the only way to trigger it. Leave the field blank and Sprigly never contacts either service.<\/p>\n\n The optional Report a Bug form in Sprigly, Settings, Tools sends a single email through your site's own The System Information block: Sprigly version, WordPress version, PHP version, site URL, active theme name, and the name of any SMTP plugin you have installed<\/p><\/li>\n What is sent: only what you typed plus the System Information block above.<\/p><\/li>\n Sprigly's Privacy Policy: https:\/\/sprigly.co\/privacy-policy\/\nSprigly's Terms and Conditions: https:\/\/sprigly.co\/terms\/<\/p>\n\n\n Important:<\/strong> Set your WordPress permalink structure to Post name<\/strong> (Settings \u2192 Permalinks \u2192 Post name) before activating Sprigly. This is required for the Recommended:<\/strong> Install and configure an SMTP plugin (WP Mail SMTP, Post SMTP, FluentSMTP, or Easy WP SMTP) to ensure reliable email delivery. By default, WordPress sends mail through your hosting server, which can be filtered or junked by Gmail\/Outlook\/Yahoo. Sprigly detects an active SMTP plugin and shows its status in Sprigly \u2192 Settings \u2192 Tools<\/strong>.<\/p>\n\n\n Yes. The client portal at Yes, each client has a WordPress user account with the At Nothing, by default. The \"Protect data on uninstall\" setting is ON by default, which means all your journeys, clients, milestones, and reflections are kept in the database even if the plugin is deactivated or deleted. You can change this behaviour in Sprigly \u2192 Settings \u2192 Tools<\/strong>.<\/p><\/dd>\n Yes. Sprigly detects WP Mail SMTP, Post SMTP, FluentSMTP, and Easy WP SMTP automatically and routes all email through whichever is active. We strongly recommend installing an SMTP plugin for reliable delivery.<\/p><\/dd>\n Yes. You can set a custom portal name, upload separate logos for the login page and the portal nav bar, set logo heights, and pick a primary brand colour (used for buttons, progress bars, and accents in the portal and emails).<\/p><\/dd>\n Yes. When creating or editing a journey, set the \"Client-facing role\" field to whatever suits your profession, coach, trainer, mentor, teacher, tutor, instructor, guide, etc. This replaces the default \"practitioner\" in all client-facing emails for that journey. A suggestion is auto-filled based on the Industry\/Category you select, but you can change it to anything you like.<\/p><\/dd>\n Sprigly Pro (sold separately at sprigly.co) layers on the practitioner toolkit: checkpoint sign-offs, scheduled milestone unlocks, custom check-in fields, a Resources library, practitioner notes, file uploads on reflections, branded PDF progress reports, JSON export and import, multi-practitioner Team support, and a branded login page. See https:\/\/sprigly.co\/pricing\/ for the full feature list.<\/p><\/dd>\n Sprigly keeps your client data on your own WordPress installation, sends emails through your own site's There are two narrow situations where the plugin does reach out to a third party, both opt-in by behaviour:<\/p>\n\n Both are documented in full in the External Services section of this readme, including Terms and Privacy links for each provider.<\/p><\/dd>\n Sprigly is built to support GDPR compliance. Client data is stored only on your own WordPress installation. You remain the data controller for all client data on your site.<\/p><\/dd>\n Sprigly ships a built-in Safety & Backups page (Sprigly, Safety & Backups, admin-only). It takes snapshots of all nine Sprigly DB tables (journeys, milestones, clients, progress, reflections, notes, resources, custom fields, field responses) directly inside your own database. Nothing is sent off-site. By default the plugin takes a snapshot every night and after every Sprigly plugin update, plus you can take a manual snapshot any time. Restores are reversible (a pre-restore safety snapshot is taken automatically). Both automatic behaviours can be disabled in the Settings tab. This is a safety net for routine \"before I touch this\" moments, your hosting provider's full-site backups remain the authoritative recovery path for catastrophic loss.<\/p><\/dd>\n WordPress.org pre-approval response cycle 3: addresses the two issues flagged in the third reviewer email (escape-on-output and unique prefixes).<\/p>\n\n Follow-up release after v1.4.0 testing. Bundles 16 fixes flagged during the cycle-2 reviewer-response testing pass plus a security tightening on the Backup\/Restore admin.<\/p>\n\n WordPress.org pre-approval response cycle 2: this release lands the changes flagged in the second reviewer email so the plugin can clear the trialware, attribution, sanitization, hardcoded-URL, and text-domain checks.<\/p>\n\n\n
\/portal\/<\/code> on your WordPress site and see their journey, milestone by milestone<\/li>\n\n
\/portal\/<\/code><\/li>\n.htaccess<\/code> hardening + media library filter<\/li>\n\n
\n
External Services<\/h3>\n\n
wp_mail()<\/code> (which you can route through any SMTP plugin you choose), and the plugin's typography is loaded from font files that ship inside the plugin (no Google Fonts request, no preconnect).<\/p>\n\n1. YouTube and Vimeo oEmbed (only when you paste a YouTube or Vimeo URL into a milestone)<\/h4>\n\n
wp_oembed_get()<\/code>) to fetch the embed metadata so the milestone page can show the video. This sends one HTTP request to the relevant provider's oEmbed endpoint to retrieve the iframe HTML; the provider sees the milestone's video URL plus a referrer header from your site. The response is cached by WordPress for 24 hours, so subsequent page loads do not re-fetch.<\/p>\n\n\n
\n
2. Bug report email (only when you click \"Send Bug Report\")<\/h4>\n\n
wp_mail()<\/code> to the Sprigly support address. The form is never submitted automatically. When you click the button, the email contains:<\/p>\n\n\n
\n
\/portal\/<\/code> URL to work correctly.<\/p>\n\n\n
Does Sprigly work with any WordPress theme?<\/h3><\/dt>\n
\/portal\/<\/code> is fully self-contained and does not inherit your theme's styles. It works correctly with any theme \u2014 including page builders like Divi, Elementor, and Beaver Builder.<\/p><\/dd>\nDo clients need a WordPress account?<\/h3><\/dt>\n
sprigly_client<\/code> role. This role gives them access only to the client portal \u2014 they cannot access wp-admin. Sprigly creates the account automatically when you add a client.<\/p><\/dd>\nWhere is the client portal?<\/h3><\/dt>\n
\/portal\/<\/code> on your WordPress site (e.g. yourdomain.com\/portal\/<\/code>). You can find the full URL in Sprigly \u2192 Settings \u2192 Portal<\/strong>. Share this link with your clients.<\/p><\/dd>\nWhat happens to my data if I deactivate the plugin?<\/h3><\/dt>\n
Does Sprigly work with my SMTP plugin?<\/h3><\/dt>\n
Can I use my own branding?<\/h3><\/dt>\n
Can I change how I'm referred to in client emails?<\/h3><\/dt>\n
What does the paid Sprigly Pro plugin add?<\/h3><\/dt>\n
Does Sprigly contact any external services?<\/h3><\/dt>\n
wp_mail()<\/code>, and ships its display font (Poppins) inside the plugin so the portal does not contact Google Fonts.<\/p>\n\n\n
wp_oembed_get()<\/code> to fetch the embed metadata from YouTube or Vimeo so the video can render. The response is cached for 24 hours.<\/li>\nIs Sprigly GDPR-compliant?<\/h3><\/dt>\n
How do I back up my Sprigly data?<\/h3><\/dt>\n
What are the hosting requirements?<\/h3><\/dt>\n
\n
1.5.1<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.3<\/h4>\n\n
\n
1.4.2<\/h4>\n\n
\n
wp_kses_post()<\/code> before echoing. The two affected echoes ($milestone_card_extras<\/code> from the sprigly_admin_enrolment_milestone_card_extras<\/code> extension point, and $sp_item['html']<\/code> from the sprigly_admin_milestone_timeline_items<\/code> filter) previously trusted contributing renderers to pre-escape; they now late-escape regardless, so a future filter callback returning unfiltered HTML cannot inject into the admin screen.<\/li>\nSP_<\/code> prefix are renamed to the standard Sprigly_<\/code> prefix: SP_Backup<\/code> becomes Sprigly_Backup<\/code> and SP_Admin_Safety<\/code> becomes Sprigly_Admin_Safety<\/code>. Both ship a class_alias()<\/code> for backwards compatibility so any external code that still references the old names keeps working. The wp_localize_script<\/code> JS object handed to portal-reflection.js<\/code> is renamed from spReflectionStrings<\/code> to spriglyReflectionStrings<\/code> (the JS file is updated in lockstep).<\/li>\nsp_*<\/code> keys missed by the v1.2.0 prefix migration are now handled. A new upgrade_to_1_4_2_rename_residual_sp_options()<\/code> routine copies values for sp_portal_page_id<\/code> to sprigly_portal_page_id<\/code> and sp_suspended_practitioners<\/code> to sprigly_suspended_practitioners<\/code>, then renames the _sp_client_id<\/code> post meta key on reflection attachments to _sprigly_client_id<\/code> in place. Idempotent. The legacy admin_post_sp_send_test_email<\/code> and admin_post_sp_send_bug_report<\/code> aliases (kept for the v1.2.0 to v1.3.0 transition) are removed; the canonical sprigly_*<\/code> action hooks remain. Stale _sp_*<\/code> references in doc comments are corrected to match the live _sprigly_*<\/code> keys.<\/li>\npaused<\/code> status but had no UI to transition out of it (Pro's Pause\/Reactivate buttons hide when is_pro()<\/code> returns false). Lite now renders a Reactivate button for paused enrolments whenever no add-on is hooked to sprigly_client_status_actions<\/code>, so a Pro to Lite downgrade can never lock the practitioner out of their own data. The button posts new_status=active<\/code> through the existing update_client_status<\/code> handler (which already accepts active<\/code> in its default whitelist, no DB layer change needed).<\/li>\nSprigly->cleanup_deleted_user()<\/code> now early-returns when the sp_journeys<\/code> table does not exist on the site. Previously, when WordPress fired deleted_user<\/code> on an install where Sprigly was loaded but its tables had never been created (or had been dropped by a cleanup utility), the cascade fired several queries against missing tables and flooded debug.log<\/code> on every WP user deletion. The guard is one SHOW TABLES LIKE<\/code> per call.<\/li>\nSprigly: Do not delete<\/code>), client-profile and journey-list dropdown placeholders (Select journey...<\/code>, Select user...<\/code>, Select...<\/code>), bug-report email subject, and admin notices are replaced with commas, periods, parentheses, or colons depending on context. Single em-dash placeholders for empty values (Phone, Industry, First Assigned columns) become empty strings. Code comments and error_log()<\/code> debug output are unchanged. Internal punctuation only, no behaviour change.<\/li>\n<\/ul>\n\n1.4.1<\/h4>\n\n
\n
class-sp-portal.php<\/code> (sprigly_portal_skip_auth_check<\/code>, sprigly_portal_skip_form_actions<\/code>, sprigly_portal_skip_role_autorestore<\/code>, sprigly_portal_resolve_user_id<\/code>, sprigly_portal_skip_render_dispatch<\/code> + sprigly_portal_render<\/code>, sprigly_portal_url<\/code>, sprigly_portal_body_class<\/code>, sprigly_portal_after_shell_open<\/code>, sprigly_portal_nav_html<\/code>, sprigly_portal_head<\/code>) so add-ons can re-implement preview without Sprigly carrying any preview-specific code itself. The Settings \u2192 Upgrade tab lists Preview Journey again under Authoring & workflow.<\/li>\nmanage_options<\/code> capability, so a hosting account, web designer, accountant, or any other non-owner administrator on the site cannot create, restore, or delete snapshots.<\/li>\nensure_admin_practitioner_role()<\/code> no longer leaks the sprigly_practitioner<\/code> role to every WordPress administrator on admin_init<\/code>. Pre-v1.4.1 the helper auto-added the role to ANY user with manage_options<\/code>, which meant a brand-new WP admin (hosting account, web designer, etc.) was silently treated as a Sprigly practitioner the first time they loaded wp-admin: they showed up in Sprigly \u2192 Team and saw the full Sprigly menu. The auto-grant is now scoped to the designated Sprigly owner. Non-owners only become practitioners through an explicit Team \u2192 Invite Practitioner \/ \"Add me as a practitioner\" banner \/ practice-setup form path.<\/li>\nis_practitioner()<\/code> no longer treats every WordPress administrator as a Sprigly practitioner. Only the designated owner OR users explicitly carrying the sprigly_practitioner<\/code> role pass the helper now.<\/li>\n#ID<\/code>s, matching the table's \"When\" column. Post-update snapshots now also fire on single-plugin updates (the previous handler only listened for the plugins<\/code> plural array key, missing the plugin<\/code> singular set by core's standard upgrade flow).<\/li>\nclass-sp-admin-settings.php:191<\/code> (WordPress.Security.ValidatedSanitizedInput.InputNotSanitized<\/code>) is suppressed with a phpcs:ignore comment naming the per-type whitelist (sanitizer_for_type<\/code>) \u2014 sanitization is happening, just dynamically dispatched.<\/li>\n<\/ul>\n\n1.4.0<\/h4>\n\n
\n
sprigly_admin_client_filter_status_options<\/code> available for add-on plugins that introduce additional workflow states.<\/li>\nregister_setting()<\/code>. The single generic sanitize_text_field<\/code> callback is replaced by per-option sanitizers driven by an explicit type schema: esc_url_raw<\/code> for logo URLs, bounded absint<\/code> (with min\/max) for the login-logo and nav-logo heights, sanitize_hex_color<\/code> for the brand colour, and a yes<\/code>\/no<\/code> whitelist for toggles. The custom save handler in Settings \u2192 Branding now routes every posted value through the same sanitizer table, so writes via the Settings UI and writes via the Options API stay consistent.<\/li>\nhome_url('\/wp-login.php?...')<\/code> replaced with wp_login_url()<\/code> + add_query_arg()<\/code> in the SiteGround Security login-redirect branch (class-sp-portal.php<\/code>), so subdirectory installs and renamed-login plugins resolve the login URL correctly.<\/li>\n__( '...', 'default' )<\/code> calls in the Plugins-page row-meta de-duplication helper are removed. The helper now compares against the canonical English labels emitted by WordPress core; a non-English locale may show a benign extra row-meta link, which is the smaller of the two trade-offs.<\/li>\nclass-sp-portal.php<\/code>, class-sp-email.php<\/code>, class-sp-roles.php<\/code>, class-sp-database.php<\/code>, class-sp-install.php<\/code>, class-sp-login.php<\/code>, class-sp-admin-clients.php<\/code>, class-sp-admin-journeys.php<\/code>, class-sp-admin-settings.php<\/code>, and class-sp-admin-menus.php<\/code> is rewritten in neutral \"extension point\" \/ \"add-on plugins can hook here\" language. The Settings \u2192 Upgrade tab no longer lists Preview Journey or Hide Powered by Sprigly as Pro features (Preview is free now; the Powered by toggle ships in Sprigly itself).<\/li>\ncount_hidden_pro_features()<\/code> and count_hidden_pro_features_for_milestone()<\/code> helpers (which existed in Lite solely to support the add-on's downgrade-detection email + dashboard banner) are removed from class-sp-database.php<\/code>. The add-on plugin owns this functionality at its own callsite now.<\/li>\nSP_Database::insert_journey()<\/code> \/ update_journey()<\/code> no longer write sequential_mode<\/code>; SP_Database::insert_milestone()<\/code> \/ update_milestone()<\/code> no longer write milestone_type<\/code>, unlock_type<\/code>, unlock_date<\/code>, unlock_days<\/code>, or require_reflection<\/code>. Add-on plugins that rely on those columns hook the existing sprigly_save_journey<\/code> and sprigly_save_milestone<\/code> actions to persist them via direct