Esipher - AI Site to Theme Converter
| 开发者 |
oluwaseunolaosebikan
afrirates |
|---|---|
| 更新时间 | 2026年10月25日 02:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
wp esipher convert).
Two optional features connect to third-party APIs, and only when you set them up (see "External services" below):
- Esipher > Connected Projects - connect your own GitHub account and repo. GitHub rebuilds on every push and Esipher shows an "Apply update" button; an administrator clicks it to update the theme. Nothing is installed or activated without that click.
- Esipher > Mobile App - Esipher generates a build project in a GitHub repo you own; GitHub Actions builds a native Android (and, optionally, iOS) app from your site.
- Supabase-backed auth, database reads/writes, and live data - detected and reported, never silently dropped.
- Client-side routing beyond what exists in the built HTML.
- Custom component layouts (cards, nav bars, icons) - these display exactly as exported, but aren't broken into individually editable pieces yet. Headings, paragraphs, and images within multi-page conversions are: they come through as real, native Block Editor blocks.
安装:
- Upload the plugin to
/wp-content/plugins/esipher, or install it from the Plugins screen. - Activate it through the "Plugins" screen.
- Open Esipher in the wp-admin menu and upload your export ZIP, or run
wp esipher convert <path-to-zip>from WP-CLI.
常见问题:
Is there a video walkthrough?
Yes: https://youtu.be/6-ne9-7Wgt4 covers exporting from Lovable, building it with the Esipher Build template, and converting it here, start to finish.
Does my code ever leave my server?
No. The entire conversion pipeline - extraction, parsing, asset rewriting, theme generation, and installation - runs locally within your WordPress install.
Can Esipher skip the manual export/upload entirely and just stay in sync?
Yes, under Esipher > Connected Projects. Connect your own GitHub account (you register a free GitHub OAuth App once and paste its Client ID/Secret in - no third-party broker, same "your account, your server" model as the rest of this plugin), then connect the GitHub repo your AI builder syncs to (e.g. GitHub sync from the Lovable or Bolt.new project menu). Esipher commits a small build workflow into that repo and registers a webhook; from then on, every push builds on GitHub and Esipher flags it as "Update ready"; an administrator clicks "Apply update" to download that build and update the theme - no export, no template repo, no manual artifact download. The incoming webhook only records that a build is ready: it can never install or activate anything by itself. A "Sync now" button triggers a rebuild without waiting for your next push. This is separate from, and doesn't replace, the manual ZIP-upload flow below.
My Lovable or Bolt.new export was rejected as "raw source, not a build" - what do I do?
Esipher converts a Vite build's finished output, not a project's raw, uncompiled source. If you exported straight from Lovable or Bolt.new and have never run a build on it, use the Esipher Build template: a free, one-click GitHub Actions workflow made for this. Open that page, click "Use this template" to get your own copy, upload your export's raw .zip to it, and a build runs automatically - no installs, no command line. Download the finished result from that run's Artifacts and upload it to Esipher instead of the original file. This template is the recommended path for Lovable and Bolt.new exports; StackBlitz (build in your own browser) is a general-purpose fallback for other builders' exports.
更新日志:
- Credits: developers listed in the readme and plugin header.
- Fix: plugin author is now shown correctly in the directory.
- New: Bolt.new exports are supported alongside Lovable (built Vite/React output converts the same way; raw Bolt.new source is detected and pointed at the Esipher Build template), and Connected Projects works with Bolt.new's GitHub sync as well.
- New: Esipher > Connected Projects - connect a GitHub-synced AI-builder repo once (your own OAuth App, your own account). Every push builds on GitHub; a webhook (with an hourly cron safety net) flags "Update ready" and an administrator applies it with one click. A manual "Sync now" button triggers a rebuild.
- Fix: the GitHub connection now also requests the "workflow" OAuth scope, which GitHub requires to commit the build workflow file. Without it, connecting a project failed with a bare "Not Found". If you connected a GitHub account on an earlier build, disconnect and reconnect once to grant the added permission - the settings screen warns when this is needed.
- Fix: downloading a build artifact failed with "HTTP 401" - the request to the artifact's signed storage URL was still carrying the GitHub auth header. The download now follows that redirect without it.
- Fix: an auto-sync would report "Up to date" while the site still showed a different theme. With "Keep this theme active" enabled (the default), a connected project now re-activates its theme on any sync where the site isn't already on it, not only the first - and a successful sync that leaves the theme inactive now says so instead of a bare "Up to date".
- Fix: disconnecting a project now always forgets it locally even if GitHub won't remove the webhook, so a later reconnect starts from a clean slate instead of silently reusing stale sync state.
- New: multi-page conversions now bundle a tiny dependency-free script that restores the mobile menu. Because a multi-page conversion ships no framework JavaScript, the hamburger button had nothing wiring it up; the helper wires it - toggling an existing hidden menu panel, or, when the panel only existed in the framework's runtime, synthesising one from the nav's own links.
- New: Esipher > Mobile App - wrap the site in a native app. Esipher generates a Capacitor project in a GitHub repo you own and a bundled GitHub Actions workflow builds it:
- Android (always): a debug APK (sideload to test) and a signed release AAB (for the Google Play Console). The signing keystore is generated in pure PHP (no Java), stored encrypted, and set as encrypted repo secrets.
- iOS (optional, "iOS" tab): a signed .ipa for App Store Connect / TestFlight, built on a macOS runner. Needs a paid Apple Developer account and an App Store Connect API key (Team ID, Key ID, Issuer ID, .p8) - leave those blank and the iOS build is skipped. From that key Esipher provisions a distribution certificate and an App Store provisioning profile via the App Store Connect API (no Mac, no manual certificate steps), stores them encrypted, and the workflow signs with them. Android and iOS build independently: the Android tab builds Android only, the iOS tab builds iOS only, and an "Rebuild Android + iOS" button builds both. So an Apple-side problem never blocks or red-flags an Android build. Uses the same GitHub connection as Connected Projects.
- Change: removed the server-side "build it now" /
wp esipher convert --buildoption, which ran a project's own npm/yarn/pnpm/bun install and build on the server. Build raw source with the Esipher Build GitHub template, a local build, or Connected Projects instead, then upload/sync the output. - Housekeeping: uploads now go through wp_handle_upload(); ZIP extraction and cleanup go through WP_Filesystem; renamed to "Esipher - AI Site to Theme Converter".
- Initial development build: headless conversion engine driven by WP-CLI, generic adapter only.