Tag Info

Hot answers tagged

7

I'm embarrassed to say that I am a bit clueless on the procedure used to update a plugin via tortoise svn even though my plugin has been on the repository for years and had over 300,000 downloads! Don't be. SVN can be tricky for a lot of people ... so let's go through things step-by-step ... This is what I've been doing so far. code the ...


5

@articlestack According to the trac revision log you added a new directory under your root with the same name as the plugin. It looks like your whole root directory got copied to the new directory because it contains all the tagged versions and trunk. The plugin bot will not be able to find your newly tagged version unless it's in trunk or the new ...


5

You already got something like this built in: Revisions. // Define the nr of saved revisions in your wp-config.php define( 'WP_POST_REVISIONS', 30 ); You can simply grab them by calling get_posts() with a post_type of revision. To show the difference between two revisions simply use wp_text_diff(). // Example $revisions = get_posts( array( ...


5

You could use a Git hook and post per XML-RPC to WordPress. A Git hook can be any executable file, even PHP. Another option – on GitHub – is to use the email hook: Go to https://github.com/username/projectname/admin/hooks, select Email and send an email to the blog. Enable the Post per email feature.


5

For the benefit of others who find this page, I suggest those wishing to provide their own updates outside the official WP repository check out this project on GitHub, that demonstrates the functionality: https://github.com/jeremyclark13/automatic-theme-plugin-update


4

Question 1: Should I switch to working with command line instead of Tortoise? will it be safer? No, tortoise SVN does everything you need to do pretty well and without the need for you to learn every command line command. I've used it plenty of time, and I never had problems that were related to it, the problems were related to me using it ;) BTW: Tortoise ...


4

There are two (2) steps. Add the WordPress.org username of the contributor you want to add to the "contributors" line in the header info of the Readme file, and that person will have SVN commit access to the plugin. Go to the plugin repository and log in with the main account Go to your plug-in and click the "admin" tab Add the user's WordPress login ...


3

Dunc, glad you asked about this before it was too late for you. You have heard the right words. You are right, unfortunately the articles tutorials are not very much newbie friendly. Frist let me try to clear some terminology for you. The thing you need to manage your code and keep track of all the changes you make to your plugins is basically called source ...


3

I run a WordPress checkout of trunk, a branch, or a tag. This way I can switch WordPress versions easily: svn sw http://svn.automattic.com/wordpress/trunk svn sw http://svn.automattic.com/wordpress/tags/3.1 In wp-content/plugins I have a trunk checkout for each of my plugins: cd wp-content/plugins svn co http://plugins.svn.wordpress.org/stats/trunk/ ...


2

Yes, this is possible. There's an entire chapter in Professional WordPress Plugin Development dedicated to this. If you haven't already, pick up a copy. It will definitely help.


2

Disclaimer - I am also beginner with SVN. Is this possible? Should be. I am using similar setup, just with WP checked out not from official repository. Are externals what i'm looking for? Nope. Externals are links between repositories. WP plugin repository ignores them for packaging downloads (so they are useless with it). And as I understand you ...


2

First of all, I'm also a beginner in SVN. I'm happy when it's working ;) I'm not completely sure if I understand your question correctly. You have checked out the WordPress trunk and inside this working copy, you want to checkout a plugin from the WordPress plugin directory? Well, I don't know if this is going to work - But you could store your ...


2

My question is whether i can checkin a plugin from directly inside the plugins directory? By 'checkin' do you mean updating the plugin on wp.org (svn commit) or downloading the plugin from wp.org (svn checkout) ? Plugins on wp.org do require the traditional trunk branches tags structure. If you want to work on an svn checkout of a plugin within an ...


2

Okay, looks like this is a problem with windows. I tested this now under linux and it worked like a charm. I have no idea what is causing this, but that specific plugin which is problematic is looking wired in svn anyway. So solution is to use a SVN client on linux. It just works.


2

I've had issues with this as well, and my solution was to use a different form of the plug-in repository URL. They give you: http://plugins.svn.wordpress.org/PLUGIN-NAME With Tortoise SVN I've successfully used: http://svn.wp-plugins.org/PLUGIN-NAME Give that a try and see if it helps.


2

Try changing your password @ wordpress.org then retry. If still fails check your firewall log If it still fails ... ask Andrew Nacin :) http://twitter.com/#!/blamenacin :)


2

License Compatibility As a recent commenter pointed out on my site, it should be possible to distribute a plug-in that's not GPL so long as you don't distribute it with WordPress. However, the guys at WP.org have pointed out time and again that only GPL-compatible plug-ins must be compatible with version 2 of the GPL. So this puts you between a rock and a ...


2

you have to commit the changes to the /trunk directory yourself, changing the version number in the /trunk/readme.txt is not going to do this on its own. Update Whenever i update a version say from 1.0.0 to 2.0.0 i first create a directory in /tags and name it just like the last version 1.0.0 the i copy everything from /trunk to it so if someone wants an ...


2

There are plugins that will let you do this. http://wordpress.org/extend/plugins/user-files/ http://wordpress.org/extend/plugins/wp-filebase/ Whatever you decide though keep in mind security when doing things like this. You don't want people going crazy and uploading huge files either, so check the plugins have built in restrictions on what can be uploaded ...


2

If your code, be it a theme or a plugin, does not support translation, then don’t use the translation functions. And if you don’t use these functions, you cannot use a text domain. :) There is a very common error that looks like this: echo __( 'Portfolio' ); Portfolio is not part of WordPress’ core strings, so this code will waste an expensive look-up in ...


1

There is this commercial Plugin and Theme Update API manager for WooCommerce that specifically works if the plugin or theme is not hosted on wordpress.org. It is designed to provide updates for self hosted plugins and themes. The plugin is for those who don’t want to write it yourself, and need a lot of features, plus working examples for plugins and themes ...


1

The link was created automatticly, if you have a profile on wordpress.org. As example: see my profile: http://profiles.wordpress.org/bueltge/ and see also a plugin of my, same user-slug: http://wordpress.org/plugins/adminimize/ But it is important, that you write case sensitive. The user must include in the readme of the plugin, on the string ...


1

The answer is already detailed here.. https://github.com/Automattic/_s#getting-started Unless you want something else. :) Basically once you have a starter Underscores theme, it's all a matter of editing the template files to get it to look the way you want it to.


1

The easiest thing I think is to ask wordpress.org if it's possible that they host your plugin with GPL v3+ compatibility. Probably they say yes. Give it a try, the discussion was very new back in the end of January so points of views might be a bit more settled these days. IMHO there is not really something to loose if they allow GPL v3+ plugins in the ...


1

As of May 2012 plugin repo rules have been updated, allowing Apache License 2.0 and some other previously incompatible licenses: The plugin directory’s licensing guidelines have been updated. The guidelines will now allow code that is licensed under (or compatible with) version 3 of the GPL. The guidelines still encourage use of “GPLv2 or later,” ...


1

Official requirements say that code should be GPLv2-compatible. Note that actual page they link to is for GPL-compatible of unspecific version and includes GPLv3 as well. Quick search show some GPLv3 plugins in repository so that one should be fine. Definite no on proprietary components, unless you convince developers to release or dual-license their code ...


1

Github will document each change automatically as you push the code to your repository which is a very useful feature among a ton that Github offers. Another useful feature for public repositories are that anyone can contribute by sending you bug reports and fixed code snippets . Note that private repositories are not free as in beer, so all of your code, on ...



Only top voted, non community-wiki answers of a minimum length are eligible