BugWP logo BugWP
Back to Community
Home / Community / Core → Everything else wordpress

Resolving Common WordPress.org Plugin SVN and Update Issues

18 threads Sep 16, 2025 Core → Everything else wordpress

Content

If you develop or maintain a plugin on WordPress.org, you've likely encountered a frustrating scenario: you commit a new version to the SVN repository, but the update never appears on your plugin's page. This is a common problem with a few typical causes and solutions.

Why This Happens

The WordPress.org plugin directory relies on a system that automatically imports changes from the Subversion (SVN) repository. This process is not always instantaneous and can sometimes fail due to server-side issues, import errors, or specific problems with your commit.

Common Issues and Their Solutions

1. The Trunk Directory Was Not Updated

The Problem: You commit a new tag (e.g., /tags/1.2.0), but the /trunk directory remains on an old version. The update system often uses the trunk to determine the latest stable version, so if it's outdated, your update may not propagate.

The Solution: Best practice is to always update the /trunk directory to match the latest stable tag. You can do this by copying the contents of your new tag directory into the trunk and committing the change.

2. SVN Server Issues (HTTP 429, 502, 504 Errors)

The Problem: You may encounter errors like HTTP 429 'Too Many Requests', 502 'Bad Gateway', or 504 'Gateway Time-out' when trying to commit or check out code. Error 429 indicates your server or IP address has been rate-limited, while 502/504 errors often point to temporary server overload or outages on the WordPress.org side.

The Solution:

  • For 429 Errors: This is a rate limit. If you are running automated scripts that frequently check the SVN, you must significantly reduce their frequency. Wait for a period (e.g., 12-24 hours) for the limit to reset.
  • For 502/504 Errors: These are typically temporary. The best course of action is to stop trying to commit and wait for an announcement that the issue has been resolved. Official status updates are often posted in the #pluginreview channel on the Make WordPress Slack.

3. Plugin Import Warnings or Errors

The Problem: The automated import process encountered a warning or error while processing your plugin, such as having too many tags. This will halt the update, and you may receive an email notification detailing the problem.

The Solution: Address the specific warning mentioned in the error message. For example, if the error is about too many tags, you may need to remove old tags from the repository. After fixing the issue in your SVN, the import process should run successfully on its next attempt.

4. General Delays and Unknown Issues

The Problem: Sometimes, everything appears correct in SVN, but the update still doesn't show. This can be due to a backlog in the import queue or an unspecified server-side issue.

The Solution: Patience is the first step. It can sometimes take up to 24 hours for an update to fully process and appear. If it has been longer than that, the recommended place to seek help is the #pluginreview channel on the Make WordPress Slack. Volunteers and contributors there can often look up your plugin and provide specific information.

When to Seek Further Help

If you have tried the solutions above and your plugin is still not updating after 48 hours, the community recommends asking for assistance in the #pluginreview Slack channel. For issues related to the initial plugin review process, it is best to continue corresponding via email with [email protected].

Remember, the WordPress.org plugin repository is a large, complex system. While delays and errors can be frustrating, they are usually resolved by following the guidelines above or with help from the community.

Related Support Threads Support