{"id":700,"date":"2015-01-28T10:17:30","date_gmt":"2015-01-28T14:17:30","guid":{"rendered":"http:\/\/192.168.1.60\/techblog\/?p=700"},"modified":"2015-03-14T11:20:49","modified_gmt":"2015-03-14T15:20:49","slug":"wordpress-svn-on-a-mac","status":"publish","type":"post","link":"https:\/\/tech.creed3.com\/?p=700","title":{"rendered":"WordPress SVN on a Mac"},"content":{"rendered":"

\"\"Having recently taken the plunge in to WordPress plugin development, I decided to offer one to the community and become ‘official’.  To do so one must be at least somewhat familiar with the idea of version control, but then I needed to dig in to the system WP uses, Apache Subversion.<\/p>\n

Not even being acquainted I first needed to find out about it and could I run it on a Mac.  In short order I discovered that Apple installs Subversion on every Mac.  Wonderful!  Or. . . not.  Maybe they used to, but today it’s part of the Xcode library which is not automatically installed on Macs, but it is a free developer library.  Okay no prob.  Except, ummmm, I’m still using Mountain Lion (yeah, yeah, I know) for my main production machine and Apple no longer makes Xcode available for that OS.  After some digging I discovered it’s possible to install Subversion on a Mac via a number of different methods<\/a> of which I chose to install Homebrew<\/a> to handle this task.  Done!<\/p>\n

Time to read up on how Subversion works<\/a> and what it does.<\/p>\n

Subversion is a command line tool.  I can do command line stuff but much prefer a GUI when ever possible.  More digging, and I discover the awesome Mac community comes through with an open source offering (among the many purchase-able options) in SvnX<\/a>, which is also pretty highly rated to boot.  After downloading and installing, I then poke around at SvnX for a while to get a feel for how it works in relation to Subversion.<\/p>\n

There was also reading to do on what WP has to say<\/a> about how they use Subversion.<\/p>\n

After hours of careful reading and research it was finally time to give it a shot.  Using my WP credentials and the location of my newly attained plugin repository, I was able to log in and ‘check out’ the empty project.  Worked like a charm, creating the necessary folders where I directed.  Then per WP instructions I needed to copy my files in to the ‘working copy’ trunk folder and then commit the changes (or, upload the files).  But, I kept getting an authentication error, which was completely unexpected since I just used those same credentials to log in and initiate all of this.  Back to searching.<\/p>\n

After an hour and numerous attempts to get it york I came up empty handed.  So I opted to quit SvnX and restart in hopes that for some reason my credentials I had entered were not getting written to a config file somewhere which was affecting this.  That did seem to be what was happening.  But when I opened the working files window again, this time I got an error that the current version of Subversion wasn’t high enough to work on those files.  The very files it had created not an hour earlier.  Back to searching.<\/p>\n

All I could find was something indicating this error was caused by trying out a newer version of Subversion, and then going back to a previous version, which I had not done.  I checked and had the absolute latest version installed.  So forget that, I’ll ‘check out’ the project again and let it work with a fresh copy.  None doing.  There was a hidden project file that wouldn’t allow that.  Grrrrr. . . .  So I delete the entire folder structure, recreate the base folder, then ‘check out’ the project again.  This time it worked.  I re-copied my files in to the trunk folder.<\/p>\n

I need to mention during all of my searching I read that there are 2 ‘commit’ buttons in SvnX, one on the ‘working copy’ main window, and then another on the review window, which is the method someone associated with SvnX said to use<\/a>.<\/p>\n

So time to try it again and this time with the review button.  Success!<\/p>\n

Hopefully something here will help someone struggling with this same problem.<\/p>\n","protected":false},"excerpt":{"rendered":"

Having recently taken the plunge in to WordPress plugin development, I decided to offer one to the community and become ‘official’.  To do so one must be at least somewhat familiar with the idea of version control, but then I needed to dig in to the system WP uses, Apache Subversion.<\/p>\n","protected":false},"author":9,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,16,30,41],"tags":[32,31],"class_list":["post-700","post","type-post","status-publish","format-standard","hentry","category-mac","category-technology","category-web-development","category-wordpress","tag-plugin","tag-wordpress"],"views":1869,"_links":{"self":[{"href":"https:\/\/tech.creed3.com\/index.php?rest_route=\/wp\/v2\/posts\/700","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tech.creed3.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tech.creed3.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tech.creed3.com\/index.php?rest_route=\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/tech.creed3.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=700"}],"version-history":[{"count":0,"href":"https:\/\/tech.creed3.com\/index.php?rest_route=\/wp\/v2\/posts\/700\/revisions"}],"wp:attachment":[{"href":"https:\/\/tech.creed3.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=700"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tech.creed3.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=700"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tech.creed3.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=700"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}