Essiow — AI SEO Suite for WooCommerce

更新日志

1.1.14

• Fix: admin assets (admin.js, admin.css) now use a filemtime()-based cache buster on top of the plugin version. Hard-refreshes the browser/CDN cache the moment the JS file changes, even when an update was pushed without bumping the user-visible version. Fixes “user is on the new plugin but the browser still calls the old AJAX endpoints”.
• Improve: legacy synchronous endpoints (essiow_optimize_product, essiow_optimize_category, bulk processors) now also call session_write_close() and raise the PHP time limit before doing any work. Mitigates 504 timeouts on shared hosts where Wordfence WAF or similar serializes admin-ajax requests through a session lock.

1.1.13

• Fix: product and category optimization are now also async (same start → poll → result pattern as blog articles), so single-product and single-category optimizations no longer fail with a 504 Gateway Timeout on hosts behind Cloudflare. The legacy synchronous essiow_optimize_product / essiow_optimize_category endpoints are kept for backward compatibility (used by the bulk optimizer that already handles its own retries).
• Improve: shared runEssiowAsyncTask() helper in admin.js — same network resilience for products/categories as for articles (30 s XHR timeout, 5 consecutive 504s tolerated, 8 s polling interval).
• Improve: prompts now ban colons in titles outright (no exceptions). The previous “avoid colons unless splitting two clearly different ideas” wording was misinterpreted by the AI as permission to keep generic ” : guide / efficace / pas cher” suffixes. Article, product and category SEO titles now use dashes, commas, “vs” or rephrasing instead.

1.1.12

• Fix: definitive fix for “Erreur réseau / 504” on sites behind Cloudflare with Wordfence WAF or any plugin that opens a PHP session. Every AJAX handler now calls session_write_close() at the very top, so concurrent polls are never blocked behind a worker that holds the session lock.
• Fix: removed the HTTP loopback dispatch — on Cloudflare-fronted sites the loopback request to admin-ajax.php went through Cloudflare too and counted as another concurrent admin-ajax hit, which triggered WAF serialization and saturated FPM workers. The plugin now relies on (1) fastcgi_finish_request() when available + (2) WP-Cron with spawn_cron() triggered immediately + (3) a poll-driven fallback in check_status that runs the task itself if it has been pending more than 30 seconds.
• Improve: client-side polling is now resilient to transient 504/timeout errors. A single failed poll no longer kills the generation: up to 5 consecutive network errors are tolerated, the polling interval is 8 s instead of 3 s, the first poll fires after 10 s, and each XHR has an explicit 30 s timeout (well below Cloudflare’s 100 s origin timeout).

1.1.11

• Fix: blog article generation no longer triggers a 504 Gateway Timeout on hosts behind a strict reverse proxy (Cloudflare, Caddy, hardened NGINX). The previous 1.1.8 dispatch ran run_task_inline inside a shutdown action, which keeps the FPM connection open until the AI call completes (10–30 s) — proxies that buffer the entire response would time out at 60 s. The new flow sends the JSON response, calls fastcgi_finish_request(), THEN processes the task in background. The browser sees a sub-second response.
• Improve: loopback fallback (for hosts without fastcgi_finish_request) now uses a 0.5 s timeout instead of 1 s — fewer cases of the parent request hanging while it waits for the loopback to dispatch.

1.1.10

• Fix: blog article generation now passes the real WooCommerce category permalinks to the AI (the previous payload key cat_links was ignored by the server, which expects category_links). Articles now contain real internal links to your store categories instead of invented or missing ones.
• Fix: category optimization now passes blog post permalinks under the correct blog_posts key — the AI can finally weave links to your real articles into the long category description.
• Add: JSON-LD BlogPosting schema is now emitted on the front-end of every Essiow-generated article (gated by the existing schema option). Includes headline, description, datePublished, dateModified, author, publisher, image, keywords. Helps rich snippet eligibility for users not running Yoast/Rank Math.

1.1.9

• Improve: blog articles, products and categories are now generated with intent-driven titles. The AI must analyze the search intent (informational, commercial, transactional, navigational) and produce a question-style or affirmative title that directly answers it — replaces generic clichés like “X : guide complet et conseils efficaces”.
• Improve: AI no longer paraphrases the prompt. Forbidden patterns explicitly listed in prompts: “Introduction” / “Présentation” / “Pour commencer” headings, “voici les liens”, “Dans cet article”, “Saviez-vous que…”, “De nos jours…”. Articles must open with the actual answer in the first sentence.
• Fix: published articles now appear as proper Gutenberg blocks (paragraph, heading, list, table, image, quote, separator) instead of a single HTML block. The plugin parses the AI HTML with DOMDocument and wraps each top-level element in the correct <!-- wp:... --> annotation before wp_insert_post.
• Fix: residual “Introduction” / “Présentation” H2 headings the AI may still slip in are now stripped before publishing.

1.1.8

• Fix: blog article generation no longer hangs with admin-ajax.php ERR_TIMED_OUT on shared / mod_security hosts. Background dispatch now uses a 3-tier strategy: fastcgi_finish_request() (instant, PHP-FPM hosts), HTTP loopback (existing), and WP-Cron fallback (always works). The first available wins; redundant workers are idempotent (transient state guards against double-processing).
• Improve: client-side polling extended from 5 min to 10 min so 5000-word articles have time to complete on slower OpenAI responses.
• Improve: HTTP loopback now forwards cookies for hosts that require an authenticated session even on nopriv handlers.

1.1.7

• Fix: API key now persists correctly across saves (no longer “disappears” after Test Connection)
• Fix: rare “Invalid API key” error caused by encryption format collision (random IV containing the legacy “::” separator) — new “v2:” format is collision-proof, legacy “v1” payloads remain readable
• Add: static cache on get_api_key() prevents redundant decryptions and migration race conditions within a single request
• Add: 5-minute transient cache on license verification, 60-second transient on credit balance — fewer redundant API calls per admin page load
• Add: automatic retry with backoff (1s, 3s) on network errors and 5xx responses (4xx auth/validation are not retried)
• Add: auto-purge of essiow_last_errors entries older than 7 days
• Settings UI: API key field now shows the masked saved key as placeholder, leave empty to keep the saved key
• Improve: uninstall.php now lists encrypted-key options explicitly

1.1.6

• Fix: blog article generation now uses asynchronous task processing to avoid “Network error” on hosts with short proxy or PHP-FPM timeouts
• Improve: background generation worker keeps running on long AI calls (ignore_user_abort, extended time limit, session lock released)

1.0.0

• Initial release
• Product SEO optimization with descriptions, meta, alt text, schema
• Category SEO optimization with rich content and FAQ
• Blog article generator with product integration
• AI Sales Agent with chatbot widget
• 8 languages, 4 tones, 3 content lengths
• Bulk optimization with progress tracking
• Yoast SEO, Rank Math, All in One SEO support
• GDPR compliant