Obsolete EmporiumPlus CIM Activity Log

[lesliekirk]

Does anyone know how many of the obsolete EmporiumPlus modules rely on the obsolete CIM Activity Log? I have been advised that it seems to be the source of the built-in coupons not re-caculating correctly and to remove it. I need to know what sort of cascading effect this is going to have in a store that still has a number of these obsolete modules still running.

[eldon99]

Leslie,

I found about 38 Emporium Plus modules in my archives that I have installed for clients over the years, and of those, the following modules had the CIM Activity Log module:

b2bnotax
external
followon
mailman
minibask
volprice

Hope this helps.

Regards,

Darren

[eldon99]

Forgot to include:

coupon

[lesliekirk]

Leslie,

I found about 38 Emporium Plus modules in my archives that I have installed for clients over the years, and of those, the following modules had the CIM Activity Log module:

b2bnotax
external
followon
mailman
minibask
volprice

Hope this helps.

Regards,

Darren

Thanks, Darren. This has been a rather arduous journey.

[Kent Multer]

Hi, I'm reviving this thread because one of my clients is having the same problem. I removed the Mail Manager module from their store, because it was generating runtime errors, even though it had been deactivated. (How is that even possible???)

Once I did that, I found that cim_log was throwing runtime errors at the same point where the Mail Manager used to (when clicking the Save button to create a customer account). So I deactivated cim_log ... but I'm wondering if that will cause other problems? The store is still running Toolkit and some other Weiland modules, although many of them are not actually being used any more.

(By the way, all of the above is happening in the dev store. I figured I should try it there before removing any modules from the live store.)

Does anyone know what the cim_log module actually does? And by association, what happens if I deactivate or remove it?

Thanks --