For those of you who use WP CLI, we’ve got some great news: Joshua Priddle has created an extension for WP CLI which provides a
wp tgmpa-plugin command allowing you to interact with TGMPA from within the WP CLI environment.
For more information and extensive usage examples, visit Joshua’s WP CLI TGMPA Plugin repository.
As the TGMPA 2.6.0 release contained a minor, but very visible and annoying little bug in a particular string replacement, we’re releasing patch version 2.6.1 today which gets rid of this issue.
We like to thank Nilambar Sharma for reporting this issue to us quickly.
Today, we are releasing TGMPA version 2.6.0.
This version addresses a few bugs, a minor security issue and improves the usability of the admin notices.
Most notable changes:
publish_posts(=Author) capability. This capability is however filterable using the new
TGMPA now ships with translations and this first version which does, already includes 17 (!) translations. This will save your translators lots of work, so we’re very happy to bring you this enhancement. More translations are of course welcome, so please send the .po file(s) in as a pull request.
Please note: If you download TGMPA using the custom generator and indicate it’s for a theme to be hosted on wordpress.org, you will receive a version without the
load_textdomain() calls or the translation files.
Theme check rules dictate that you should only use one textdomain in your theme and the localization calls will be adjusted to use your theme’s textdomain.
As most TGMPA strings have a lot of translations available in GlotPress already, this should not cause any real issues.
For full details, please have a look at the changelog.
If you are a theme designer and publish themes on wordpress.org, you may have come across feedback from the Theme Check plugin and/or the Theme Review team along the lines of “You are only allowed to use add_theme_page(), please remove the call to add_submenu_page().” or “You are only supposed to use one text-domain.”.
So you go and do a search-and-replace and then get users reporting fatal errors because the search and replace also replaced some strings which shouldn’t have been changed.
And then when TGMPA is updated, you have to do it all over again.
Well, no more. We’ve heard you and we’ve worked hard to make this easier for you.
So today, we are releasing a Custom TGMPA Generator. You can find it on the Download page.
Just fill out the form with the text-domain of your theme or plugin, what sort of WordPress add-on you will be including TGMPA in and, if it’s a theme, the publication channel you’ll be using and we’ll generate a custom download of the current version of TGMPA for you with all the relevant code already adjusted.
We hope you like it. As this is a first release, there may of course still be some bugs. If you find one, please report it to us and we’ll try and fix it as soon as possible.
Since last summer, we’ve been slowly preparing ourselves to create the next version of TGMPA. The main issue we’d like to solve is multisite compatibility and we’d also like to reduce issues of conflicts between different versions of TGMPA running within one WP install.
Now it is time for you to stand up and be heard.
We’d like to hear your opinion about the changes we are proposing.
Please help us define the future of TGMPA by taking ten minutes of your time to fill out the survey.
Your opinion is much appreciated!
Also: please spread the word about the survey to other developers. The more, the merrier.