WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #25351, comment 3


Ignore:
Timestamp:
09/18/13 22:25:44 (4 years ago)
Author:
rohitink
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25351, comment 3

    initial v1  
    11Yes, the changes are too many. This does indeed create the problem of backwards compatibility. Since, the changes are too many, so it wouldn't be efficient to create a custom build. As newer themes/plugins would prefer to use the latest version of this script. 
    22 
    3 But, to offer compatibility to older themes/plugins, we can include the 2 versions, and give access to the older(2.1.05) version by default. And the developers who would like to use the latest version, should expicitly state the version. 
     3But, to offer compatibility to older themes/plugins, we can include the 2 versions, and give access to the older(2.1.05) version by default. And the developers who would like to use the latest version, should use something like 'jquery-masonry3' in the {{{wp_enqueue_script('jquery-masonry3')}}} function call. 
     4 
     5This update is important, as it has been backed by a lot of theme reviewers at our mailing list. 
    46 
    57And we can remove the older version in any of the coming updates.