Preparing & Releasing a Plugin on WordPress.org

Preparing & Releasing a Plugin on WordPress.org

How do you get a plugin onto the WordPress.org repository? What steps do you need to take? Are there any specific requirements?

These are just some of the questions this talk, aimed at anyone who wants to push a plugin to the Wordpress.org repository will answer. We will go through the steps you need to take in order to prepare your plugin, some best practices in the plugin code and how to submit it to .org.

31af50af29856a3e6734bdae0a0d68cf?s=128

Mark Wilkinson

January 20, 2016
Tweet

Transcript

  1. PREPARING YOUR PLUGIN For a .org Release Mark Wilkinson |

    markwilkinson.me | @wpmark
  2. WHY? PREPARATION SUBMISSION AFTERCARE

  3. WHY? PREPARATION SUBMISSION AFTERCARE

  4. WHY? PREPARATION SUBMISSION AFTERCARE

  5. WHY? PREPARATION SUBMISSION AFTERCARE

  6. None
  7. ASSUMPTIONS

  8. WHY?

  9. DEVELOPMENT WHERE WILL IT HAPPEN?

  10. Coding Standards https://make.wordpress.org/core/handbook/best-practices/coding-standards/ https://upload.wikimedia.org/wikipedia/commons/1/1a/Code.jpg

  11. EXTENSIBILITY do_action() / apply_filters() wordpress.tv/2014/08/29/mark-wilkinson-easy-extensible-plugins/

  12. SANITIZE & VALIDATE wp_kses( $string, $allowed_html, $allowed_protocols ) esc_html( $text

    ) / esc_url( $url ) / esc_attr( $attr ) $wpdb->insert( $table, (array) $data )
  13. define( 'WP_DEBUG', true );

  14. https://www.flickr.com/photos/lendingmemo/11702409583

  15. None
  16. None
  17. None
  18. readme.txt https://wordpress.org/plugins/about/readme.txt https://wordpress.org/plugins/about/validator/ Contributors: wpmarkuk Donate link: http://markwilkinson.me/saythanks/ Tags: users,

    user switching Requires at least: 3.1 Tested up to: 4.4 Stable tag: 1.0.6 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html
  19. None
  20. SUBMIT TO .ORG

  21. https://wordpress.org/plugins/add/

  22. None
  23. SVN

  24. assets/ branches/ tags/ trunk/

  25. SUPPORT

  26. 1.  Must be compatible with the GNU General Public License

    v2, or later 2.  Must not do anything illegal, or be morally offensive 3.  You have to actually use the Subversion repository we give you 4.  The plugin must not embed external links on the public site (like a "powered by" link) without explicitly asking the user's permission. 5.  If you don’t specify a compatible license, what you check in is considered GPLv2 or later. 6.  We also have a large list of detailed guidelines, but mostly they say how not to be a spammer. FOLLOW THE RULES
  27. 1.  Must be compatible with the GNU General Public License

    v2, or later 2.  Must not do anything illegal, or be morally offensive 3.  You have to actually use the Subversion repository we give you 4.  The plugin must not embed external links on the public site (like a "powered by" link) without explicitly asking the user's permission. 5.  If you don’t specify a compatible license, what you check in is considered GPLv2 or later. 6.  We also have a large list of detailed guidelines, but mostly they say how not to be a spammer. FOLLOW THE RULES
  28. 1.  Must be compatible with the GNU General Public License

    v2, or later 2.  Must not do anything illegal, or be morally offensive 3.  You have to actually use the Subversion repository we give you 4.  The plugin must not embed external links on the public site (like a "powered by" link) without explicitly asking the user's permission. 5.  If you don’t specify a compatible license, what you check in is considered GPLv2 or later. 6.  We also have a large list of detailed guidelines, but mostly they say how not to be a spammer. FOLLOW THE RULES
  29. 1.  Must be compatible with the GNU General Public License

    v2, or later 2.  Must not do anything illegal, or be morally offensive 3.  You have to actually use the Subversion repository we give you 4.  The plugin must not embed external links on the public site (like a "powered by" link) without explicitly asking the user's permission. 5.  If you don’t specify a compatible license, what you check in is considered GPLv2 or later. 6.  We also have a large list of detailed guidelines, but mostly they say how not to be a spammer. FOLLOW THE RULES
  30. 1.  Must be compatible with the GNU General Public License

    v2, or later 2.  Must not do anything illegal, or be morally offensive 3.  You have to actually use the Subversion repository we give you 4.  The plugin must not embed external links on the public site (like a "powered by" link) without explicitly asking the user's permission. 5.  If you don’t specify a compatible license, what you check in is considered GPLv2 or later. 6.  We also have a large list of detailed guidelines, but mostly they say how not to be a spammer. FOLLOW THE RULES
  31. 1.  Must be compatible with the GNU General Public License

    v2, or later 2.  Must not do anything illegal, or be morally offensive 3.  You have to actually use the Subversion repository we give you 4.  The plugin must not embed external links on the public site (like a "powered by" link) without explicitly asking the user's permission. 5.  If you don’t specify a compatible license, what you check in is considered GPLv2 or later. 6.  We also have a large list of detailed guidelines, but mostly they say how not to be a spammer. FOLLOW THE RULES
  32. #wpcumbria wpcumbria.com

  33. Thank you Questions? @wpmark markwilkinson.me github.com/wpmark profiles.wordpress.org/wpmarkuk P.S. I’m available

    for hire!