[Building Sakai] [Deploying Sakai] Issue in 2.7.x content branch from 18 May to 1 Aug

[Angela Rabuck]

Can u check to see if the "bad" code is installed on our servers?  

Thanks
Angela

Sent from my iPhone

On Aug 5, 2011, at 9:02 AM, Daniel Robinson <d.b.robinson at lancaster.ac.uk> wrote:

> Hi Stephen,
> 
> We updated our production instance of 2.8.x late June and have some worksites experiencing what seems to be the same problem.
> 
> We'd appreciate any help you can offer with the cleanup scripts.
> 
> Best wishes,
> 
> Daniel
> 
> On 5 Aug 2011, at 14:13, Anthony Whyte wrote:
> 
>> The ticket in question that tracks this issue is SAK-20280.
>> 
>> https://jira.sakaiproject.org/browse/SAK-20280
>> 
>> It appears that 2.8.x was also affected by this bug between r92647 (Mon 5 May 2011) and r96021 (Mon 1 Aug 2011).
>> 
>> Second, a cursory review of the commits associated with SAK-20280 suggests that the content.properties commit r92656 (Thur 5 May 2011) is missing from 2.8.x but the properties file change was indeed merged (r92657) though linked to SAK-20264.
>> 
>> Cheers,
>> 
>> Anthony
>> 
>> 
>> On Aug 5, 2011, at 3:47 AM, Stephen Marquard wrote:
>> 
>>> Hi all,
>>> 
>>> There was a bug in the 2.7.x content branch between r93034 (Wed 18 May)
>>> and r95999 (Mon 1 Aug) which led to incorrect release and retract dates
>>> being set on content folders or items whose properties were updated
>>> (e.g. setting a quota on a site's resources folder, or updating a
>>> description). This does not affect any 2.7 releases, only the
>>> maintenance branch between 2.7.1 and 2.7.2 (still to be released).
>>> 
>>> The effect of the bug was to set a release date of the current date
>>> (when it was revised) with a retract date 7 days later. Hence in due
>>> course, many resources (and entire folder structures) became hidden
>>> unexpectedly.
>>> 
>>> If you had this code in production at any time, your users may have
>>> been exposed to this issue (and may not realise it until some time
>>> later). We unfortunately fell into this trap at UCT, and have written
>>> some cleanup scripts to fix the affected resources which we can share if
>>> anyone else runs into the same situation.
>>> 
>>> Regards
>>> Stephen
>>> 
>>> 
>>> Stephen Marquard, Learning Technologies Co-ordinator
>>> Centre for Educational Technology, University of Cape Town
>>> http://www.cet.uct.ac.za
>>> Email/IM/XMPP: stephen.marquard at uct.ac.za 
>>> Phone: +27-21-650-5037 Cell: +27-83-500-5290 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ###
>>> UNIVERSITY OF CAPE TOWN 
>>> 
>>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer
>>> published on our website at
>>> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from
>>> +27 21 650 9111. This e-mail is intended only for the person(s) to whom
>>> it is addressed. If the e-mail has reached you in error, please notify
>>> the author. If you are not the intended recipient of the e-mail you may
>>> not use, disclose, copy, redirect or print the content. If this e-mail
>>> is not related to the business of UCT it is sent by the sender in the
>>> sender's individual capacity.
>>> 
>>> ###
>>> 
>>> _______________________________________________
>>> production mailing list
>>> production at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/production
>>> 
>>> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>> 
>>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>