Description
Robosolo Connector for SEOFLY links your WordPress site to your SEOFLY account (https://seofly.ir), so the SEO articles you generate there are delivered and published on your site without copy-pasting.
How it works
- Create your SEOFLY account and add your site in the SEOFLY dashboard.
- Install the connector and open Settings → Robosolo Connector for SEOFLY.
- Enter the Platform URL, Client ID and Secret, then press “Save & Connect”.
- Publish (or send as draft) articles from SEOFLY — they appear on your site automatically.
Features
- Server-to-server REST connection signed with HMAC-SHA256, with a per-request timestamp (5-minute window) and replay protection.
- Articles are delivered as posts: title, content, excerpt, slug, categories and tags.
- Featured image is uploaded automatically and set as the post thumbnail; in-article images can be uploaded to the WordPress media library before publishing.
- Full Yoast SEO and Rank Math support: meta title, meta description and focus keyword are written to the matching fields of the active SEO plugin.
- When no SEO plugin is active, the connector outputs the meta description, Open Graph tags and FAQPage JSON-LD schema itself.
- WooCommerce support: SEOFLY can read your published products, update product descriptions and SEO fields, and create brand-new WooCommerce products (simple or variable) with images, prices, stock, categories and SEO meta.
- Draft or direct publish mode — you always control what goes live.
- Connection monitoring: a signed hourly heartbeat lets your SEOFLY dashboard show that the connection is healthy — and warn you before a scheduled publish on an unreachable site can fail.
- Translation-ready (English default; a Persian (fa_IR) translation is bundled in /languages, and translations are also managed on translate.wordpress.org).
- Master switch: the connector can be paused from its own settings page without deactivating the plugin.
Privacy
The plugin communicates only with the SEOFLY platform URL that you configure in the settings. It does not track your visitors and does not collect analytics. See the “External Services” section for the exact data flow.
External Services
Outbound — SEOFLY platform (the URL you set in Settings → Robosolo Connector for SEOFLY, for example https://seofly.ir)
The plugin contacts the SEOFLY platform API in two cases:
- Credential check — when you press “Save & Connect” in the settings, to verify your credentials.
- Connection heartbeat — an hourly WP-Cron event sends the same site identity as the credential check to the same platform URL (path /api/agent/health), so your SEOFLY dashboard can show whether the connection to your site is still alive, warn you before a scheduled publish fails and keep the recorded plugin version current.
- What is sent: the credential check sends your site URL, WordPress version, plugin version, which SEO plugin is active (Yoast, Rank Math or none) and whether WooCommerce is active. The hourly heartbeat sends the same WordPress/plugin version identity (no article content, no visitor data): the request headers carry only the Client ID, a timestamp and the HMAC-SHA256 signature.
- When: the credential check only when an administrator clicks “Save & Connect” in the plugin settings; the heartbeat hourly while credentials are configured — scheduled on activation, removed on deactivation.
- Service terms: https://seofly.ir/terms
- Service privacy policy: https://seofly.ir/privacy
Inbound — REST endpoints (seofly/v1 namespace)
The plugin registers REST API routes (site-info, products, posts, articles, media) so the SEOFLY platform can read basic site information and deliver the articles that you send from your own SEOFLY account. These routes do not use WordPress user accounts: every request must be signed with the HMAC-SHA256 secret known only to your site and your SEOFLY account, carries a timestamp with a 5-minute window, and is protected against replay. Articles are only created, updated or trashed when they come from your SEOFLY account; deleting is limited to posts created by the connector.
No other third-party services are contacted by this plugin.
Installation
- Upload the plugin files to the
/wp-content/plugins/robosolo-connector-for-seoflydirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the ‘Plugins’ screen in WordPress.
- Go to Settings → Robosolo Connector for SEOFLY, enter the Platform URL, Client ID and Secret from your SEOFLY dashboard and press “Save & Connect”.
- From SEOFLY, send a test article to make sure everything works.
Coming from an earlier direct-download build (“SEOFLY Connector” or “Connector for SEOFLY”)? Just install and activate this plugin — your connection settings and previously published articles carry over automatically (they live in shared WordPress options, not in the plugin folder); then deactivate the old copy.
FAQ
Do I need a SEOFLY account?
Yes. The connector is the publishing bridge for the SEOFLY content platform (seofly.ir). Everything it publishes comes from your SEOFLY account.
Where do I find the Client ID and Secret?
In your SEOFLY dashboard, open the settings of your site and copy the Client ID and Secret shown there.
Can I review articles before they are published?
Yes. Choose draft mode in SEOFLY and every delivered article will wait in your posts list for your approval.
Does it work with Yoast SEO or Rank Math?
Yes. Meta title, meta description and focus keyword are written to the matching fields of the active SEO plugin. Without an SEO plugin, the connector outputs basic meta and Open Graph tags and FAQPage schema itself.
Does the plugin send my site data anywhere else?
No. The only endpoint is the SEOFLY platform URL you configure yourself, as documented in the External Services section.
I used the direct-download SEOFLY Connector / Connector for SEOFLY. Do I lose my settings?
No. Connection settings, scheduled events and published articles migrate automatically on the first run of this plugin; nothing is lost. Because the plugin folder name changed to match its WordPress.org slug, activate this plugin first and deactivate/delete the old copy afterwards.
What happens to my posts if I remove the plugin?
Uninstalling removes the plugin options and its post meta. Your posts, images and product data remain untouched.
Changelog
3.4.0
- Fixed: the true root cause of “the product gallery never updates” is finally proven from the official WooCommerce code reference – since 3.3.2 the connector called WooCommerce methods that have never existed: WC_Product only has get_gallery_image_ids()/set_gallery_image_ids(); there is no get_gallery_ids()/set_gallery_ids(). Every gallery path died with “Call to undefined method WC_Product::…()”: the 10-image limit count line of POST /products/{id}/images (since 3.3.3 the whole route died before any sideload – which is why every image actually traveled through the images[] fallback), the gallery assignment in that same route, the inline gallery of POST /products/new, the fallback loop, and even the 3.3.10 gallery_id compensation. That is exactly why featured images (set_post_thumbnail = a direct meta write) kept landing while attachments sat in the media library and the gallery stayed empty on any host. The hook shield of 3.3.9/3.3.10 and the gallery_id compensation were guarding against the wrong killer – the exception came from the connector itself, not from another plugin’s hooks.
- Changed: the product gallery is now written exactly like the featured image – a direct write of the canonical meta _product_image_gallery (comma-separated attachment IDs; the exact storage WooCommerce reads on every product load and its own images metabox writes), through the new galIds()/galAdd() helpers. No $p->save(), no WooCommerce save chain, no hook dependency – works on any host and any WooCommerce version. All five gallery windows keep their hook shield and try/finally; a rare meta-write failure is still reported honestly through the attach-ok contract and compensated with gallery_id (which now really works).
- No breaking changes: REST routes, auth and payload format stay identical to 3.3.10; platforms written for 3.3.8-3.3.10 keep working unchanged.
3.3.10
- Fixed: “the featured image is set, but the product gallery never updates” – the gallery append runs through WooCommerce’s own product save chain ($p->save() triggers woocommerce_update_product, save_post_product, wp_insert_post, transition_post_status, deleted_transient and the meta hooks), while the featured image only writes meta. The 3.3.7 hook shield covered the sideload window only, not the assignment window, so a broken callback of another plugin on that save chain throws exactly there; since the 3.3.8 attach-first contract that exception is caught and returned as meta=”attach-ok” – but the platform honored that contract only for featured images, so for gallery images the failure stayed invisible: the image landed in the media library, the platform counted a success and the gallery stayed empty. The whole assignment window (featured/gallery/transients) now runs inside the same temporary hook shield with try/finally – a broken hook can no longer kill the assignment on any host, and the meta filters are shielded too so no plugin can silently veto the meta write by returning false.
- New: the product-update route POST /products/{id} now also accepts gallery_id (append an existing attachment to the product gallery, deduplicated, inside the same hook shield, mirrored after thumbnail_id). The platform uses it as a tiny compensation request when the gallery assignment of an uploaded image is reported as attach-ok, so the gallery can no longer silently stay empty. The response gains a gal=1 field when the gallery assignment was actually performed.
- No breaking changes: REST routes, auth and payload format stay identical to 3.3.9; platforms written for 3.3.8/3.3.9 keep working (the product-update response only gains the informational gal field when a gallery assignment was actually requested).
3.3.9
- Fixed: the real killer of every upload since 3.3.6 is found and removed – the essential-first rewrite of 3.3.6 called wp_handle_sideload() with an inline array literal as its first argument, but that core function takes the file array BY REFERENCE (&$file), so PHP aborts every call with “wp_handle_sideload(): Argument #1 ($file) could not be passed by reference” before any image data is touched. That is exactly why featured images, gallery images and even the 1×1 probe all died in well under a second on any PHP 8 host regardless of memory/time limits (the raw exception the platform’s probe details finally exposed: class-wcfs-rest.php:665), and why no memory, hook or route theory fixed it. The array now lands in a variable first and is passed normally – plain PHP semantics, no host-specific tuning involved; the hook shield, the immediate payload registration and the product-update images[] fallback all keep working on top of it.
- No breaking changes: REST routes, auth and payload format stay identical to 3.3.8.
3.3.8
- Fixed: the remaining fatal-class failures on the product-images route can no longer turn a completed upload into a reported failure. Full archaeology of the field reports (the 158/159-byte fatal-reporter bodies with HTTP 200, always in under 0.3 seconds) shows the death happens in the window AFTER the attachment is created but BEFORE the success payload is registered – i.e. in the thumbnail/gallery/transient assignment steps, not in the upload itself; the attachment was already sitting in the media library while the platform heard “failed” and re-sent the same image. The route now registers its success payload the moment the attachment exists and runs the thumbnail/gallery/transient assignment inside try/catch – if any of those steps throws or fatals, the answer is still a success answer (meta=”attach-ok”) carrying the real cause, and the platform compensates the thumbnail assignment with a tiny separate request.
- New: the product-update route POST /products/{id} now also accepts images[] (the same inline sideload sequence the product-creation route used before the two-phase split – the exact path that kept working on the affected host) and thumbnail_id (assign an existing attachment as the featured image, inside the same temporary hook shield). This gives the platform a generic fallback path for every fatal-class killer of the per-image route – no host-specific tuning involved.
- Changed: the media route registers its success payload right after the attachment is created too, and the URL lookup is guarded, so the 1×1 probe and in-article images can no longer be reported failed after a successful attach.
- No breaking changes: REST routes, auth and payload format stay compatible; platforms written for 3.3.7 keep working (the product-update response only gains informational images/feat/image/error fields when images or a thumbnail assignment were actually requested).
3.3.7
- Fixed: the 1×1 probe image that succeeded on 3.3.5 started failing with an HTTP 500 carrying a PHP exception while the real product images still died with the fatal reporter’s 158-byte answer – the killer is on the host’s attachment-hook surface (a broken callback of another plugin on add_attachment/save_post/the metadata filters, which throws or fatals exactly when an attachment is created). No plugin may be allowed to kill this plugin’s essential upload step: the two essential steps (wp_handle_sideload + wp_insert_attachment) now run inside a temporary hook shield – all callbacks of the affected hooks are removed for that step and restored immediately afterwards with try/finally (also on failure paths). WooCommerce size/metadata generation (inline attempt and wp-cron) is shielded the same way, so a broken optimizer hook cannot kill the sizes either. Side effect limited to this plugin’s own attachments: immediate reactions of other plugins (instant optimization) are skipped there – optimization/sizes were already deferred to wp-cron.
- New: “Image processing health” panel on the connector settings page – PHP memory/time limits, GD (JPEG) and Imagick availability, writability of the uploads and temp directories, the list of active image-optimizer plugins (up to 10), and the last upload failure / last recorded PHP fatal with their dates. The same environment data plus the last failure records are served via the GET /site-info route so support can read them without server log access.
- Changed: when the temporary image file cannot be written, the raw PHP reason (up to 120 characters, e.g. permission denied or disk full) is appended to the error message shown to the platform.
- No breaking changes: REST routes, auth and payload format stay compatible; platforms written for 3.3.6 keep working (the /site-info response only gains informational fields).
3.3.6
- Fixed: the last field failure showed a tiny ~300 KB image dying with “PHP Fatal” in 0.3 seconds at every resize level (2048/1200/800) while the 1×1 probe upload succeeded – so it was neither memory nor execution time: a deterministic killer on that host’s attachment/metadata path (e.g. a broken hook of an image-optimizer plugin or a missing function inside the metadata generation chain). The upload request now does only the two essential steps of media_handle_sideload – wp_handle_sideload (move the file into uploads) and wp_insert_attachment (create the attachment row) – both plain file/database operations that do not decode the image, so no image-processing killer on the host can fatal the upload anymore. WooCommerce size/metadata generation (the classic crash point) leaves the request entirely: a new wp-cron event (wcfs_genmeta) generates it about a minute later (the wp-cron runner is proven alive on affected hosts), and every image route still attempts it inline at the very end – if PHP dies there, the shutdown reporter answers with the route’s own SUCCESS payload plus meta=”fatal-deferred” and the real fatal detail, because the attachment already exists: the platform records the image as uploaded, the store shows the original file immediately and the sizes arrive via wp-cron (with one 10-minute retry for transient limits).
- Changed: real fatal details are now also stored in the wcfs_last_fatal option for diagnostics.
- No breaking changes: REST routes, auth and payload format stay compatible; platforms written for 3.3.5 keep working (the success payload only gains an informational meta/error field).
3.3.5
- Fixed: uncaught PHP exceptions on the image routes were invisible to both WordPress’s fatal handler and the 3.3.4 reporter – error_get_last() never records an uncaught exception and WordPress prints no error page for it, so the site answered HTTP 500 with an empty body and the platform could only show “WordPress error: HTTP 500” with no cause at all. The four routes that touch images (articles, media, product creation, product images) now catch every uncaught Throwable: a product-image failure answers the route’s own contract (image=0 + the real exception message, so the platform can translate it to Persian and retry a lighter version), and the other three answer with the same WP_Error shape their ordinary failures already use.
- Changed: the fatal reporter now also covers E_USER_ERROR (WordPress treats it as a fatal) and, when memory is truly exhausted at shutdown, emits a minimal static JSON instead of an empty response.
- No breaking changes: REST routes, auth and payload format stay compatible; platforms written for 3.3.4 keep working.
3.3.4
- New: PHP fatal reporter for image routes. When PHP dies during image processing (memory or execution limit on small hosts, or any other fatal), WordPress returned its generic “critical error” HTML page and the platform could only show “WordPress error: A critical error occurred” with no real cause. The articles, media, product-creation and product-images routes now buffer their output and a shutdown handler replaces that HTML with the connector’s own JSON (marker “wcfs”) carrying the real fatal message, file/line and peak memory usage. The platform translates it to Persian and automatically retries the image with a smaller version.
- Changed: oversized product photos (more than 12 megapixels, e.g. supplier photos) are downscaled to at most 2048 pixels before the attachment is created and WooCommerce generates its image sizes – one light decode instead of decoding the full raw photo in GD, which exhausted the memory limit on shared hosts. The memory limit is raised (never lowered) and the execution limit set to 120 seconds for the sideload.
- No breaking changes: REST routes, auth and payload format stay compatible; platforms written for 3.3.3 keep working.
3.3.3
- New: REST route POST /products/{id}/images – uploads one product image per request AFTER the product itself was created. Root cause fixed for “the panel said the product failed while it was actually published”: the previous single POST /products/new call carried every image (up to ~12 MB of base64) and sideloading all of them in one request could hit the PHP memory/execution limit on small hosts – WordPress returned its critical-error HTML page instead of JSON, the product stayed published but the platform marked the creation as failed and refunded the credits. Product creation is now fast (no images) and images arrive one small request at a time; a failed sideload answers HTTP 200 with image=0 and an error text instead of killing the response, so the “published” state is never broken by an image.
- New: GET /products now accepts optional search (product name) and since (only items from the last N minutes) parameters, used by the platform to recover an already-created product when the publish response was lost – no more false failures, no double refund, no duplicate products from platform-side retries.
- Changed: the per-product image cap in /products/new was raised from 6 to 10 to match the platform wizard; the new images route enforces the same cap.
- No breaking changes: REST routes, auth and payload format stay compatible; platforms written for 3.3.2 keep working and only use the new route when they know it.
3.3.2
- Fixed: additional product images now land in the WooCommerce product gallery. The wizard payload already sent every image, and the connector sideloaded them all, but only the featured image was attached (set_post_thumbnail) – the gallery meta (_product_image_gallery) was never written, so the product page showed a single image. All non-featured images are now collected and set via set_gallery_ids; if no image is flagged as featured, the first one becomes the featured image. The featured image itself stays out of the gallery (standard WooCommerce behavior).
- No breaking changes: REST routes, auth and payload format are untouched; platforms written for 3.3.1 keep working.
3.3.1
- Fixed: front.css / front.js are now always enqueued (while the connector is enabled) instead of only on managed single posts. On some sites the old is_singular(‘post’) + post-meta check silently failed (page-builder themes, altered main queries, non-post display), so the article styling never loaded. The enqueue now also runs at priority 999 on wp_enqueue_scripts — the same fix site owners had to paste into their theme’s functions.php. You can remove that manual snippet after updating: the plugin now does it itself.
- New: table-of-contents links in SEOFLY articles smooth-scroll (fast) to the matching heading — in Firefox the native #sec-n anchor jump often did nothing; the scroll now works consistently in every browser and respects sticky headers / the admin bar (scroll-margin-top).
- New: long table-of-contents get a fixed height (320px) with a vertical scrollbar instead of pushing the whole article down.
- New: the FAQ section of articles renders as styled accordions (details/summary, same pattern as the in-article accordions); legacy articles built with h3+question pairs are converted to the same accordion on the fly by front.js — no content is rewritten in the database.
- No breaking changes: all REST routes, auth and meta behavior are untouched; platforms written for 3.3.0 keep working.
3.3.0
- New: REST route GET /terms — lists every public taxonomy on the site (WooCommerce product categories, post categories, tags and any custom taxonomies) with up to 200 terms each, plus a per-term flag showing whether SEO meta (Yoast or Rank Math) already exists. Used by the new “دستهبندیهای وردپرس” target of the SEOFLY Improve SEO page.
- New: REST route POST /terms/{id} — writes the SEO of a category/term: archive description plus meta title, meta description and focus keyword. Both meta sets are written (Yoast: wpseo_title / wpseo_desc / wpseo_focuskw term meta keys, Rank Math: rank_math_title / rank_math_description / rank_math_focus_keyword), so it works whichever SEO plugin the site uses. Existing posts and products are untouched.
- No breaking changes: older SEOFLY platform builds keep working; all new routes use the same signature auth as every other route.
3.2.2
- New: Persian (fa_IR) translation is bundled in the plugin’s /languages folder — the settings screen, connection messages and REST errors now appear in Persian on fa_IR sites.
- New: master switch in the settings (“Enabled”). Turning it off pauses the connector without deactivating the plugin: every REST route answers with a clear “disabled” message (HTTP 503) instead of publishing, the hourly health heartbeat stops, and the front-end meta/FAQ behaviors are skipped. Settings and connection data are kept; turn it back on anytime.
- The Client ID and Secret field labels (and the page heading) are now translatable strings.
3.2.1
- Fixed (plugin review feedback): every REST route now declares its permission_callback literally inside its own register_rest_route() call. The routes previously shared one callback array via a PHP variable, which automated scanners could not resolve and reported the permission_callback as missing. No runtime behaviour change: all 13 routes were and are protected by the same auth() permission callback — a server-to-server check (HMAC-SHA256 signature over client ID + timestamp + method + route + body, 5-minute timestamp window, replay protection) that gates every read and write for the connected SEOFLY account only.
3.2.0
- New: per-attribute variation flag. The SEOFLY panel now sends variation=true|false for every product attribute (the new “متغیر” toggle next to each attribute name in the New Product wizard). Only flagged attributes drive variations (each with its own price and stock); unflagged ones are saved as plain, visible product attributes in the product definition.
- Changed: in variable products, attributes without the variation flag are no longer marked “used for variations”, so the product page shows dropdowns only for the attributes that really build variations.
- Compatibility: payloads from older SEOFLY panel builds always send variation=true, so behaviour is unchanged with them.
3.1.0
- New: the SEOFLY panel’s “Edit Variations” dialog now shows exactly two fields per variation (price and stock). Stock semantics per variation: a number enables stock management with that quantity (0 = out of stock), clearing a previously saved quantity turns stock management off and marks the variation fully in stock.
- New: POST /products/{id} (panel edit) accepts manage_stock=false per variation entry to release WooCommerce stock management and set the variation fully in stock.
- Fixed: the panel previously dropped the typed stock quantity for variation edits (field mismatch between panel and REST payload); quantities now save correctly.
3.0.0
- Renamed to “Robosolo Connector for SEOFLY” so the third-party relationship is clear from the title, as requested by the WordPress.org review; the text domain now matches the robosolo-connector-for-seofly slug in every file (translations move to translate.wordpress.org automatically).
- New: REST route GET /pcat — lists the store’s WooCommerce product categories (product_cat), so the SEOFLY “New Product” wizard gets a dedicated category step that reads the real categories of the user’s own site.
- New: POST /products/new accepts categories[] (product_cat term IDs, with name fallback); missing terms are created idempotently and the product is assigned to them.
- Changed: stock is now optional when creating products. When no stock quantity is sent, the product is published fully “in stock” and WooCommerce stock management is turned off for it (no quantity tracking); when a quantity is sent, stock management works exactly as before. Applies to simple products and to each variation independently.
- Internal: no breaking changes; older SEOFLY platform builds keep working.
2.9.0
- New: REST route GET /attributes — lists the store’s global product attributes (pa_*) with their terms, so the SEOFLY “New Product” wizard offers the store’s own predefined attributes (with a loading indicator) instead of free-text names.
- New: REST route POST /attr — creates (or returns an existing) global attribute with its terms, idempotent; the attribute lands in the store’s filter widgets exactly as the user typed it.
- New: REST route GET /products/{id}/variations — reads a variable product’s variations (price, stock quantity, stock status) live from the product itself for the panel’s single-edit variation list.
- Improved: POST /products/{id} now accepts price_op (increase/decrease by amount or percent, applied against the real WooCommerce price with Toman rounding — increase rounds up, decrease rounds down, step 10/100/1000 by magnitude), stock_status (“outofstock” makes the product fully out of stock without touching its numeric stock) and variations[] (per-variation regular_price / stock_quantity / stock_status). The response now returns the final price and stock status so the platform cache stays accurate.
- Improved: GET /products now includes the product type (simple/variable) — the platform excludes variable products from bulk editing.
- Internal: no breaking changes; older SEOFLY platform builds keep working.
2.8.0
- New: REST route POST /products/new — create WooCommerce products (simple or variable) straight from the SEOFLY “New Product” wizard, with images (base64, featured flag), per-variation price/stock and SEO meta (Yoast/Rank Math compatible).
- Improved: POST /products/{id} now accepts name, regular_price and stock_quantity for single/bulk editing from the SEOFLY panel (simple products; variable products are managed at variation level).
- Internal: hardening only; no breaking changes.
2.7.0
- New REST endpoint POST /seofly/v1/cat: creates (or returns an existing) WordPress category by name, so the SEOFLY article pop-ups can offer a “+” button that adds a brand-new category straight to the user’s site and publishes the article in it. Signed with the same HMAC handshake as every other endpoint; category creation is idempotent (a same-name category is returned instead of duplicated).
- No schema or option changes; downgrade-safe — older SEOFLY platform builds simply never call the new endpoint.
2.6.0
- The /products sync now also reports each product’s real WooCommerce stock status and its main image URL, so SEOFLY can offer only in-stock products inside generated articles and render product boxes/carousels with the real product image.
- front.js now wires the arrows of the related-products carousel; the carousel itself is a scroll-snap strip that also works by touch without JavaScript. front.css gains styles for the related-articles quote box, the single product box and the carousel.
2.5.1
- Featured-image delivery is now fail-proof and transparent: every upload failure (size, format, permissions, media-library error) is reported back to the SEOFLY platform with a concrete reason instead of failing silently, and the article page in SEOFLY shows exactly why the image is missing.
- The connector now also accepts a featured image sent as a URL by platform builds that recorded an older plugin version, so the post thumbnail is set regardless of the delivery contract.
- The hourly heartbeat now carries the plugin identity (WordPress/plugin version, active SEO plugin, WooCommerce) so the platform refreshes its records without a manual re-connection.
2.5.0
- SEOFLY articles can now carry accordions and copyable prompt/code blocks as native Gutenberg blocks: the platform wraps them in Custom HTML blocks () with details/summary accordions and a copy button next to every code block.
- Block comments are preserved on delivery (wp_kses_post removes HTML comments, so they are masked before sanitizing and restored after the post is saved; the visible HTML itself still passes through wp_kses_post).
- The sanitizer allowlist for this signed platform content now also keeps details/summary, the copy-button markup and code blocks with their styling classes; front.js wires the copy buttons (clipboard API with a textarea fallback) and front.css styles accordions, buttons and code blocks.
2.4.0
- The plugin is now named “Connector for SEOFLY” to make clear it is an integration for the SEOFLY platform.
- All declarations, hooks and stored data now use the unique “wcfs_” prefix; settings, post data and scheduled events migrate automatically from earlier direct-download builds.
- Removed bundled translation files in favor of translate.wordpress.org; the plugin remains translation-ready.
2.3.0
- New REST endpoint /media: the platform can upload in-article images to the WordPress media library before publishing (posts then serve those images from the site itself, not from the platform server).
- Shared hardened sideload core for featured image and in-article images (unique file names, alt text stored).
2.2.0
- Connection monitoring: a signed hourly heartbeat (WP-Cron) reports the site as reachable to your SEOFLY dashboard.
- Your SEOFLY dashboard now shows the last successful contact for each site and warns you before a scheduled publish on an unreachable site can fail.
- No change to article delivery, REST routes or stored data; the heartbeat sends an empty body and is unscheduled on deactivation.
2.1.0
- Security hardening: nonce-verified admin notices, fully unslashed and sanitized input handling.
- Replaced discouraged functions with WordPress core APIs (wp_delete_file, delete_post_meta_by_key) and removed error-suppression operators.
- Added translators comments for all placeholder strings and moved to the recommended translation loading.
- Readme cleanup: limited to 5 tags and shortened the short description to 150 characters.
2.0.0
- Complete rewrite: new option prefix, WooCommerce product SEO updates, Yoast SEO and Rank Math meta support, FAQPage JSON-LD schema, automatic featured image upload, HMAC timestamp and replay protection, translation-ready interface, uninstall data cleanup.
1.0.0
- Initial release.