Troubleshooting

Browser Runtime Missing

Pressship installs Chromium automatically. If that fails, run:

npx playwright install chromium

For local development:

Run the `browsers:install` package script.

Not Logged In

Run:

npx pressship login
npx pressship whoami

If the saved session is stale:

npx pressship logout
npx pressship login

Plugin Check Setup Problems

The managed Plugin Check environment is automatic, but it still needs PHP and internet access on first run.

To bypass only Plugin Check during submit-style uploads:

npx pressship submit ./my-plugin --skip-plugin-check

To bypass both readme validation and Plugin Check before publishing or releasing through SVN:

npx pressship publish ./my-plugin --no-verify
npx pressship release ./my-plugin --no-verify

To use your own WordPress install:

npx pressship submit ./my-plugin --wp-path /path/to/wordpress

Subversion Missing

pressship get, pressship release, and pressship publish --release need svn. If it is missing, Pressship detects your operating system and package manager, then asks before installing Subversion.

Supported installer paths include Homebrew, apt, dnf, yum, pacman, zypper, apk, winget, and Chocolatey.

To skip automatic installation and print manual instructions instead:

npx pressship get list-all-urls --no-install-svn
npx pressship release ./my-plugin --no-install-svn

Playground Demo Noise

demo suppresses PHP deprecation notices so demo pages are readable. Real warnings, errors, and fatal errors are still shown.

Use --reset when a persisted Playground site is stale:

npx pressship demo ./my-plugin --reset

WordPress.org Form Changes

The WordPress.org submission and reupload flows are browser automation over the logged-in developer page, not a documented public API. If WordPress.org changes the form, Pressship fails loudly and saves a debug screenshot under the config directory.