Hello,
the following sugar behavior drives me a little crazy (Version is 5.2)
* I create a custom module and deploy it
* I update this module
* I remove the old module and do *not* remove the associated tables- because I need that data
* I deploy the updated module
Now, ordinary users cannot use the module anymore, because the entries in acl_actions are not created after such an reinstall. I consider this a bug.
I came up with the following workaround:
I create a file post_install.php with the following content:
------------------------------------------------------------------
if ($_POST['mode'] == 'Install') {
include_once('modules/ACLActions/ACLAction.php');
$module = 'my_module';
ACLAction::addActions($module);
echo "<h4>ACL-entries for $module created.</h4>";
}
------------------------------------------------------------------
this post_install is included in the manifest as
$installdefs = array (
'post_execute' => array(
'<basepath>/actions/post_install.php',
...
The problem with this is that any rights associated with
my_module are lost. Any ideas?
Thank you.


LinkBack URL
About LinkBacks



Reply With Quote
Bookmarks