Hi Bert, Yep, exactly--that neatly summarises what I'm seeing. If this is the expected behaviour then I'm happy and can work with it.
Thanks, Mark Bert Pareyn <[email protected]> writes: > Hey Mark, > > If I'm reading this correctly I'd say this is expected behaviour. > From the moment you upload a new version the data that's set on the current > version will be stored, the data that's set after that upload will not be > applied to that created version. > Further break down of your workflow: > > - Upload new version through add content widget, creates version 1.0 and sets > the description to 'V1'; > - Upload second version, this takes description 'V1' and creates version 1.1. > Afterwards you change the description to 'V2'; > - Upload a third version, this takes description 'V2' and applies it to 1.2. > > Results: > > - 1.0 has description of V1 > - 1.1 has description of V1 > - 1.2 has description of V2 > > So, in short, users would have to change their description to 'V2', 'V3', > etc. prior to uploading a new version. > > Hope to help (and make sense) > - Bert -- Mark Triggs <[email protected]> _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
