GlotPress 1.0.1 is now available. This maintenance release fixes 2 bugs in version 1.0.0.
- Bugfix: Unslash PHP’s superglobals to prevent extra slashes in translations. (#220)
- Bugfix: Adjust add/delete glossary entry links with trailing slashes. (#224)
For a full list of changes, consult the list of issues and the changelog.
Thanks to everyone who reported bugs and provided code or other help, including Greg Ross, Iain Poulson, François-Xavier Bénard, and Taco Verdo.
Version 1.0 of GlotPress, named “Bunsen Honeydew”, is available for download in WordPress.org’s Plugin Directory.
This is the first public release of GlotPress as a WordPress plugin, an alternative to the standalone version.
Between the initial commit and today’s last commit for the first plugin version 70 issues were solved and 86 Pull Requests were merged, a total of 352 commits.
- It’s a plugin! 😉
- WP-CLI support
- Integrated with WordPress’s user system
- Easy installation through the WordPress.org plugin directory
- Multisite support
For the first version the goal was to change as little as possible to get it working well. But still we had to remove some things in favour of WordPress’ API system. You can review the list of breaking changes in our wiki. If you have existing plugins for the standalone version take a look at this guide on how to convert them to WordPress plugins.
Contributors of this release: Aki Björklund, Alex Kirk, Andrew Nacin, Ashley Rich, Brad Touesnard, Chantal Coolsma, Dominik Schilling, Gabor Javorszky, Gilbert Pellegrom, Greg Ross, Iain Poulson, Ian M. Jones, Jeff Gould, Ryan McCue, and Samuel Sidler. Also, a special thanks goes to Hugo Baeta for the great logo!
If you want to follow along or help out, check out our repository on GitHub.
The first beta of GlotPress as a WordPress plugin is now available! 🍾
Since the first meeting the current development team has achieved a lot. 81 Pull Requests were merged with more than 250 commits by 13 contributors! Now we need some help with testing what we have been working on.
This software is still in development. Consider setting up a test site just to play with the new version. Please read also the list of breaking changes.
If you have existing plugins for the standalone version take a look at this guide to convert them to WordPress plugins.
The beta can be downloaded in the plugin directory, just search for “GlotPress” and click the install button.
If you think you’ve found a bug, you can post to the issue tracker on GitHub.
The release of 1.0 is targeted for Januar 18th 2016.
On January 14th @ 14:00 UTC we’ll have our next meeting. We’ll talk about our goals for 2016 – you’re invited!
Reminder: The fourth GlotPress as a WordPress Plugin chat happens on October 22th @ 13:00 UTC (tomorrow) in the #glotpress Channel on Slack.
Please go through the list of issues/PR’s and leave a :thumbsup: if you think something is OK or add comment if something should be changed. Thanks!
Here’s the agenda for the GlotPress as a WordPress Plugin chat on October 15th @ 13:00 UTC in the #glotpress Channel on Slack.
1. New Issues
The goal is to set a release tag and owner, technical discussion of the issue can be done in the GitHub ticket.
IS33 Prefix all GlotPress Action/Filters with “gp_”
IS34 Database is only updated on plugin activation
IS35 Replace $gpdb with $wpdb
IS36 Recent merge of upstream changes conflicted with the assets move PR
2. New PRs
The goal is to make a decision if a pull request is:
- ready to merge
- not ready but should be targeted at the next release milestone
- not ready and will be targeted at a future release milestone
- will not be merged (declined)
PR38 Allow GP to take over the root URL on the frontend
PR44 Plugin prefix actions and filters
PR45 Move install css
PR46 Remove the $gpdb global and replace it with $wpdb
PR47 Database is only updated on plugin activation
PR48 Convert gp plugin system
PR49 Merge upstream changes as of Oct 14 2015
3. Outstanding Issues/PR’s with 1.0 tag
The goal is to assign an owner if none exists, determine if it should still be targeted at the 1.0 release or postpone to a future release.
IS1 Attempting to “import originals” times out [SergeyBiryukov]
IS5/PR20 Remove GP_User [A5hleyRich]
IS7/PR48 Convert GlotPress plugin system to WordPress [toolstack/Greg Ross]
IS9 Backwards Compatibility 
IS10 Allow GlotPress tables to have a table prefix independent of the WP table prefix [bradt]
IS11/PR43 Merge upstream changes [ocean90]
IS15/PR16 Make plugin translation ready [polevaultweb]
IS19 Convert GP permissions to WP roles 
IS21/PR22 Flush rewrite rules on plugin (de)activation 
IS23/PR24 Convert scripts to WP-CLI commands 
IS30/PR38 Allow GP to take over the root URL on the frontend [bjork]
IS31/PR32 Unit tests [gilbitron]
4. Release Target
Discussion for a soft target for 1.0 release.
5. New Items/Technical Discussion/Open Discussion
Suggestions for any other agenda items can be posted in the comments.
(Thanks to Greg Ross for the agenda proposal.)
At the GlotPress weekly chat last week (September 24), a large number of attendees were interested in developing GlotPress as a WordPress plugin. There are certain advantages to this direction, including the availability of tens of thousands of WordPress plugins and the ability to utilize many WordPress features instead of reinventing them. You can read the log of that meeting here (there was more follow up in today’s GlotPress meeting as well).
As a result of those discussions, a group from the community has formed a team to develop GlotPress-the-plugin on GitHub. Today, this team met and discussed a short roadmap to get the plugin ready for production on translate.wordpress.org, among other sites. Here’s a quick recap of some of the decisions that were made on the path toward 1.0:
- In general, the goal is to keep GlotPress the same and only replace features if WordPress already includes them. Commits to GlotPress core (SVN) will be merged into the plugin as-needed.
- GlotPress-the-plugin should live alongside WordPress instead of being a standalone application. This means a site could still use posts and pages, just like other WordPress installations. Of course, this behavior could easily be modified by a plugin.
- For the initial version, the GlotPress administration tools will remain on the front end and not move to WP-Admin (#14).
- GlotPress plugins will need to be converted to WordPress plugins; GlotPress-the-plugin will not provide backward compatibility for GlotPress plugins. However, scripts should be made to migrate installs, perhaps using wp-cli (#9).
- It is recommended that WordPress plugins that support GlotPress-the-plugin use “gp” at the start of their slug and include the “glotpress” tag in the plugin directory.
- For version 1.0, theming in GlotPress will remain the same. Integration with WordPress themes will happen later.
- Version 1.0 of the plugin will also not include migration tools for
usermeta tables. While there are certainly installations which utilize these GlotPress tables, a fair number use WordPress tables to manage their users. Migration tools will be added later (#6).
- Code practices should follow the WordPress core best practices. However, just as core does, these standards only apply to new code or when modifying code; old code can remain as it is (see also).
For the foreseeable future, development of this plugin will take place on GitHub. You can view the 1.0 milestone for more information.
If you’re interested in this direction for GlotPress, get involved and help build the plugin or join us for the next GlotPress-the-plugin chat, next Thursday at 13:00 UTC, just after the GlotPress chat.
Currently we have a new header/breadcrumb design which looks better then we had before. It takes up a little bit more height but in return we now have a menu where you can add links if wanted.
Due to this redesign the output of gp_breadcrumbs is a list now and styling will be applied on display. Still makes adding new items easier since you don’t need to know the styling. Also the action after_hello got removed.
Other updates are:
- Show login after installation again and after that redirect to the home page
- Make warnings for newline mismatches more verbose.
- Ready to commit a patch for gp_title
- Currently working on favorites/watched projects and decline with feedback.