understanding content-module behaviour
Posted: Tue Dec 29, 2009 4:49 pm
i have read the manual belonging to the content-manager, but i still have a general question about the way the content-modules are meant to be.
in our company, the sales department creates the monthly newsletter as a text-document. when it's finished, they add it to openemm(, during the past with templates).
to make it more comfortable for them, i decided to divide the template into 6 modultypes and content-moduls.
with our own cm-template and these content-moduls, they can easily add the content-moduls to the mailings.
but, when you add a content-module to mailing A and modify it, you are taken back to the content-manager and the content-module-editor page to edit the 'general' module.
this means that you always edit the basic module.
so changes in mailing A will affect mailing B with the same module. (beside we don't change the mailing, but the module).
is this how the content-manager is meant to be?
i thought, it should be like you add a module to a mailing like a copy of the module which you can edit for this single mailing and which does not influence other mailings.
the only would it could work for us, would be to build the same content-modules for every mailing again with different names.
but i am sure that this is not who it is supposed to be.
tia
pheelix
in our company, the sales department creates the monthly newsletter as a text-document. when it's finished, they add it to openemm(, during the past with templates).
to make it more comfortable for them, i decided to divide the template into 6 modultypes and content-moduls.
with our own cm-template and these content-moduls, they can easily add the content-moduls to the mailings.
but, when you add a content-module to mailing A and modify it, you are taken back to the content-manager and the content-module-editor page to edit the 'general' module.
this means that you always edit the basic module.
so changes in mailing A will affect mailing B with the same module. (beside we don't change the mailing, but the module).
is this how the content-manager is meant to be?
i thought, it should be like you add a module to a mailing like a copy of the module which you can edit for this single mailing and which does not influence other mailings.
the only would it could work for us, would be to build the same content-modules for every mailing again with different names.
but i am sure that this is not who it is supposed to be.
tia
pheelix