Why Subversion is not a complete way to update WordPress

Since you’re already typing commands to the server, why not use wget and unzip to download themes and plugins?

That way there’s no need to download them to your computer before uploading them again to the server.

Also, with the right permissions, casual users can update everything by clicking around in the admin interface. There’s no need for them to dabble with this stuff.

Since you’re already typing commands to the server, why not use wget and unzip to download themes and plugins?

That way there’s no need to download them to your computer before uploading them again to the server.

Also, with the right permissions, casual users can update everything by clicking around in the admin interface. There’s no need for them to dabble with this stuff.

The whole idea is type minimal commands. With wget, things get out of hand when it comes to updating plugins.

I understand that everything can be managed via the dashboard, but thats not the case when it comes to some servers that do not allow Safe mode to be disabled. Also, FTP connections are insecure.

I still see potential in Subversion, however with some streamlining.

There is a move towards Subversion among the more advanced WordPress users. I am trying to understand whats in there for the casual user and how it can be improved.

The crux of that post, to me, is this:

While updating WordPress through SVN is a breeze, the same does not apply to updating (or installing) additional themes and plugins.

SVN is fine for WordPress core, but no, I don’t use it for themes and plugins. I use the built in auto-update tools for that.

I use svn externals on a couple of sites for updating themes and plugins as well as core. Works fine. I detail a method of doing this here:

https://ottopress.com/2011/creating-a-wordpress-site-using-svn/

Thanks for the link…posted to article.