Upgrading ^1.1 => ^2.0

Thank you so much for your detailed description and your suggestions. This is great input altogether.

In detail:

The described step by step process sounds perfect.

Finally then, I then issue a drush eca:update and the result is...

Pretty much no feedback which is probably a good thing but I think at least 'done successfully' for each update might be useful.

That's correct, and I see that being not ideal. I've opened ✨ Add feedback to the eca:update drush command Active to address that.

What I do see is...

[error] The action plugin comment_unpublish_by_keyword_action can not be initialized. ECA is ignoring this action. The issue with this action: The "comment" entity type does not exist.

...and I'm going to assume there that that 'error' didn't stop proceedings but I I don't know that for sure.

Where and when do you see that output? I know where it comes from: Drupal has removed some action plugins in 10.3 and the message above means that at least one of your models seems to be using this action. You should find out which one and remove/replace that action with something else.

... my more complex ECA models and they appear to be working as normal but like I said, I cannot be certain of that ...

Here is what we've done to address that: for our business critical ECA models, we've write automated end-to-end tests for all scenarios in those models. We run them in our project related pipelines for every update, and that way we can be certain that nothing broke. I know, this is a lot of work to prepare, but it feels great and pays back quickly.

"Update existing ECA models with drush eca:update" - 'drush' is missing.

Thanks, I've fixed that right away. The same issue existed also in the release notes @ https://www.drupal.org/project/eca/releases/2.0.0 → , of course as a result of copy & paste.

Question RE shared hosting

Great suggestion, we should follow up with that at ✨ Make eca:update available through the UI Active .

Brilliant @jurgenhaas → , thank you for all the clear clarification.

I was seeing the error message...

[error] The action plugin comment_unpublish_by_keyword_action can not be initialized. ECA is ignoring this action. The issue with this action: The "comment" entity type does not exist.

As the only output from the drush eca:update command.

I do not use appear to be using the comment_unpublish_by_keyword_action anywhere in any of my models which stands to reason given that I do not even have the Comment module active.

However, what I did have was the core (deprecated) Actions UI module active and it seems that once I had uninstalled that and re-run a drush eca:update the same error message does NOT show so we can probably safely assume that the deprecated module was the root cause.

I will await any movement on https://www.drupal.org/project/eca/issues/3458517 ✨ Make eca:update available through the UI Active then try it out on my shared hosting as and when it's ready to test.

However, what I did have was the core (deprecated) Actions UI module active and it seems that once I had uninstalled that and re-run a drush eca:update the same error message does NOT show so we can probably safely assume that the deprecated module was the root cause.

Agreed, that sounds about right.

So, I'm closing this one as fixed then.

Similarly, when upgrading from ECA 1.1 to 2, I ran updatedb. When the system tried to run the update "eca_post_update_rename_tokens_2_0_0", there was an error: The "node_assign_owner_action" plugin does not exist.

I wasn't using the "change the author of content" action that is in ECA 1.1, but I'm guessing it's used by the core module Actions UI. I'm hesitant to mess with core, so I'm just going to wait until the Drupal 11 release scheduled for July 29, when the deprecated Actions UI module is to be removed from core. Then I'm going to re-run drush updatedb and drush eca:update, and see if the problem is resolved.

Automatically closed - issue fixed for 2 weeks with no activity.