Hi Sean,
Sorry for the late reply -
On Oct 31, 2008, at 5:15 PM, SeanMcTex wrote:
I did try entering the key manually too as you'd suggested, but
didn't have
any luck.
I eventually figured out, however, that including the Enterprise
module in
the build does the trick. (We had been including only the LDAP
module from
Enterprise in our build up to now, so it hadn't been necessary
before.) Got
the transactional activation working a few minutes ago.
Yeah, you need to enterprise module for your license to be registered
in Magnolia itself.
I was, however, a bit disappointed to see that one can still delete
a page
in the Authoring stage, and problems with deactivating the content
on the
public servers don't prevent the page from being deleted on the
Authoring
stage.
http://jira.magnolia.info/browse/MAGNOLIA-2251
Thus, it's apparently still possible to get Author and Public stages
out of sync if there's a problem during deactivation. :(
If deactivation uses the Transactional activation too, then it
shouldn't - I'm not exactly sure what the state is here, but manually
removing nodes from a public instance isn't exactly the same thing has
prooving that a failed deactivation would make your instances out of
sync.
Cheers,
-g
----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------
