Forum .LRN Q&A: Re: IMS-LD Status and Maintenance

Collapse
Posted by Emmanuelle Raffenne on
Hi Derick,

This is great news. Thanks for taking on the imsld package maintainance.

We are about to branch .LRN packages for the next release (2.4.0), imsld should be part of that release.

Currently the situation is, as mentioned in guatemala, that the imsld package is broken on HEAD. Version available on 5-3 branch is working fine.

Do you know what the status of the code on HEAD is or should be? if the code on HEAD shouldn't have changed since .LRN 2.3.1, it would mean that the problem is due to the last merge from 5-3 branch to HEAD.

Collapse
Posted by Derick Leony on
Hi Emmanuelle,

I checked this with Jose and the package hasn't been changed since .LRN 2.3.1.

After reviewing the bug with Jose and some debugging, we noticed this was due to a change in content::folder::new, where now the default parent_id for the folder is the security_context_root instead of the root_folder, as it used to be up to 5-3.

We have changed the proc in IMS-LD in order to work with this and would be able to submit the patch or commit the change in order to include it in .LRN 2.4.0.

Collapse
Posted by Emmanuelle Raffenne on
Hi Derick,

Thanks for looking into this. content::folder::new has been fixed so the default parent_id is now the item_root_folder (as it has to be).

I've tested again imsld and it solved the problem.