Merge pull request #171 from pantheon-systems/release_1.3.3

Release 1.3.3

Author: mklasen

.distignore

@@ -27,4 +27,8 @@
 /webpack.mix.js
 /SECURITY.md
 /.distignore
-/LICENSE
+/.eslint.config.js
+/.prettierrc
+/phpunit.xml
+/tsconfig.json
+/vite.config.ts

.gitignore

@@ -1,6 +1,6 @@
 node_modules/
 vendor/
-dist/
+assets/dist/
 bin/
 .DS_Store
 *.code-workspace

CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing
+
+The best way to contribute to the development of this plugin is by participating in the GitHub project:
+
+<https://github.com/pantheon-systems/pantheon-content-publisher-wordpress>
+
+## Workflow
+
+Development and releases are structured around two branches, `primary` and `release`.
+The `primary` branch is the default branch for the repository, and is the source and destination for feature branches.
+
+We prefer to squash commits (i.e., avoid merge PRs) from a feature branch into `primary` when merging and to include the PR number in the commit message. PRs to `primary` should also include any relevant updates to the changelog in readme.txt. For example, if a feature constitutes a minor or major version bump, that version update should be discussed and made as part of approving and merging the feature into `primary`.
+
+`primary` should be stable and usable, though possibly a few commits ahead of the public release on wp.org.
+
+The `release` branch matches the latest stable release deployed to [wp.org](wp.org).
+
+## Release Process
+
+1. Merge feature branches into `primary` with a PR. This PR should include any necessary updates to the changelog in readme.txt and README.md. Features should be _squash merged_.
+1. From `primary`, checkout a new branch `release_X.Y.Z`.
+1. Make a release commit:
+    * In `README.md`, `readme.txt`, `package.json, package-lock.json`, and `pantheon-content-publisher.php`, remove the -dev from the version number. For the README files. the version number must be updated both at the top of the document as well as the changelog.
+    * Add the date to the ** X.Y.X ** heading in the changelogs in README.md, readme.txt, and any other appropriate location.
+    * Commit these changes with the message "Release X.Y.Z"
+1. Push the release branch up.
+1. Open a pull request to merge `release_X.Y.Z` into release. Your PR should consist of all commits to main since the last release, and one commit to update the version number. The PR name should also be Release X.Y.Z.
+1. After all tests pass and you have received approvals from CODEOWNERs, merge the PR into `release`. A merge commit is needed in this case. **Never** squash to release.
+1. After merging to the `release` branch, a draft Release will be automatically created by the [`build-tag-release`](https://github.com/pantheon-systems/pantheon-content-publisher-wordpress/.github/workflows/build-tag-release.yml) workflow. This draft release will be automatically pre-filled with release notes.
+1. Confirm that the necessary assets are present in the newly created tag, and test on a WP install if desired.
+1. Review the release notes, making any necessary changes, and publish the release.
+1. Wait for the [_Release pantheon-content-publisher plugin to wp.org_ action](https://github.com/pantheon-systems/pantheon-content-publisher-wordpress/.github/workflows/wordpress-plugin-deploy.yml) to finish deploying to the WordPress.org plugin repository. If all goes well, users with SVN commit access for that plugin will receive an email with a diff of the changes.
+1. Check WordPress.org: Ensure that the changes are live on the plugin repository. This may take a few minutes.
+1. Following the release, prepare the next dev version with the following steps:
+    * `git checkout release`
+    * `git pull origin release`
+    * `git checkout primary`
+    * `git rebase release`
+    * Update the version number in all locations, incrementing the version by one patch version, and add the `-dev` flag (e.g. after releasing `1.2.3`, the new version will be `1.2.4-dev`)
+    * Add a new `** X.Y.X-dev **` heading to the changelog in readme.txt and README.md
+    * `git add -A .`
+    * `git commit -m "Prepare X.Y.X-dev"`
+    * `git push origin primary`
+1. Publish a public release note on [Pantheon's Documentation](https://github.com/pantheon-systems/documentation/) with the changelog and any notes.

Contributing.md

@@ -4,7 +4,7 @@
 **Tags:** pantheon, content, google docs  
 **Requires at least:** 5.7  
 **Tested up to:** 6.8.1  
-**Stable tag:** 1.3.2  
+**Stable tag:** 1.3.3  
 **Requires PHP:** 8.0.0  
 **License:** GPLv2 or later  
 **License URI:** <http://www.gnu.org/licenses/gpl-2.0.html>
@@ -51,7 +51,11 @@
 
 ## Quick start
 
-This is a WordPress plugin. It can be installed via the usual WordPress Dashboard workflow.
+The Pantheon Content Publisher plugin can be installed like any other WordPress Plugin, from your WordPress Dashboard, go to Plugins -> Add Plugin and search for: Pantheon Content Publisher, click the Install Now button and then click Activate. 
+
+After the plugin is active, set up your connection to Pantheon Content Publisher and Google Drive via the settings page in the WordPress admin dashboard.
+
+Alternately you can download and install the plugin manually:
 
 - [Download the latest release.](https://github.com/pantheon-systems/pantheon-content-publisher-wordpress/releases/)
 

README.md

@@ -3,7 +3,7 @@ Contributors: getpantheon
 Tags: pantheon
 Requires at least: 5.7
 Tested up to: 6.8.1
-Stable tag: 1.3.2
+Stable tag: 1.3.3
 Requires PHP: 8.0.0
 License: GPLv2 or later
 License URI: http://www.gnu.org/licenses/gpl-2.0.html
@@ -62,6 +62,9 @@ All posts/pages created with Pantheon Content Publisher will remain on your Word
 
 == Changelog ==
 
+= 1.3.3 (5 November 2025) =
+* Fix: Fixed plugin not loading on WordPress.org due to missing build files
+
 = 1.3.2 =
 * Fix: Resolved issue loading Content Publisher admin screen
 

README.txt

@@ -90,7 +90,7 @@ private function enqueueDevAssets(string $handle): void
 
 	private function enqueueProdAssets(string $handle): void
 	{
-		$manifestPath = CPUB_PLUGIN_DIR . 'dist/build/.vite/manifest.json';
+		$manifestPath = CPUB_PLUGIN_DIR . 'assets/dist/build/.vite/manifest.json';
 		if (!file_exists($manifestPath)) {
 			error_log('Manifest file not found');
 			return;
@@ -105,11 +105,11 @@ private function enqueueProdAssets(string $handle): void
 		$jsFile = $entry['file'] ?? null;
 		$cssFiles = $entry['css'] ?? [];
 		if ($jsFile) {
-			wp_enqueue_script_module($handle, CPUB_PLUGIN_DIR_URL . 'dist/build/' . $jsFile, [], null, true);
+			wp_enqueue_script_module($handle, CPUB_PLUGIN_DIR_URL . 'assets/dist/build/' . $jsFile, [], null, true);
 			$this->addBootstrap();
 		}
 		foreach ($cssFiles as $css) {
-			wp_enqueue_style($handle, CPUB_PLUGIN_DIR_URL . 'dist/build/' . $css, [], null);
+			wp_enqueue_style($handle, CPUB_PLUGIN_DIR_URL . 'assets/dist/build/' . $css, [], null);
 		}
 	}
 

app/Admin.php

@@ -707,17 +707,17 @@ public function enqueueAdminAssets(): void
 	{
 		wp_enqueue_script(
 			'pantheon-content-publisher',
-			CPUB_PLUGIN_DIR_URL . 'dist/app.js',
+			CPUB_PLUGIN_DIR_URL . 'assets/dist/app.js',
 			[],
-			filemtime(CPUB_PLUGIN_DIR . 'dist/app.js'),
+			filemtime(CPUB_PLUGIN_DIR . 'assets/dist/app.js'),
 			true
 		);
 
 		wp_enqueue_style(
 			'pantheon-content-publisher',
-			CPUB_PLUGIN_DIR_URL . 'dist/app.css',
+			CPUB_PLUGIN_DIR_URL . 'assets/dist/app.css',
 			[],
-			filemtime(CPUB_PLUGIN_DIR . 'dist/app.css')
+			filemtime(CPUB_PLUGIN_DIR . 'assets/dist/app.css')
 		);
 
 		wp_localize_script(
@@ -749,9 +749,9 @@ public function enqueueFrontAssets(): void
 
 		wp_enqueue_script(
 			'pantheon-content-publisher',
-			CPUB_PLUGIN_DIR_URL . 'dist/pcc-front.js',
+			CPUB_PLUGIN_DIR_URL . 'assets/dist/pcc-front.js',
 			[],
-			filemtime(CPUB_PLUGIN_DIR . 'dist/pcc-front.js'),
+			filemtime(CPUB_PLUGIN_DIR . 'assets/dist/pcc-front.js'),
 			true
 		);
 

app/Settings.php

@@ -1,6 +1,6 @@
 {
   "name": "pantheon-content-publisher",
-  "version": "1.3.1",
+  "version": "1.3.3",
   "description": "Publish WordPress content from Google Docs with Pantheon Content Cloud.",
   "scripts": {
     "dev": "NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --config=node_modules/laravel-mix/setup/webpack.config.js",