IN RELEASE

New date format for artist comment pages

TODO

Restricted page access via unique email link

Clean up the foreach clone >= $version code in functions.php- WRAP IN FUNCTION if possible

^ The first 2 versions of this (save new deployed/not deployed) loop do not have the <= $version clause

?? Think this is expected as you are inserting new version which must be the max version. As $version does not exist in this scenario, the <= clause cannot be used...

?? Can't seem to wrap array build into function... none of the > versions from rc end up in prod when creating new clone of deployed bersion in rc.

Introduce notification labels to state whether the last action was pushed to clone DB?
i.e.
CMS version 536 has been updated but is not deployed (keep grey and keep message as is)
It was also pushed to the PRODUCION database (maybe green)

If we want to start listening to whether switches are changed, we'll need to start giving these inputs unique IDs. Currently they are all set to true/false and I am not sure this needs to be this way? Their value should be true/false as they are currently, but surely their IDs can be unique...? They could have the same ID as their name I think - test this and potentially make this change to all switches prior to investigating event listeners and subsequent jQuery functionality.
^ DONE

Further to this, after next deploy investigate having two j-confirm models - 1 modal and 3 modal versions. JS vars can deal with the content on a case basis.

Check this page:
http://jsfiddle.net/fXnFF/2/

It works with an if method like so:

    $("#myTextBox").bind("change paste keyup", function() {

    var t = $(this).val();

    if (t == 2){

       alert(t);

       }

    });