Support Team Update for October 4th, 2013

Despite that WordPress 3.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. was successfully dropped last week it’s has been relatively quiet in the support forums. I did not have any specific agenda to discuss in the #wordpress-sfd IRC.

One thing that was discussed is the new auto-update feature of the beta.

If the 3.7 beta detects that the install is running as a subversionSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the released code are all centrally managed through SVN. or git checkout then that feature is disabled. To enable auto-updates (if you are using subversion) you have to delete all the .svn directories in your WordPress installation.

Just take care not to delete the .svn directories of those items that you still wish to use subversion with such as in the themes or plugins directory. Doing a search and delete of all .svn directories in your installation may not be what you really want to do.

In make:coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. there was a very good post written by Dion Hulse discussing this new feature. If you are testing the new beta then please consider enabling automatic core updates.