Skip to content

Early-bird lifetime licence: $199 once, for the first 200 buyers only. See the offer

All docs

Switch from FluentSnippets

Snipfire reads FluentSnippets' snippet files directly and imports them with their settings and conditions. Read Switching from another snippet plugin first for how importing, Check first and Switch over work.

Steps

  1. Snipfire → Snippets → Import, then pick FluentSnippets.
  2. Select the snippets and click Import … selected. They arrive switched off in Imported/FluentSnippets, with FluentSnippets' groups as subfolders.
  3. Look at anything marked Check first.
  4. Click Switch over.
  5. Clear your page cache, check the site, then deactivate and delete FluentSnippets.

Command line: wp snipfire import-from fluent-snippets --dry-run, then --switch.

What comes across

FluentSnippets In Snipfire
PHP snippets PHP on setup_theme (where FluentSnippets runs them), or on wp when they have conditions; admin-only and front-end-only snippets get a Request type condition
PHP + HTML (mixed content) and HTML snippets HTML snippets in the header, after <body> opens, the footer, before or after the content, or as a shortcode (PHP mixed in keeps running)
CSS snippets, including load in block editor CSS on Front end, Front end and block editor or Admin area
JavaScript snippets JavaScript in the front-end or admin header or footer
Load as file External file
Groups Folders
Descriptions, tags, priority, status Description, tags, priority, on/off
Conditions: logged in, user role, page type, post type, taxonomy page, taxonomy term, page IDs, URL, date range, time range, day of week Conditions

Marked "Check first"

  • A location Snipfire doesn't have.
  • A condition with no Snipfire equivalent. It's left out and the note names it.
  • An admin-only snippet with page conditions (page conditions only work on the front end).

Close, but not identical

  • PHP snippets set to run on the front end get a Request type is Front end condition, so they run on the front end only. FluentSnippets also ran them in the admin area; the note says so.
  • CSS FluentSnippets also loaded in the admin: Snipfire loads it on the front end. Duplicate the snippet and set Where to Admin area if you need both.

Shortcodes

[fluent_snippet id="…"] keeps working after switching over, even with FluentSnippets deleted.

Switching over

Snipfire marks each snippet file as draft (@status: draft) and rebuilds FluentSnippets' index. If the index can't be updated, you'll see a note: open FluentSnippets and save any snippet to rebuild it.

Because FluentSnippets runs its snippets from files, Snipfire waits a few seconds between switching them off there and on here when you use WP-CLI, so the server's PHP cache doesn't run both copies.

Something unclear or missing? Tell us