4WP Drive

Import Google Docs, Markdown, and Word from Google Drive, or Markdown packages from GitHub, into WordPress drafts — or update existing posts and pages from the admin Incoming screen.

Plugin page: 4wp.dev/plugin/4wp-drive/ · WordPress.org · 4wp.dev · GPL-2.0-or-later

Current stable: 1.7.0

1. Writers drop articles into a source incoming/ folder (Drive or a GitHub repo).
2. 4WP Drive syncs them into the admin Incoming queue (source tabs + workspace).
3. Editors Preview, pick Content language (Polylang, when needed), then Create new draft, Update existing post, or Reject.
4. On import, the package moves to published/ (same tree). Reject goes to failed/.
5. Analytics records each import (drafts and published).

Front-matter lines before a separator (--- or =====) map to post fields (title, slug, categories, SEO, etc.). The rest becomes Gutenberg post content.

Patterns, family plugins, placing images in the article, wrap pin, and Analytics that actually lists imports.

• From Incoming: drag a package image from the tree onto the preview, or click the file, pick L / C / R, then click a paragraph.
• Writes [image:hero.png left] (optional center / right). Markdown ![alt](hero.png) in the same folder becomes the same marker.
• Featured image is still Incoming (cover / hero / first file), not this marker.

• Tabs: Overview, Core Block, Integrations Plugins, Custom Blocks (soon).
• Overview front-matter sample is the live Settings field map, with a link to Settings → Documentation.
• Core Block — always imported: headings, paragraphs, lists, tables, quotes, code, separators, package-folder images.

Drive keeps the list in src/Blocks/Family_Plugin_Catalog.php. Add a sibling with a new row there, or the filter forwp_drive_family_plugins. Cards show even when the plugin is off: Get plugin / Activate. Wrap titles become editable after activate.

• 4WP FAQ — H2 FAQ (any language; aliases in Patterns) + H3 question / body answer → forwp/faq accordion.
• 4WP SEO Helper (TechArticle) — Goal, Context, Steps, Common mistakes. Map: tech-article (or TechArticle) in front-matter, heading aliases, or wrap pin in Incoming.

Click a wrap in the toolbar, then a heading or paragraph to wrap that section. × unwraps. Selected pin is highlighted; counts show on the pin (FAQ-1, Goal-1).

Import destination on one row. Keep document fonts is compact. Plugin tags stay sticky. Tree load no longer dies on a duplicate const marker.

Drafts and published. Columns: date/time, type, post ID/type, status, create vs update, details. No history ID. Restore to incoming is removed from this screen (it moved the storage package, not the WordPress post).

Incoming editor UX and Google Docs fidelity.

• The queue is a lazy folder tree: one Drive/GitHub level at a time, not a recursive dump of the whole incoming/ tree.
• Nested folders stay closed until expanded. incoming / published / failed open when they have child folders.
• Expand fetches children (including shortcuts / shared drives). Empty folders no longer stay empty if Drive has files.

• Classic tables import as core/table. Docs wraps cells in <p>; those paragraphs no longer leak into the post body.
• Default: strip Google Arial/11pt so the theme fonts win. Import checkbox Keep document fonts when you need the Doc’s typeface.

• Image files in the tree get an image icon.
• Click the name: workspace preview (no Import / Reject).
• Open-outside icon: Drive file view or GitHub blob.

• Sync cooldown (“already ran recently”) is yellow, not red.
• Export errors: N is from the last Sync: Google could not export that many articles as HTML (Docs export API, Word conversion, or unsupported mime). Click the chip for names and messages. It is not a failed WordPress import.

Progress since 1.4.0 (Inbox dashboard). This is the release cut.

• Screen name Incoming (same slug as the old Inbox).
• Source tabs: Google Drive and GitHub are live. OneDrive / Dropbox stay on the roadmap.
• Status bar: connection, last sync, ready count, Open folder, Sync.
• Package folders: one article = a subfolder with a document + png/jpg images.
• File to import when a folder has more than one document (Markdown preferred).
• Inline images from the article folder: Google Doc paragraph [image:hero.png] (optional left / center / right). Markdown ![alt](hero.png) becomes the same marker. Exact filename. Featured image is Incoming (cover / hero / first file), not this marker.
• Image pin in preview: pick a package image, set alignment, click a paragraph.
• Import still writes core blocks (headings, paragraphs, lists, quotes, code, images).

• Same incoming/ → published/ / failed/ folder contract.
• Articles: Google Doc, Markdown (.md / .markdown), or Word (.docx). Not Drive shortcuts.
• Markdown is preferred when several article files sit in the same package folder.

• Connect under Settings → Storage sources → GitHub: owner, repository, branch, incoming path (default incoming), personal access token.
• Scans incoming/ for Markdown packages (subfolder with .md + images, or a flat .md).
• After import: files move to published/ (Git commit via Contents API: new path + delete old path). Reject → failed/.
• 4WP Drive only talks to the configured owner/repo. A classic PAT with repo can still access all repos the GitHub user can reach. Prefer a fine-grained token limited to this repository, Contents: Read and write.
• Token is stored encrypted. GitHub shows a classic token only once (ghp_…).

Example package:

incoming/
  4wp-drive-plugin-overview/
    article.md
    cover.png
published/          ← after import, same folder tree
  4wp-drive-plugin-overview/
    article.md
    cover.png

• Menu: 4WP Drive → Analytics.
• Separate table wp_forwp_drive_import_history (created on the next admin load — no plugin reactivation required).
• Each successful import stores: source (Drive / GitHub), date, post ID + post type, folder alias, site alias (slug), incoming path, published path, create vs update.
• Restore to incoming moves the package from published/ back to incoming/ (Drive parent change, or GitHub commit). Then Incoming → Sync to see it in the queue again.
• Restore does not rebuild Markdown from WordPress. The source package is the source of truth.
• History starts from the next import after 1.5.0. Older imports are not backfilled.

• Polylang language picker at import (1.2.0). WPML planned.
• Update existing post (1.1.0).
• Patterns (FAQ / accordion / core image markers) (1.3.0).
• Encrypted OAuth / PAT in the database.

• WordPress 6.4+ (tested up to 7.1)
• PHP 7.4+
• Drive: Google Cloud project, Drive API, OAuth 2.0 Web client
• GitHub (optional): PAT with access to one repo (fine-grained recommended)
• Polylang (optional) — multilingual import

1. Activate the plugin.
2. 4WP Drive → Settings → Storage sources — paste Client ID & Secret → Save credentials.
3. Connect Google Drive (register the redirect URI from Documentation in Google Cloud Console).
4. Set root folder ID → Save & create subfolders (incoming, published, failed).
5. Incoming → Google Drive tab → Sync → preview → import.

1. Create a repo with an incoming/ folder and one package subfolder (Markdown + images).
2. Settings → GitHub — owner, repository, branch, incoming path, PAT → Save GitHub settings.
3. Incoming → GitHub tab → Sync → preview → import.
4. Check Analytics after import; use Restore to incoming if you need the package back in the queue.

Optional wp-config.php constants (Drive):

define( 'FORWP_DRIVE_GOOGLE_CLIENT_ID', '…' );
define( 'FORWP_DRIVE_GOOGLE_CLIENT_SECRET', '…' );
define( 'FORWP_DRIVE_OAUTH_REDIRECT_URI', '…' ); // local loopback if needed

wp forwp-drive sync

composer install
composer test
composer run lint

• PHP source: src/ (PSR-4 ForWP\Drive\)
• Family plugins for Patterns: src/Blocks/Family_Plugin_Catalog.php (forwp_drive_family_plugins)
• Admin UI: plain JS in assets/ (no npm build)
• Tests: tests/unit/
• History schema: src/Database/Schema.php (forwp_drive_documents, forwp_drive_import_history)

WordPress.org assets: see .wordpress-org/assets/README.txt.

Release announcements (Google, social, newsletter): docs/releases/ — not shipped in the wp.org ZIP. Latest: 1.7.0.md.

• Google OAuth 2.0 — administrator authorization for Drive
• Google Drive API — list, export, and move files during sync/import
• GitHub REST API (api.github.com) — list/read Contents and commit moves when a PAT is saved (administrators only)

See readme.txt → External services for WordPress.org detail.

Overview and FAQ: 4wp.dev/plugin/4wp-drive/

GPL v2 or later. See LICENSE if present or plugin header.