Samuel Wood (Otto) 4:50 pm on February 3, 2011
Tags: extend ( 5 ), themes ( 43 ), wporg ( 10 )

Theme pages now have a little “Theme SV…

Theme pages now have a little “Theme SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase.” link in their FYI box. This just gives a link to the theme’s SVN, for people that want to use it.

This is something several of the theme reviewers asked for, and it fits with the long term goal of allowing some theme authors the ability to directly update themes via SVN instead of using the ZIP file uploader. Encouraging SVN use is a good thing, I think.

#extend, #themes, #wporg

Rich Pedley 6:52 pm on February 3, 2011

That just lists all the versions, ala the ‘Other Versions »’ link on pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party pages. Shame it can’t be WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/-ified rather than a simple listing though.
- Otto 6:54 pm on February 3, 2011
  
  That’s what it’s supposed to do. The theme SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. isn’t organized like the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party SVN, with trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. and tags and such. It just has one directory for each theme version.
  - Rich Pedley 7:28 pm on February 3, 2011
    
    So it could be pulled into a WordPress themed page then…
    
    😉
  - Dion Hulse (dd32) 1:13 pm on February 5, 2011
    
    Rich: Given it’s a SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. repo, I’m not really sure it’s possible to style it like WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. That aside, as it’s a SVN repo, it’s not designed to look like WordPress.org 🙂
  - Rich Pedley 8:09 pm on February 5, 2011
    
    On a site such as WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ having unstyled pages like that is very un-professional. I still think the data could be pulled into a themed page, and even if it can’t I have seen better web front ends for SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase..
  - Peter Westwood 10:08 pm on February 5, 2011
    
    You can style the SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. web interface but I wouldn’t want to be the person writing the XSLT to do it – it’s not fun and you won’t make it look much better – I don’t see why it needs styling at all.
  - Alex M. 6:58 am on February 6, 2011
    
    If you want to look at a pretty version of the code, then use the plugins TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. instead of browsing the directory via SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase.. Or even better just use a proper SVN client.
    
    The SVN repository isn’t really meant for browsing with your browser. 😉
  - Matt 6:14 pm on February 6, 2011
    
    I think it would be worth a little XSLT to just put a note at the top, like “This is blah blah blah for the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party’s page please see LINK or visit WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.”
Radhe 6:45 am on February 4, 2011

This is welcome addition,
but I do think “trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.” folder should be given, that will be helpful when author modify theme code in response to theme-users support request.
Dion Hulse (dd32) 1:13 pm on February 5, 2011

Could we get the same thing for Plugins?
- Otto 6:00 pm on February 5, 2011
  
  Plugins have had the SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. links in their Adminadmin (and super admin) sections forever. Not sure it’s worth exposing them on the public side of things.
  - Dion Hulse (dd32) 10:34 pm on February 5, 2011
    
    Not everyone has access to the adminadmin (and super admin) section of every pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
    
    I personally see SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. access for Plugins as more useful than for Themes. Every task is common between them however (Other than Theme review team stuff, but thats a not a normal front end task anyway). Allowing easier access to the SVN repo from the plugins page will help people who are not aware of SVN get into it at well, encourage them to use svn..
    
    One of the first thing I do, and I’d hope other Plugin developers do, is open the plugins SVN repo and take a glance at the code, it’s what tells me if I’m going to atttempt to use it or not. That’d be my main use for it for Plugins (as well as for Themes).
  - Rich Pedley 9:37 am on February 7, 2011
    
    erm plugins already have a link to the Development log in the FYI box. This was what I was referring to when I thought that the themes should match it.
Denis 6:00 am on February 12, 2011

Slightly off topic, but… It just occurred to me that the default vote for compatibility was for 3.1 at a time where it was not released. As much as I like the idea that one can vote on works/broken for the latest 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./RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)., it seems to me that the vote should apply to the latest and greatest *released* WP version by default. (Or maybe it already is the case, in which case it’s not clear at all…)
- Denis 6:01 am on February 12, 2011
  
  i’m meaning for plugins, btw. But since you’re also worrying about that and I can only assume the same logic applies for themes, I figured I’d raise it here.

Comments are closed.

Welcome!

Communication

Theme pages now have a little “Theme SV…

Welcome!

Communication

Share this: