Skip to content

1.5.0 — Extra paths to include

Choose a tag to compare

View all tags
@gunjanjaswal gunjanjaswal released this 27 Jul 12:19
· 5 commits to main since this release
v1.5.0
359514c

Adds a way to ship files and folders the crawler never sees in the rendered HTML.

A new Export Scope → Extra paths to include setting lets you bundle assets that don't show up as URLs on any page — a plugin's icon font (Elementor's Font Awesome at wp-content/plugins/elementor/assets/lib/font-awesome, say), a webfont directory, a downloadable PDF. List them one path per line, relative to your WordPress root, and the plugin copies them straight off local disk into the deploy.

  • A whole folder is pulled in recursively, a single file is copied as-is, and a trailing wildcard (wp-content/uploads/2025/*.pdf) is expanded.
  • Bundled files under /wp-content/ get their URLs pointed at the live host so the deployed page loads the bundled copy, while the rest of /wp-content/ stays on origin exactly as before.
  • Because the files are read locally, there's no origin firewall in the way.
  • Paths are confined to the WordPress root — anything escaping it via .. or a symlink is skipped and logged — and each rebuild is capped at 5,000 files / 200 MB.

New setting extra_paths, new class SFORGE_Extra_Assets. Optional; nothing changes unless you set it.

Also on wordpress.org: https://wordpress.org/plugins/staticforge-for-cloudflare-pages/

Assets 2
Loading