| 开发者 | brightagbomado |
|---|---|
| 更新时间 | 2026年5月28日 10:52 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp/v2/media REST endpoint, authenticated via the Application Password you generated during Connect. No custom auth code on the upload path — WordPress core handles the authentication.wp-content/uploads/.htaccess file to allow RelahConvert.com to load your attachments for processing:
Header set Access-Control-Allow-Origin "https://relahconvert.com"
The block is bracketed by # BEGIN RelahConvert-PDF CORS and # END RelahConvert-PDF CORS markers so the plugin can clean up after itself. The rule is automatically removed when the plugin is deactivated.
If you also use the RelahConvert Image Tools plugin, both plugins manage their own marker blocks independently — they coexist without interfering with each other.
Features
relahconvert-pdf-office-tools folder to /wp-content/plugins/.No. All 16 tools process your file entirely in your browser using JavaScript libraries (pdf-lib, pdfjs, JSZip, mammoth.js, SheetJS, docx). Your PDF, Word, Excel, or PowerPoint file never leaves your device. The only time your file moves over a network is when you explicitly click "Send to WordPress" to upload the processed result back to your own Media Library. That goes only to your WordPress site, not to any third party.
Yes. All 16 tools are free to use. No account is required for processing. No watermark is added to output. Optional sign-in unlocks cloud-saved files and preference sync across devices.
No. The plugin uses WordPress's built-in Application Passwords, which are generated automatically when you click "Connect" on the plugin settings page. You never enter or manage an API key.
The plugin uses WordPress Application Passwords — the official WordPress mechanism for authenticating third-party app requests. When you click Connect in plugin settings, WordPress's built-in authorization screen asks you to approve the app once. WordPress generates an application-specific password (separate from your login password) and stores it. The plugin then uses that password to authenticate the upload via WordPress's native /wp/v2/media REST endpoint using HTTP Basic Auth. You can revoke access at any time via plugin settings (Disconnect) or directly from your WordPress profile under "Application Passwords".
Those conversions (and the reverse direction — PDF→Word, PDF→Excel, PDF→PowerPoint) require a server-side conversion engine because they can't be done reliably in the browser. RelahConvert.com offers them as free tools through a third-party conversion API. We've intentionally excluded them from this plugin so that everything in the plugin can guarantee "your file never leaves your device." If you need those conversions, visit RelahConvert.com.
Yes. The plugin adds action buttons in the media library modal used by both the Classic Editor and Block Editor.
After processing a file on RelahConvert.com, you can click "Send to WordPress" to upload the processed file directly to your WordPress Media Library without manually downloading and re-uploading.
Yes. On activation, the plugin adds a CORS header to wp-content/uploads/.htaccess to allow RelahConvert.com to load your attachments. The block is wrapped in # BEGIN RelahConvert-PDF CORS / # END RelahConvert-PDF CORS markers and is removed on deactivation.
Yes. The two plugins use distinct REST namespaces (relahconvert-pdf/v1 vs relahconvert/v1), distinct .htaccess marker blocks, and distinct transient key prefixes. They are designed to coexist.
/wp/v2/media REST endpoint with HTTP Basic Auth — no custom auth code on the upload path.authorize-application.php.