i18n resource … the hide & seek game Note up front: I’m not 100% sure about this, so please take the following with a grain of salt. I’m 99% sure by now, that the following information is correct. (Still, it’s confusing even after years with WordPress). Non-Gettext translation for core The 18n.wordpress.org resource is used … Read more
You should store a version number for your plugin in the database (if you don’t already, add this pronto), using that you can do this (note that this is pseudocode): if( $db_version < {your desired version} ) { // previous updates and such $db_version = $new_version; //put that in the database } if( $db_version < … Read more
Real answer, taking all the above into account: Regarding .svn directories: Subversion 1.7 was released a little over a year ago ( http://svn.haxx.se/dev/archive-2011-10/0152.shtml ) and the working copies no longer contain .svn directories in every folder. They contain a single .svn directory in the root, along with fairly substantial performance improvements. Today, SVN is up … Read more
TLDR: No. It’s all about trust. So there are some very basic checks on wp.org but generally this can happen (and probably also does happen from time to time). Of course if something like this happens and people notice it wp.org can block updates or replace them with something safe. Also have a look at … Read more
Im going to make this answer a blog article since it went slightly off-topic GRIN. On http://wp.leau.co/2011/02/25/how-to-setup-your-wordpress-php-development-environment/ in chapter 6 I made some explanation for SVN in eclipse but you are probably looking for something else. The story I made here was about your comment “So for now I wing it with VCS integration features … Read more
Good news and more good news! First – all of the code related to WordPress itself and its repositories resides in version control system (Subversion). Among other things that makes publicly available sites with all code in plain sight: http://core.svn.wordpress.org/ http://themes.svn.wordpress.org/ http://plugins.svn.wordpress.org/ One not so obvious result of that – if you can see it, … Read more
Yep, you can pass the initial revision from which to start scanning: git svn clone -s -r387893 http://plugins.svn.wordpress.org/your-plugin/ You can hunt down that revision by using this command: svn log http://plugins.svn.wordpress.org/your-plugin/ The last line shows the earliest revision. Source: http://teleogistic.net/2011/05/revisiting-git-github-and-the-wordpress-org-plugin-repository/
Yes. You need to: Change stable tag to 0.2 Commit (or copy/branch) new version to /tags/0.2 Don’t forget to update version to 0.2 in plugin’s header
I would only increase the version number if users needed to download the plugin again. The “Tested up to” variable is not used when the plugin is installed, only when people want to install it or want to upgrade. In that case, the information comes from the server anyway, so you don’t need to force … Read more
The easiest way to create a patch is described here: http://wordpress.org/download/svn/ Can I create patches from older version or must I use trunk? You should create the patch against the same version you want it applied against. In other words, don’t expect a patch created against WP 3.0.1 to apply cleanly on WP 3.1-alpha. If … Read more