There are many like it, but this one is mine.
There are many like it, but this one is mine.
First, in case you are not familiar, here is a little bit of background on how translations work for WordPress.
Way back in 2013, WordPress 3.7 added support for something called language packs. When combined with Glotpress and a few automated processes behind the scenes, anyone who is multilingual with a WordPress.org account can translate plugins, themes, and even WordPress core through a simple front end interface.
Once a specific locale reaches the 95% translation mark, a language pack will be generated and automatically made available to anyone using the plugin on their WordPress site with that language locale selected.
Anytime you push an update to your plugin’s SVN repository, identical strings from past versions are automatically synced to the most recent versions. You can even watch this happen in the #meta-language-packs channel of the Making WordPress Slack.
Now, on to the issue that I experienced. When I pushed my updates to the plugin’s SVN repository, I noticed that the “Stable” column was empty. This was weird because “Development” and “Stable” were the same code.
I had committed my new code and changed the plugin’s stable version in the plugin file’s header in the same commit. Because of this, the automated processes that generate the translations behind the scenes could not generate a list for “Stable”.
To fix this, just make a commit to the plugin’s repository. I did this by increasing the version number while leaving the stable version alone. I watched the #meta-language-packs channel for my plugin to be regenerated after doing this, and all was well.
Do you speak another language? Hop over to the Toggle wpautop translation page and spend a few minutes translating my plugin. All contributions are appreciated.
For more background info on how translations work on wordpress.org, check out these Make WordPress blog posts.
If you are a plugin or theme developer and want to learn more about using language packs in your code, read through the core handbook for Internationalizing Your Plugins, and Internationalizing Your Themes.
I hope that someone finds this helpful!
After some investigation, I realized that the file it specified was only 25KB. However, at some point in its history it was over 100MB, Because I was pushing the entire commit history for that repository, it was rejecting everything.
The solution is to remove the file entirely from the repository’s history. It took some trial and error for me to find something that worked for me because most snippets relied on history already existing in the origin repository. Here is what worked for me:
git filter-branch --index-filter "git rm -rf --cached --ignore-unmatch path_to_file" HEAD
Hope this helps someone!
At WordCamp Rhode Island 2016, I ran the Contributor Day workshop. Before we got to work contributing to core, I gave a short presentation about how the WordPress development process works, and introduced them to the tools they would need to be familiar with.
I followed the Trac tickets that the participants became involved in. By my count, 5 first time contributors were credited in WordPress 4.7.
Congrats to all of the first-time contributors from WordCamp Rhode Island!
This weekend, me and several friends went on a mini getaway to North Conway, New Hampshire. We found a great place on airbnb that was able to accommodate all of us.
When we walked in, we were greeted on the counter by a bottle of wine, and a guest book. The guest book was filled with stories from past guests answering the following questions:
We spent time reading the stories in the book, which contained everything from bears climbing through the kitchen window in August to going skiing for the first time ever at Cranmore. But as we read these recollections, it was missing one thing: faces.
And that’s where this post comes in! We wrote our stories in the book for future guests to enjoy and included a link to this post in order to share photos of our trip with these future guests.
If you are reading this and are also a guest of the Tonnings, comment below and tell us about your trip.
Today I am teaching a workshop at WordCamp Providence 2014 called WordPress Plugin Development from Scratch. Below you can find the slides for you to follow along, as well as the finished plugin that we will be creating today.
Looking forward to working with you today!
Today, I gave my WordCamp Providence 2013 talk, “Next Level Plugin Development”. In case you missed it, or were in attendance and wanted a closer look at the slides, you can find them here.
In case you missed it, I was able to speak at WordCamp Providence last fall. My session was entitled Plugin Development – Stirred not Shaken.
This presentation makes sense of the pandemonium of plugin development by breaking it down into three stages: planning, implementation, and release, while providing resources and discussing best practices.
There are also a bunch of other WordCamp Providence 2012 session videos available.
“To do nothing is the most difficult thing in the world. It is also the most intellectual.” – Oscar Wilde