|
Tuesday 28 July 2009 11:59:04 pm
Hello, It sounds like the simplest thing to do might be to add workflow event which contains conditional php logic which when assigned to the content module's publish action would add the user email address to the separate tables you describe. Alternately you could simply create copy of the default kernel user module as a module extension. This allows you to basically create a copy and quickly modify the php to provide the additional features to do. We've talked about this in the past [2] Remember you will need to change the module 'name' in the extension/customerExt/module/customer/module.php here is an example $Module = array( 'name' => 'Customer management',
'variable_params' => true );
<i>"2. All modules need to be defined in module.ini[ModuleSettings]ModuleList[] as of 4.1, in 4.0 and earlier this was optional and module list was generated on the fly on each request (lots of file system stat calls)"</i> [3] also remember to do this or your module may not be properly recognized [3,1,0], You may also wish to add these settings to your site.ini append file [RoleSettings] PolicyOmitList[]=customerExt
Cheers,
Heath
[0] http://ezpedia.org/en/ez/module
[1] http://ezpedia.org/en/ez/ez_publish_4
[2] http://ez.no/developer/forum/developer/add_to_basket_multiple_products
[3] http://ez.no/developer/forum/extensions/access_denied_with_custom_extensions_after_upgrade_to_4_1
[4] http://ez.no/developer/forum/developer/passing_custom_parameters_from_shop_userregister
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|
