| 开发者 | ocmdeveloper |
|---|---|
| 更新时间 | 2026年8月6日 15:57 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
oc-bridge/v1) to fetch menus, SEO metadata, widgets, and related content, and renders your WordPress blog inside the Magento storefront. When content changes in WordPress, the plugin sends a signed webhook to your Magento store so its cache is purged immediately.
Security:
X-OC-Bridge-Key header, compared with a timing-safe checkX-OC-Bridge-Signature header/blog URLs, renders posts in your storefront theme, and consumes these webhooks - is a separate commercial extension from Orange Collar Media. You do not need it to install, activate, or use this plugin.
Every endpoint is plain REST returning JSON, so any client that can send an HTTP header can consume it. Magento is simply the client it was built for.
ocmlabs-content-bridge-for-magento folder to /wp-content/plugins/No. The plugin activates and runs on any WordPress site, and its endpoints return plain JSON to any authenticated client. It was built for one purpose though: feeding WordPress content to a Magento 2 storefront. Without a Magento store, or another consumer of the API, it does nothing user-visible. The endpoint reference documents every response shape if you want to build your own client.
No. Every custom endpoint under the oc-bridge/v1 namespace requires the API key in the X-OC-Bridge-Key header. Requests without the correct key receive a 403 response. Core WordPress REST endpoints are unaffected by this plugin.
Yoast SEO and Rank Math are detected automatically. If neither is active, the SEO endpoint falls back to sensible defaults built from the post title and excerpt.
Yes. When ACF is active, the plugin injects ACF field data into post and page REST responses for authenticated bridge requests.
Deleting the plugin removes all of its stored settings (API key, webhook URL, and webhook secret). It stores nothing else.