Book Image

WordPress 3 Plugin Development Essentials

Book Image

WordPress 3 Plugin Development Essentials

Overview of this book

WordPress is one of the most popular platforms for building blogs and general websites. By learning how to develop and integrate your own plugins, you can add functionality and extend WordPress in any way imaginable. By tapping into the additional power and functionality that plugins provide, you can make your site easier to administer, add new features, or even alter the very nature of how WordPress works. Covering WordPress version 3, this book makes it super easy for you to build a variety of plugins.WordPress 3 Plugin Development Essentials is a practical hands-on tutorial for learning how to create your own plugins for WordPress. Using best coding practices, this book will walk you through the design and creation of a variety of original plugins.WordPress 3 Plugin Development Essentials focuses on teaching you all aspects of modern WordPress development. The book uses real and published WordPress plugins and follows their creation from the idea to the finishing touches in a series of easy-to-follow and informative steps. You will discover how to deconstruct an existing plugin, use the WordPress API in typical scenarios, hook into the database, version your code with SVN, and deploy your new plugin to the world.Each new chapter introduces different features of WordPress and how to put them to good use, allowing you to gradually advance your knowledge. WordPress 3 Plugin Development Essentials is packed with information, tips, and examples that will help you gain comfort and confidence in your ability to harness and extend the power of WordPress via plugins.
Table of Contents (19 chapters)
WordPress 3 Plugin Development Essentials
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Committing changes to the repository


This is how we really add files to the repository, we commit them. To jump right to it, we use the commit command like this:

svn commit . -m "Testing our first commit"

It produces some output like the following:

Sending        laika.php
Transmitting file data ......
Committed revision 2.

The dot after the commit symbolizes this directory, so as written, the command assumes that you are inside the root of your working copy. You could run that command from elsewhere on the file system simply by specifying the full path and it would have the same effect:

svn commit /full/path/to/my-working-copy -m "Testing our first commit"

The -m is short for --message, and it allows us to describe this particular commit. These messages are searchable and they can help you track down when particular changes were made, so it's good to describe each commit in a meaningful way so that you can search for those changes later.

The rest of the output shows us which files were transmitted...