Forum OpenACS Development: Re: Is this a bug: right after creating pkg in APM, key is not known but should be

Collapse
17: Re: Is this a bug: right after creating pkg in APM, key is not known but should be (response to 5)
Posted by Jim Lynch on 04/10/10 05:35 AM
no apm_package_type is created for the package
Yes it is, just tested in 5.5. I'll be posting a log. Here is the log: http://jam.sessionsnet.org/files/download/package-error-log.txt?file_id=5669
Collapse
18: Re: Is this a bug: right after creating pkg in APM, key is not known but should be (response to 17)
Posted by Jim Lynch on 04/10/10 05:37 AM
the above log is generated when I click the button on the site map that actually creates the package instance and mounts it.
Collapse
19: Re: Is this a bug: right after creating pkg in APM, key is not known but should be (response to 17)
Posted by Don Baccus on 04/10/10 06:54 PM
You're right, it is. What wasn't being generated was the cache entry for the new package_key, an nsv that I added to implement "extends" and "embeds". I rearranged things in 5.6 a bit to improve the semantics and that leads to the nsv being used in a couple of places where it wasn't used before, and I missed this instance.
Collapse
20: Re: Is this a bug: right after creating pkg in APM, key is not known but should be (response to 19)
Posted by Jim Lynch on 04/11/10 06:31 PM
cool... I don't necessarily mind restarting, but if there's a simple fix that can be backported to 5.5.0 that would make it easier to work... would be appreciated.