I am using [site_node_closest_ancestor_package acs-subsite] in the Curriculum package, and then [site_node_apm_integration::get_child_package_id curriculum] in order to retreive the package_id of the single curriculum instance that is allowed in any given subsite ...
In dotLRN, we want to be able to, and are indeed able to, mount one package instance in each club, class, etc. - which proves (I think!) that each class, club, etc is a separate subsite. So far so good...
However, for some reason, clubs and classes aren't "pure" subsites; they are packages with the package-key "dotlrn". Hence [site_node_closest_ancestor_package acs-subsite] won't work as expected. In a default dotLRN 1.0.1 install, it will return the package_id of the "Main subsite", when in fact what I'd like it to return is the package_id of the club or class or whatever subsite the request was issued under. The behaviour will be the expected one if I replace the "acs-subsite" argument with "dotlrn" but the proc will then stop working outside dotLRN!
I suppose my question boils down to how this incompatibility might be solved. By introducing a new package parameter, perhaps? Hmm...
/Ola
Request notifications