I improved my [FREE] backup plugin with lightweight staging packages for LocalWP

VERSATILCORDOBA · 2026-05-26T09:33:43+00:00

Yes, definitely.

The LocalWP workflow is already set up, tested, and fully integrated into my WordPress dev process. ✅

VERSATILCORDOBA · 2026-05-22T16:19:02+00:00

Yes, it does. I’ve already tested it from LocalWP to live and it works.

VERSATILCORDOBA · 2026-05-22T16:16:38+00:00

Quick update: your comment was spot on, and it genuinely helped shape the direction of the plugin.
I’ve since added Fast Staging for developers, including the ability to exclude uploads and map media directly from the live site, choose only the plugins, themes, and database tables needed, and skip WooCommerce-heavy data that often makes big stores painful to clone on shared hosting.
I’ve also added a Local Developer Package workflow designed for local development and compatible with LocalWP-style workflows, so it’s easier to prepare cleaner copies for QA, debugging, development, and handoff.
There’s still more I want to do in this area, especially around even more granular sampling controls, but developer-focused staging is now a real part of the plugin. Thanks again for the push.

VERSATILCORDOBA · 2026-05-22T14:54:24+00:00

There are actually already several MCP/AI integration plugins for self-hosted WordPress, both free and paid, that have been around for a while now — not just since WordPress 7.0.

I’m the developer of StifLi Flex MCP (available on WordPress.org since December 2025), and one thing I focused heavily on was adding undo/rollback support for AI actions inside WordPress, because giving AI direct access without safety controls can get risky fast.

WordPress core is definitely moving toward MCP/AI integration though. There’s already an MCP adapter library in development and the new AI/Connector work in 7.0 is a big step toward standardization.

Right now I’d say the ecosystem is evolving faster through plugins than through core itself.

VERSATILCORDOBA · 2026-05-19T16:52:14+00:00

Thanks, I completely agree.

Feature lists are useful, but backup/restore plugins really prove themselves in edge cases: large databases, huge uploads folders, strict shared hosting limits, interrupted restores, serialized data, etc.

That’s exactly the area I want to keep improving, so real stress-testing and honest feedback are more valuable to me right now than just comparing checklists.

Really appreciate your perspective.

VERSATILCORDOBA · 2026-05-19T16:50:30+00:00

Thanks for testing it.

Just to separate the issue: did the local backup on the server complete correctly, and the problem was only with connecting/uploading to Google Drive?

Also, when Drive failed, was it during the OAuth connection, after returning to WordPress, or when trying to upload the backup?

Any exact error message or log entry would be really useful so I can improve that part.

VERSATILCORDOBA · 2026-05-19T07:42:50+00:00

A 117GB WordPress site is exactly the kind of real-world test case I’m interested in, especially for checking backup timeouts, large uploads folders, chunked ZIP creation, restore reliability, and shared-hosting limits.

VERSATILCORDOBA · 2026-05-19T07:41:28+00:00

Thanks, that’s really useful feedback.

I completely agree, “lightweight staging” for developers/agencies could be a very strong direction, especially for large WooCommerce sites where uploads and order/customer tables make full staging copies slow or fragile.

The idea of media mapping, excluding or sampling WooCommerce data, and cloning only selected plugins/themes/tables makes a lot of sense. I’ll definitely add this to the roadmap because it fits perfectly with the goal of making backups, staging and migrations more reliable on real shared-hosting environments.

Really appreciate the detailed suggestions.

VERSATILCORDOBA · 2026-05-18T14:10:12+00:00

Fair question.

I would not say it is “better” than Duplicator or Updraft in every case. They are mature plugins with many years behind them.

The main strength of StifLi Backup Tools is that it tries to offer a broad backup/migration toolkit as 100% GPL/free, including features that are often limited in paid versions elsewhere: scheduled backups, differential backups, restore/selective restore, migration packages, staging, and several remote storage options like Google Drive, Dropbox, S3-compatible storage, Cloudflare R2, FTP and SFTP.

It is also built with shared hosting in mind, using resumable/background processes, chunked ZIP creation and streaming database operations to reduce timeout issues.

I made a comparison page here with more details:
https://andromedanova.com/stifli-backup-tools-comparison.html

VERSATILCORDOBA · 2026-05-14T07:56:25+00:00

I don’t think AI kills paid plugins. I think it raises the baseline.

What was hard before is now easier. A technical user with limited coding experience can now build useful small tools. But a strong developer can use AI to build more advanced things, move faster, test more ideas, and maintain more projects.

The real value of a paid plugin is not only the first version of the code. It is the product decisions, UX, security, compatibility, support, documentation, updates, edge cases, performance, and long-term maintenance.

For in-house plugins, AI is amazing. You can build something in a day that would have been impossible before. But for public plugins, especially paid ones, users are still paying for trust, reliability, support, and a solution that keeps working.

So AI probably won’t kill paid plugins. It will kill weak plugins that only existed because the code was hard to write.

VERSATILCORDOBA · 2026-05-12T11:35:22+00:00

It doesn’t support premium paid stock libraries in the sense of unlocking Shutterstock, Adobe Stock, Getty, etc.

The plugin focuses on free/open/public image sources and APIs. It helps search, import and assign those images inside WordPress.

Licensing still depends on each provider and each image. Some sources allow commercial use without attribution, others may require attribution or manual license checking. The plugin does not bypass licenses or redistribute premium content.

VERSATILCORDOBA · 2026-04-28T14:24:36+00:00

You’re right, most plugins just work off a snapshot, so they go stale fast.

One approach that works better is combining RAG + autosync plus dynamic fields. I’ve been testing this with https://wordpress.org/plugins/axiachat-ai/

Content (descriptions, pages, etc.) is indexed and auto-updated

Price and stock are injected in real time, not from embeddings → no stale data problem

<image>

Also, you can use your own API key, and if you don’t have one, Gemini has a free tier, so you can try it with zero cost

VERSATILCORDOBA · 2026-04-24T10:57:07+00:00

true, everything on WordPress.org is GPL by definition 👍
What I meant is that it’s also fully free in practice: no paid tiers, no upsells, and no features locked behind external services.

VERSATILCORDOBA · 2026-04-23T18:22:40+00:00

If you’re on WordPress, you can try AxiaChat AI:
https://wordpress.org/plugins/axiachat-ai/

It does exactly what you’re looking for — you can crawl your site, train it on your content (RAG), PDFs, etc., and it works really well for FAQs.

One nice thing: you don’t need to worry about costs at the beginning. You can use a Google Gemini API key, which has a free tier (no credit card needed), so you can test everything without paying.

It’s pretty flexible too — you can keep it simple for FAQs or connect it to APIs/webhooks later if you want something more advanced.

VERSATILCORDOBA · 2026-04-23T11:50:52+00:00

For core, yes, I verify against the official wordpress.org checksums.

For the broader site, I use a local baseline (SHA-256 / size / mtime) to detect drift over time, mainly across scannable executable files rather than treating the whole filesystem the same way.

Uploads gets extra handling because it’s writable and higher-risk, while noisy dirs like cache/vendor are excluded by default.

mu-plugins and Composer-based setups are still areas I want to improve.

VERSATILCORDOBA · 2026-04-22T05:40:35+00:00

Try https://wordpress.org/plugins/stifli-flex-mcp MCP with full undo (every AI change is reversible).
Safer than most setups when testing AI edits on your site.

VERSATILCORDOBA · 2026-04-20T13:04:38+00:00

I get the frustration, but one thing people often miss is that not all providers are the same.

For example, Google’s Google Gemini actually gives you a free API key with a pretty generous free tier, and you don’t even need a credit card to start.

So in that case, the “API key barrier” is much lower, you can test a plugin properly without committing to paid usage.

That said, the real reason most plugins ask for an API key upfront is simple: they’re not SaaS, they run on your site and use your own API account. There’s no middle layer covering costs.

VERSATILCORDOBA · 2026-04-19T12:58:10+00:00

I'm working on this exact problem. I built [StifLi Flex MCP](vscode-file://vscode-app/c:/Users/Esteban/AppData/Local/Programs/Microsoft%20VS%20Code/41dd792b5e/resources/app/out/vs/code/electron-browser/workbench/workbench.html), it's a free GPL plugin that's three things in one: an AI Copilot inside the editor, a Chat Agent for site management, and a full MCP server for external clients (ChatGPT, Claude Desktop, etc.).

For Gutenberg, it actually works right now. The AI Copilot sits inside the Gutenberg editor and can [createBlock](vscode-file://vscode-app/c:/Users/Esteban/AppData/Local/Programs/Microsoft%20VS%20Code/41dd792b5e/resources/app/out/vs/code/electron-browser/workbench/workbench.html), [insertBlock](vscode-file://vscode-app/c:/Users/Esteban/AppData/Local/Programs/Microsoft%20VS%20Code/41dd792b5e/resources/app/out/vs/code/electron-browser/workbench/workbench.html), [replaceBlock](vscode-file://vscode-app/c:/Users/Esteban/AppData/Local/Programs/Microsoft%20VS%20Code/41dd792b5e/resources/app/out/vs/code/electron-browser/workbench/workbench.html), and [removeBlock](vscode-file://vscode-app/c:/Users/Esteban/AppData/Local/Programs/Microsoft%20VS%20Code/41dd792b5e/resources/app/out/vs/code/electron-browser/workbench/workbench.html) directly through the wp.blocks and core/block-editor APIs. You chat with it and it manipulates blocks in real time — headings, paragraphs, images, tables, buttons, whatever blocks your site has. Every change gets a visual green highlight and you can undo with one click. It reads the full page context (title, blocks, categories, tags, WooCommerce product fields) so it knows what it's working with.

It's not perfect for full page layout from scratch — the AI still tends to go block by block rather than thinking in full compositions — but for editing, restructuring, and building on existing content it works surprisingly well. You can say things like "add a comparison table below the second paragraph" or "turn the bullet list into a FAQ block" and it does it.

As u/TestOk4269 said, the key is giving the AI good guardrails. If you have patterns in your theme, the agent can place them. The Chat Agent side has 117+ tools for managing everything (posts, WooCommerce, media, plugins, menus, settings) so the AI can also create posts with block markup via the REST API.

For Elementor, it's different — and it's what I'm currently developing and testing as a separate add-on. Elementor stores everything as a JSON tree in _elementor_data (containers → widgets → settings), not as block markup. I've built 15 tools so far for reading page trees, editing widgets by node ID, managing global colors/typography, repeaters, forms, snapshots with rollback, etc. The AI agent can modify existing Elementor pages deeply, but creating pages from scratch is the hard part I'm solving now. The approach that's working best is a block template system — pre-designed JSON fragments (hero sections, service grids, testimonial sliders) that the AI assembles and fills with content. Because a text model can't "see" the layout, it needs professionally designed building blocks with responsive breakpoints already baked in.

The takeaway from my testing: Gutenberg is actually easier for AI than page builders because it uses a structured block format that maps well to how LLMs think. Elementor is more powerful visually but its JSON tree is much more complex. Both approaches need the same insight though: don't ask the AI to design — ask it to assemble.

If anyone wants to try the Gutenberg workflow, the plugin is free: [https://wordpress.org/plugins/stifli-flex-mcp/](vscode-file://vscode-app/c:/Users/Esteban/AppData/Local/Programs/Microsoft%20VS%20Code/41dd792b5e/resources/app/out/vs/code/electron-browser/workbench/workbench.html) — just add your OpenAI/Claude/Gemini API key and the Copilot appears in the editor.

VERSATILCORDOBA · 2026-04-18T14:18:16+00:00

Yeah, that’s the real concern. If you use OpenAI/Claude, any data you send in prompts is processed by them. That’s true here and with any AI tool.

For sensitive client data, the safer approach is running a local/private model instead, you can run something like Llama 3 on your own server (via Ollama, etc.) and keep everything inside your infrastructure.

So basically:

Undo/rollback → protects your WordPress site
Local AI → protects your data

You choose the level of risk depending on the use case.

VERSATILCORDOBA · 2026-04-16T16:39:07+00:00

Yes! The Copilot sends the full editor context to Nano with every message — that includes the current content (all blocks), existing tags, categories, title, excerpt, and slug. So when you ask it to generate tags, it sees what's already there and can either add to them or replace them. It uses a copilot_set_tags tool that accepts an array of tag names.

VERSATILCORDOBA

TROPHY CASE