Skip to content

1.1.0 - WordPress.org review compliance

Choose a tag to compare

View all tags
@nolderoos nolderoos released this 14 May 12:15
1.1.0
a0d2fcc

OpenTrust 1.1.0 implements every fix requested in round 1 of the WordPress.org plugin review. It ships no new features. Every change is compliance, security hardening, or internal correctness work, and the plugin is now ready for directory resubmission.

Compliance and hardening

  • Custom post type prefix. The five custom post types were renamed from the ot_ prefix to opentr_ (opentr_policy, opentr_certification, opentr_subprocessor, opentr_data_practice, opentr_faq) to meet the WordPress.org four-character prefix rule. An automatic database migration rewrites existing content on the first load after upgrade. See "Upgrade notes" below. (#21)
  • Output escaping. All output is now escaped at the point it is echoed, across the public trust center, the AI chat, and every admin screen. Every phpcs:ignore escape suppression has been removed. There is no visible change to rendered pages. (#19)
  • Asset loading. Front-end and chat CSS and JavaScript are now registered and enqueued through the standard WordPress asset API with real file URLs instead of being inlined, so browsers can cache them between page loads. (#11)
  • File uploads. Uploaded import archives are now processed through the standard wp_handle_upload() pipeline, which applies core MIME-type validation and the upload_mimes filter chain. (#17)
  • Outbound HTTP. The AI chat streaming request now goes through the WordPress HTTP API (wp_safe_remote_post() with the documented http_api_curl hook) instead of a raw cURL call. Streaming, the Stop button, the host allowlist, and SSL verification are unchanged. (#15)
  • Review solicitation. The review link in the admin footer and milestone notice now points to the plugin's neutral reviews page, and the five-star wording has been removed, in line with WordPress.org guidelines. (#9)

Fixes

  • Removed an unused require of a WordPress core admin file from the import routine. (#13)

Upgrade notes

  • This release ships a v3 to v4 database schema migration. On the first page load after upgrading, the plugin rewrites wp_posts.post_type for every existing policy, certification, subprocessor, data practice, and FAQ from the old ot_* slugs to the new opentr_* slugs.
  • The migration is automatic, idempotent, and crash-safe. Post IDs, content, meta, revisions, policy version history, and WPML or Polylang translation links are all preserved.
  • A database backup before upgrading is recommended, as with any schema migration.
  • If you maintain custom code (theme snippets, companion plugins) that references the old ot_* post type slugs directly, update those references to the new opentr_* slugs. There is no compatibility shim.
  • Content archives exported by OpenTrust 1.0.x still import correctly. The importer remaps legacy slugs automatically.

Install

Download opentrust-1.1.0.zip below and install it through Plugins, Add New, Upload Plugin, or extract it into wp-content/plugins/.

Full Changelog: 1.0.1...1.1.0

Assets 3
Loading