Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Samuel Sidler 3:22 pm on October 1, 2015 Permalink | Reply

    GlotPress, a Future WordPress Plugin 

    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, 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 users and 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.

  • Marko Heijnen 11:23 am on October 1, 2015 Permalink | Reply

    Status Update October 2015 


    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.
  • Marko Heijnen 2:37 pm on September 24, 2015 Permalink | Reply

    The upcoming week lot’s of code changes will happen. When you keep up-to-date with the latest code of GlotPress, it is recommended to not do this directly on production in the next days. Specially when you have custom code or theme. I would appreciate you guys testing things out and leaving feedback during this week.

    My focus in random order is:

    • new header with navigation
    • redesigned breadcrumbs
    • Changes in gp_title
    • favorites
    • notifications
    • reject with feedback
    • Move BackPress to GlotPress

    If you feel something is missing then let me know and I will see if I can manage to get something done on that too. Otherwise I will let you know when I think I can work on it. Also if you want to help out, let me know here or ask in the GlotPress Slack channel on WordPress Slack

  • Marko Heijnen 5:50 pm on September 20, 2015 Permalink | Reply

    Meeting starts this Thursday 

    It has been a long time goal to have a regular meeting but till now I couldn’t find the time that I would able to be there most of the time. After rethinking the time from comments, I decided to set up a weekly meeting at 12UTC on every Thursday starting this week.

    This first meeting we will discuss how to notify Validators and translators for important changes. I just created two tickets for a Notification Center and for Favorites. This will help us out with sending out notifications and building up a user dashboard. In the next couple of days I will work on this so we can discuss the progress.

  • Marko Heijnen 7:38 pm on February 13, 2015 Permalink | Reply
    Tags: theme   

    Rebuilding our theme 

    In the last year there were several discussions about the design of GlotPress. I tried to use bootstrap to make it nicer but what we really need is a complete rewrite of the theme. For this purpose I created a repo on GitHub where we can build a fresh new theme that fits our needs. Also Aris Blevins already created some mockups how the translation flow could work. This is also linked on the GitHub channel.

    If you want to help out just leave a comment and check out You can create tickets with ideas and things you would like to change.

    • fxbenard 3:11 pm on February 17, 2015 Permalink | Reply

      The new default theme looks nice, just to give you some “encouragements”. Well done

    • Chantal Coolsma 1:16 pm on February 18, 2015 Permalink | Reply

      I would love to see an improvement if a string is corrected while it already has been translated. That would be easier to compare if the new translation is better.

    • cfoellmann 12:36 pm on March 8, 2015 Permalink | Reply

      does this mean you will add some kind of theme support? So “we” can use custom themes?

  • Marko Heijnen 12:06 am on February 5, 2015 Permalink | Reply

    Status update 

    So it has been quiet for the last two months. Only some small changes have been made to the code. But before going into this years plans I first want to thank all the contributors from last year: yoavf, Secretmapper, vanillalounge, nacin, nbachiyski, DJPaul, koke, dimadin, juanramondiaz, wonderboymusic, stuwest, extendwings, Nao, ocean90, knome, joostdevalk, waclawjacek, cfoellmann, ramiy, hew. And that is without mentioning the people who submitted still waiting patches and tickets. It was a good year where great improvements where made.

    So for this year already quite some tickets and patches have been created and I will try to review this month. There will be three focus topics for this year which are increasing contributions, build a new default theme and rebuild part of core (to increase performance).

    To increase the amount of contributors we will try to be more proactive when tickets, patches and issues are raised so people feel more connected to the project. Also from March there will be a weekly meeting where we can sync planning and work on new ideas. currently I’m thinking to do this meeting on Thursdays at 15:00 UTC. If you have suggestions then please let my know. I will create blog posts for the other two topics.

    As last, from this point on I will be actively leading the project. Due to the fact that we have active contributors now, it also means that my role need to be active instead of committing things that I like to work on. Also GlotPress has become more important for open source projects and there is a lot of things that could increase the usability of GlotPress.

    • Japh 12:17 am on February 5, 2015 Permalink | Reply

      Thanks for the update, Marko! :)

      I’d really like to contribute more this year. 15:00 UTC will be 02:00 AEST, so if that’s the time meetings happen, us Aussies will need to just catch up on scrollback.

    • Tor-Bjorn Fjellner 4:35 pm on August 14, 2015 Permalink | Reply

      Would it be possible to submit a translated string by hitting ctrl+Enter on the keyboard? That would speed things up.
      Oh, and a keyboard shortcut to copy original string to the translation.

  • Marko Heijnen 7:04 pm on November 30, 2014 Permalink | Reply

    Process November 2014 

    As promised in last update we will now have monthly update post. The biggest change is that since this weekend we moved to PHP 5.3. While we adding new features, we also clean up the code and this time we starting to deprecate our lambda function and now moving to anonymous functions which got added in PHP 5.3.

    Unfortunately we didn’t manage to do the things on our roadmap due to fixing some important bugs. But I’m sure that some of those bugs will make you guys happy. I finally had the time to dig into the caching issue of the translation set counts and fixed it.  We also currently hidden public profiles but that will be back in a few days.

    Changes made

    • Invalidate the translation set cache when approving/rejecting a string.
    • Increased performance of profile pages.
    • Disregard context if it’s any falsy value.
    • Fix going to the previous translation with the keyboard.
    • Move to the next translation when approving/rejecting a string.
    • Reduce the size of index ‘singular_plural_context’ for originals.
    • Added a link on users profile page to his translations of that translation set.
    • Fix guess_uri() for subdirectory installations.
    • Fixed not exporting translation comments for PO files.
    • Don’t fatal when hitting a projects page where the parent project has been deleted (work in progress).
    • Remove RRC format.
    • Stop using lambda function and start switching to anonymous or normal functions.
    • Add support for Oriya and Lingala.
    • Update Kinyarwanda.

    Thanks to: yoavf, joostdevalk, nbachiyski and waclawjacek

    Changesets 970 – 999

  • Marko Heijnen 9:55 pm on November 23, 2014 Permalink | Reply  

    Moving to PHP 5.3+ 

    In the last year things got changed and improved. Lately things are speeding up and part of that we decided to move to PHP 5.3+ because we want to move away from create_function() and start using anonymous functions. For the current patch you can check out

    The current patch will be committed this week and from there we will start looking at other functions that are still calling create_function().

  • Marko Heijnen 9:43 am on November 5, 2014 Permalink | Reply  

    Survey for Translators & Validators 

    Hey all,

    So lately we are moving forward in making GlotPress better and we would love to hear your feedback. teamadesign made 2 surveys to see how you guys translate/validate strings and how the design of GlotPress should reflect that.

    For translators:
    For validators:

    It would be great if you can fill it out so GlotPress becomes the translation tool you like.

    • slaFFik 10:07 am on November 5, 2014 Permalink | Reply

      Answered. But why results are private?

    • Petya 11:52 am on November 5, 2014 Permalink | Reply

      Marko, post this on the Polyglots P2, it will raise the response rate :)

      • Petya 11:53 am on November 5, 2014 Permalink | Reply

        Also, agree about the results – they should be public.

      • Marko Heijnen 2:29 pm on November 5, 2014 Permalink | Reply

        I left a comment on Slack about that ;) but now I did posted it.

  • Marko Heijnen 3:18 pm on November 2, 2014 Permalink | Reply

    In the last couple of months some great features got added like profiles and locale pages. Also we created a roadmap and try to keep up with that one. So from last month only profiles got added and we still need to do a bit more work for fixing the SQL issues and cleaning up locales.php. Also since we now have a roadmap, I will post by the end of every month an update about what got done.

    Changes made

    • Added locale pages (in progress).
    • Added public profiles (in progress).
    • Fixes to Glossary.
    • Fixes for branching.
    • Complete overhaul of the installation process. You can now fill in your username, password and email address.
    • Return percent_translated and wp_locale when using the API to retrieve the translation sets of a project.
    • Add last_modified to the API and cache it.
    • Show by default references again and add a filter to hide them if needed.
    • Exclude old strings from the untranslated translations query.
    • Add filter to the import method to allow selective import over existing translations.
    • Add action in the translation set filters form.
    • Add filter to import translation status.
    • Small design changes
    • Cleanup locales.php a bit
    • Proper native name for Sakha.
    • Update native names for zh_CN and zh_TW.

    Thanks to yoavf, nacin, nbachiyski, secretmapper, knome, extendwings, vanillalounge, stuwest and ocean90

    Changesets 931 – 969

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc

Get every new post delivered to your Inbox.

Join 483 other followers