The behavior of the modules fundamentally change in >OXID v.6.2

[TumTum]

• If you save a variable in the backend. The module will be disabled / enabled
• With the command oe-console oe:module:apply-configuration. The module will be disabled / enabled
  • If you have an EE version it will be disabled / enabled per store.

Knowing this, it means that the Events::onActivate() SQL will be executed, and in case of Events:: onDeactivate() tables will be deleted.

We have 9 SubShops with command the oe-console oe:module:apply-configuration.
We will delete the table 9 times and create it again. That means the start page of the store will throw a fatal error as soon as wleWallee_cron is deleted. Or just because you have changed a setting in the backend.

The Event modules are not suitable at all. For the first installation. There rather uses Doctrine module-migration

[theodorspringwallee]

Dear TumTum

Sorry for the late response. According to our devs this was not happening again.

Therefore, I will close this ticket.

[TumTum]

Hi @theodorspringwallee

According to our devs this was not happening again.

What does that mean?
Then you have not understood the problem whatsoever!
These event classes slow down the whole system.

[theodorspringwallee]

Dear TumTum

Sorry, I guess there was a misunderstanding about this issue. Our developers will run now a more in-depth investigation.

[theodorspringwallee]

Dear TumTum

Our developer told me, that we currently can't reproduce your issue on OXID 6.10, where we currently support this.

Are you using an older OXID version?

Best regards

[TumTum]

Very sad. Also in this OXID-CE 6.10 the problem is included. I don't want to explain this to you anymore.
I totally don't care now either. We do not use your module for these reasons.