WordCamp Victoria 2013: Plugin Development 2013
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

WordCamp Victoria 2013: Plugin Development 2013

  • 1,009 views
Uploaded on

This is a presentation from WordCamp Victoria 2013 where I show power users and novice developers how to get started with plugin development. I think a lot of people don’t realize how easy it is to......

This is a presentation from WordCamp Victoria 2013 where I show power users and novice developers how to get started with plugin development. I think a lot of people don’t realize how easy it is to get started with plugin development or just how small and simple can be. It doesn’t require 100s of lines of code…

Many WordPress tutorials out there talk about copy this or that to your functions.php file in your theme. However, it’s just as easy to create your own functionality plugin; which makes for easier to maintain code in the future that isn’t theme dependant. I begin this talk with the basics of what a plugin is and how it’s structured. I then explain the hooks (actions and filters API), followed by a very simplistic demo. I then give some pro tips and talk about some of the most commonly used WordPress APIs in plugins, as well as promote coding standards. A second more in-depth demo is then presented. Finally, I discuss security in plugins and share some resources for developers and users to further learn from.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,009
On Slideshare
1,009
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
17
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Plugin Development - Joey Kudish http://slides.jkudish.comFriday, 11 January, 13
  • 2. About me • WordPress developer since 2007 • Initially built sites for a variety of clients • Freelance plugin development • Code Wrangler at WordPress.com / Automattic since May 2011 • Originally from Montreal, moved to Vancouver in 2011Friday, 11 January, 13
  • 3. Friday, 11 January, 13
  • 4. What’s a plugin?Friday, 11 January, 13
  • 5. A plugin extends or modi!es WordPress to do something it didn’t previously doFriday, 11 January, 13
  • 6. Themes can act as plugins. Oh and there’s mu-plugins too.Friday, 11 January, 13
  • 7. Plugins can be huge...Friday, 11 January, 13
  • 8. ... or tiny.Friday, 11 January, 13
  • 9. What’s in a plugin?Friday, 11 January, 13
  • 10. Where does it go? wp-content/plugins/[plugin_name] or wp-content/mu-plugins/Friday, 11 January, 13
  • 11. In order to “hook” into WordPress, we use action and !lter hooksFriday, 11 January, 13
  • 12. Action hooks allow you to add your own code to WordPress’ call stackFriday, 11 January, 13
  • 13. Filter hooks allow you to modify an existing variable or piece of informationFriday, 11 January, 13
  • 14. Demo timeFriday, 11 January, 13
  • 15. Let’s add Google Webmaster Tools veri!cation to our siteFriday, 11 January, 13
  • 16. Friday, 11 January, 13
  • 17. Friday, 11 January, 13
  • 18. Friday, 11 January, 13
  • 19. Finding hooks • WordPress.org Codex (http:// codex.wordpress.org/) • http://adambrown.info/p/wp_hooks • Debug Bar + Debug Bar Action Hooks plugin (http://wordpress.org/extend/plugins/debug-bar- action-hooks/) • Search core (use your IDE or a command line tool like ack)Friday, 11 January, 13
  • 20. Some pro tipsFriday, 11 January, 13
  • 21. Use built-in APIs, don’t re-invent the wheelFriday, 11 January, 13
  • 22. Use WordPress coding standardsFriday, 11 January, 13
  • 23. Be nice to other devs. Namespace your classes and functions. Leave hooks for others.Friday, 11 January, 13
  • 24. Demo timeFriday, 11 January, 13
  • 25. Friday, 11 January, 13
  • 26. Friday, 11 January, 13
  • 27. Friday, 11 January, 13
  • 28. Friday, 11 January, 13
  • 29. hey that’s the !le we want to hook intoFriday, 11 January, 13
  • 30. Friday, 11 January, 13
  • 31. Friday, 11 January, 13
  • 32. Friday, 11 January, 13
  • 33. Friday, 11 January, 13
  • 34. Let’s create our pluginFriday, 11 January, 13
  • 35. Friday, 11 January, 13
  • 36. Friday, 11 January, 13
  • 37. Friday, 11 January, 13
  • 38. Friday, 11 January, 13
  • 39. Friday, 11 January, 13
  • 40. Friday, 11 January, 13
  • 41. Friday, 11 January, 13
  • 42. Friday, 11 January, 13
  • 43. It works, now let’s have some funFriday, 11 January, 13
  • 44. Friday, 11 January, 13
  • 45. Friday, 11 January, 13
  • 46. Friday, 11 January, 13
  • 47. Friday, 11 January, 13
  • 48. Finished pluginFriday, 11 January, 13
  • 49. A word on SecurityFriday, 11 January, 13
  • 50. don’t trust usersFriday, 11 January, 13
  • 51. sanitize input, escape output http://codex.wordpress.org/Data_ValidationFriday, 11 January, 13
  • 52. protect users from malicious attacks, use nonces to validate user actions http://codex.wordpress.org/WordPress_NoncesFriday, 11 January, 13
  • 53. Plugin DistributionFriday, 11 January, 13
  • 54. Friday, 11 January, 13
  • 55. Friday, 11 January, 13
  • 56. Friday, 11 January, 13
  • 57. Further readingFriday, 11 January, 13
  • 58. Friday, 11 January, 13
  • 59. Friday, 11 January, 13
  • 60. Friday, 11 January, 13
  • 61. http://www.wrox.com/WileyCDA/WroxTitle/ http://www.packtpub.com/wordpress-plugin- Professional-WordPress-Plugin- development-cookbook/book Development.productCd-0470916222.htmlFriday, 11 January, 13
  • 62. Thanks! Q&A http://slides.jkudish.comFriday, 11 January, 13