Tag Archives: wordpress-plugin

Unknown's avatar Dominik Schilling 9:14 pm on October 21, 2015
Tags: wordpress-plugin   

Reminder The fourth GlotPress as a WordPress Plugin…

Reminder: The fourth GlotPress as a WordPress Plugin chat happens on October 22th @ 13:00 UTC (tomorrow) in the #glotpress Channel on Slack.

Agenda: https://github.com/deliciousbrains/GlotPress/wiki/4.-Weekly-Meeting-Agenda

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!

#wordpress-plugin

Unknown's avatar Dominik Schilling 10:14 pm on October 14, 2015
Tags: wordpress-plugin   

Agenda for the GlotPress as a WordPress Plugin chat on October 15th

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.

Issues:

  1. IS33 Prefix all GlotPress Action/Filters with “gp_”
  2. IS34 Database is only updated on plugin activation
  3. IS35 Replace $gpdb with $wpdb
  4. 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)

Pull Requests:

  1. PR38 Allow GP to take over the root URL on the frontend
  2. PR44 Plugin prefix actions and filters
  3. PR45 Move install css
  4. PR46 Remove the $gpdb global and replace it with $wpdb
  5. PR47 Database is only updated on plugin activation
  6. PR48 Convert gp plugin system
  7. 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.

  1. IS1 Attempting to “import originals” times out [SergeyBiryukov]
  2. IS5/PR20 Remove GP_User [A5hleyRich]
  3. IS7/PR48 Convert GlotPress plugin system to WordPress [toolstack/Greg Ross]
  4. IS9 Backwards Compatibility []
  5. IS10 Allow GlotPress tables to have a table prefix independent of the WP table prefix [bradt]
  6. IS11/PR43 Merge upstream changes [ocean90]
  7. IS15/PR16 Make plugin translation ready [polevaultweb]
  8. IS19 Convert GP permissions to WP roles []
  9. IS21/PR22 Flush rewrite rules on plugin (de)activation []
  10. IS23/PR24 Convert scripts to WP-CLI commands []
  11. IS30/PR38 Allow GP to take over the root URL on the frontend [bjork]
  12. 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.)

#wordpress-plugin

Unknown's avatar Samuel Sidler 3:22 pm on October 1, 2015
Tags: wordpress-plugin   

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 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 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.

#wordpress-plugin