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

Language files


Now that we have internationalized our code and prepared it for localization using the __() family of functions, it's time to create a POT file. POT stands for "portable object template", and the .pot file will store all of your translatable messages in one place. The POT file is what translators will typically use to translate your messages into a specific language and locale. It is called a template because it contains message IDs . You may have thought that you were typing actual messages into your plugin, but take a moment to think of them as IDs. We are all familiar with this type of message ID—we see them all the time in error codes. For example, the copy machine might display "Error Code 7", or you may get a 404 message when you try to visit a web page that no longer exists. Later we translate that code or ID into a message we understand, like "Toner Low" or "Page not Found", but the ID itself is language agnostic.

In other words, you could have written your entire...