Brasth Document Sync for Google Docs
| 开发者 | canvilled |
|---|---|
| 更新时间 | 2026年6月22日 20:34 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Brasth Document Sync for Google Docs helps editorial teams use Google Docs as the source of truth while publishing clean WordPress content. Site owners provide their own Google OAuth web client, each WordPress user connects their own Google account, and authorized users can browse accessible Google Docs, link a document to a post or page, and sync content into WordPress.
The plugin exports Google Docs as HTML ZIP packages, imports embedded images into the WordPress Media Library, rewrites image URLs, sanitizes the resulting HTML, and converts common document structures to Gutenberg block markup. If Google blocks a large HTML ZIP export, Brasth Document Sync retries through the Google Docs API fallback before changing post content.
Features include:
- Self-managed Google OAuth setup wizard.
- Server-side Google Drive document browser for My Drive and shared drives.
- Advanced Google Docs URL and raw file ID linking.
- Background sync through WP-Cron with source status and diagnostic logs.
- One-way Google Docs to WordPress sync for posts, pages, and enabled public custom post types.
- Media import for images exported from Google Docs.
- Gutenberg block markup for common headings, paragraphs, lists, tables, and images.
- Uninstall cleanup for settings, encrypted user tokens, and scheduled events.
- Google OAuth 2.0 endpoints, to authorize a user's Google account and refresh access tokens.
- Google Drive API, to list visible Google Docs, shared drives, folders, document metadata, and HTML ZIP exports.
- Google Docs API, to read document structure when the large-document fallback is needed.
- Google Privacy Policy: https://policies.google.com/privacy
- Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
- Google APIs Terms of Service: https://developers.google.com/terms
安装:
- Upload the
brasth-document-sync-for-google-docsfolder to/wp-content/plugins/, or install the plugin ZIP through Plugins > Add New > Upload Plugin. - Activate Brasth Document Sync from the WordPress Plugins screen.
- In Google Cloud, create or select a project.
- Enable the Google Drive API and Google Docs API.
- Configure the OAuth consent screen for the WordPress site users.
- Create an OAuth 2.0 Web application client.
- Add the authorized redirect URI shown in the Brasth Document Sync setup wizard.
- In WordPress admin, open Brasth Document Sync and save the OAuth client ID and client secret.
- Connect a Google account, browse or paste a Google Doc, and link it to a WordPress post or page.
屏幕截图:
常见问题:
Does Brasth Document Sync provide a hosted Google connector?
No. This release uses self-managed Google OAuth. The site owner supplies the Google Cloud project and OAuth web client.
Which Google APIs are required?
Enable both the Google Drive API and Google Docs API in the same Google Cloud project used by the OAuth client.
Which Google OAuth scope is used?
Brasth Document Sync uses https://www.googleapis.com/auth/drive.readonly so connected users can browse and sync Google Docs their account can read.
Does sync delete WordPress posts?
No. Sync updates the linked post content, and uninstall never deletes synced posts. Full post-meta cleanup is available only through the documented full-uninstall constant or filter.
What happens on low-traffic sites?
Manual and scheduled background syncs use WP-Cron. Low-traffic sites or sites with DISABLE_WP_CRON should configure a real server cron job that calls wp-cron.php.
Are Google OAuth secrets and user tokens stored safely?
Brasth Document Sync encrypts the site OAuth client secret and per-user Google tokens with WordPress salts before storage. Rotating WordPress salts invalidates those credentials and users must reconnect.
更新日志:
1.0.5
- Added Elementor sync support (opt-in via settings).
- Added per-post Elementor/block sync toggle in the post sync meta box.
- Synced Elementor posts use native Elementor widget layouts with container or section/column wrapping.
- Scoped Elementor CSS cache invalidation to the synced post, with global cache clear as fallback.
- Improved admin UI/UX for Sources, Logs, and Drive Browser.
- Fixed Sources table row tag rendering and layout.
- Fixed color and high-contrast accessibility issues.
- Fixed admin asset enqueuing on Sources and Logs pages.
- Added WordPress.org screenshot assets and readme sync lint.
- Hardened the build pipeline and installable ZIP artifact layout.
- Hardened release metadata, WordPress.org readme compliance, CI checks, and admin i18n coverage.
- Updated WordPress.org listing artwork and directory tags.
- Aligned plugin version metadata for the 1.0.1 GitHub release package.
- Initial WordPress.org-ready release.
- Added self-managed Google OAuth setup.
- Added Google Drive document browser and advanced URL/file ID linking.
- Added one-way Google Docs to WordPress sync for posts, pages, and enabled public custom post types.
- Added HTML ZIP import, image sideloading, Gutenberg block conversion, background sync, and diagnostic logs.