Skip to content

WORDPRESS.org.md

Latest commit

 

History

History
90 lines (62 loc) · 1.99 KB

WORDPRESS.org.md

File metadata and controls

90 lines (62 loc) · 1.99 KB

WordPress.org SVN Instructions

After your plugin is approved for the WordPress.org plugin directory, you will receive SVN access details.

SVN Structure

The SVN repository for WordPress.org plugins has the following structure:

/assets/    - Plugin assets (banner, icon, screenshots)
/tags/      - Tagged releases (1.0.0, 1.1.0, etc.)
/trunk/     - Current development version

Initial SVN Setup

  1. After receiving SVN access, check out the repository:
svn checkout https://plugins.svn.wordpress.org/wp-devlog/
cd wp-devlog
  1. Copy your plugin files to the /trunk directory:
# From your development directory
cp -R * /path/to/svn/wp-devlog/trunk/
  1. Copy assets to the /assets directory:
cp -R assets/* /path/to/svn/wp-devlog/assets/
  1. Add all files to SVN:
cd /path/to/svn/wp-devlog/
svn add trunk/* --force
svn add assets/* --force
  1. Commit the changes:
svn commit -m "Initial plugin version"

Tagging a New Release

When you release a new version:

  1. Update version numbers in:

    • devlog.php (Plugin header)
    • readme.txt (Stable tag)
    • Update changelog in readme.txt

  2. Commit the changes to trunk:

svn commit -m "Update to version X.Y.Z"
  1. Create a new tag:
svn copy https://plugins.svn.wordpress.org/wp-devlog/trunk https://plugins.svn.wordpress.org/wp-devlog/tags/X.Y.Z -m "Tagging version X.Y.Z"

Updating Plugin Assets

To update banners, icons, or screenshots:

cd /path/to/svn/wp-devlog/
svn commit assets/ -m "Update plugin assets"

WordPress.org Plugin Guidelines

Always ensure your plugin follows the WordPress.org Plugin Guidelines.

Common issues to avoid:

  • Make sure all code is GPL compatible
  • Do not include obfuscated code
  • Make sure the plugin works with the latest WordPress version
  • Do not track users without consent
  • Keep the SVN repository clean and well-organized