Genius Commerce

Àkọsílẹ̀ àwọn àyípadà

0.9.2

• Removed: the Custom CSS setting. Stores can add their own styling through the WordPress Customizer or Site Editor (Additional CSS). Previously saved custom CSS is no longer loaded on the storefront.
• Removed: the endpoint for deleting customers (DELETE /customers/{id} and the delete action of /customers/batch). Genius Commerce cannot delete WordPress users.

0.9.1

• Changed: “Tested up to” is declared only in readme.txt, no longer also in the plugin header.

0.9.0

• Changed: every option, transient, hook, AJAX action, nonce, constant and script handle now carries the genius_commerce_ prefix instead of gc_. Existing settings, the API key and the webhook secret move over automatically on the first page load after updating.
• Changed: the template filters are renamed to genius_commerce_delivery_product_template_args, genius_commerce_delivery_cart_template_args and genius_commerce_discount_price_template_args. Themes that hook into the old gc_ names must switch to the new ones.
• Changed: the scope refresh button on the settings page loads its script through the enqueued admin script instead of an inline script tag.
• Update: tested up to WordPress 7.1 and WooCommerce 11.1.

0.8.4

• Fixed: webhooks were never installed after coupling through the “Connect” button. That flow never stores a backend URL, so every call to Genius Commerce failed with “Backend URL not configured” and the “Test connection” button disappeared from the status overview. The plugin now falls back to the default backend URL and records it when connecting.
• Fixed: webhooks heal themselves. A store that is coupled but has no webhook secret or webhooks now fetches them on the next admin page load or the next authenticated call from Genius Commerce — no manual step after disconnecting and reconnecting.
• Fixed: webhooks created outside the admin screens are no longer owned by user 0, which made WooCommerce deliver empty payloads.

0.8.3

• Added: “Disconnect” button on the Connection tab — breaks the coupling with Genius Commerce (clears the local API key and webhook secret, removes the registered webhooks) behind a confirmation, so a store can reconnect after a backend-side disconnect without manually deleting a WP option (Story 4.11).

0.8.2

• Cleanup: uninstall routine wrapped in a function so its locals no longer land in the global scope.
• Cleanup: the five global plugin functions now carry the full genius_commerce_ prefix instead of the gc_ abbreviation.
• Cleanup: documented why the direct database reads in the sync endpoints are intentional and uncached — caching them would let a sync read stale data.
• Fix: corrected a misplaced phpcs annotation on the HPOS order-status query.
• Note: the gc_delivery_* and gc_discount_* template filters keep their names; renaming them would break themes that already hook into them.

0.8.1

• Compliance: added translators comments to the four translatable strings containing placeholders.
• Compliance: replaced unlink() with wp_delete_file() when cleaning up temporary image downloads.
• Compliance: the log redactor no longer exposes a constant-based bypass of its direct-access guard.
• Compliance: removed the Domain Path header and the load_plugin_textdomain() call — WordPress.org serves translations automatically since WP 4.6.
• Hardening: REMOTE_ADDR and X-Forwarded-For are now unslashed and sanitised before use in the IP allowlist.
• Hardening: the HPOS order table identifier is escaped with esc_sql().
• Update: tested up to WordPress 7.0.

0.8.0

• Security (high): batch endpoints for categories and brands now sanitise name/description inside create/update, closing a stored-XSS path that bypassed the route-level sanitize callbacks (audit #2).
• Security (high): sync-mapping now validates meta keys against the last Discovery scan (meta keys sanitised + allowlisted), preventing export of arbitrary post-meta such as other plugins’ secrets (audit #3).
• Security (medium): the generic taxonomy-terms route now applies the same exclusion list as the listing route, so a taxonomies.read scope can no longer read category/attribute term data (audit #4).
• Security (medium): Custom CSS is now filtered with safecss_filter_attr on save and output, stripping external url()/@import exfiltration vectors (audit #5).
• Security (low): remote image import now enforces an https + host/IP allowlist before download_url() across products/categories/brands/variations, hardening against SSRF (audit #6).

0.7.1

• Security (critical): the Customers REST endpoint no longer writes arbitrary user-meta keys. meta_data keys are now sanitised and role/session keys (wp_capabilities, wp_user_level, session_tokens, wp_* namespace) are rejected, closing a privilege-escalation path from a customers.write key to administrator.

0.7.0

• Added: one-click “Connect” button Ìtumọ̀ Yorùbá: – couples the store automatically without pasting an API key (Story 4.2)
• Added: token-exchange with shop-ownership proof via origin callback (Genius verifies the store by calling back into the plugin REST API)
• Update: manual API-key entry demoted to an advanced/fallback option

0.6.0

• Security: IP-allowlist enforcement on REST routes, with opt-in X-Forwarded-For support
• Security: scope enforcement on API keys with WP-transient cache and feature-flag cutover
• Security: PII redaction in request logging
• Fix: /debug and /system-info now return 403 FORBIDDEN_IP with a log line on an IP block (was a silent 401), consistent with the other REST routes

0.5.1

• Security: output escaping, input sanitization, XSS-hardened shortcodes, authenticated debug endpoint, prepared SQL, realpath template validation
• Update: WC tested up to 10.6, WordPress tested up to 6.9

0.5.0

• Enhancement: Internal link styling for rich text content blocks
• Enhancement: Expanded platform squeeze page content (800+ words)
• Enhancement: Contextual internal links across all key pages
• Improvement: FAQ accordion link styling with hover states

0.4.4

• Fix: Various bug fixes and improvements

0.3.5

• Fix: Sync mapping settings for meta fields with leading underscores (e.g., _weight) are now saved correctly

0.1.0

• Initial release