Error: Call to a member function checkIfEmpty() on null in Drupal\ai_automators\AiAutomatorEntityModifier->baseShouldSave()

Could you first try the following (if you didn't):
1. Run either "drush updb" or the update.php page.
2. Make sure to flush the cache.
3. Make sure that AI Automators are enabled and not AI Automator (we did a name change).

If that is done, could you please give back the following information:
* What was the branch/commit you had before updating (if you know).
* What is your current branch/commit according to composer.lock.
* Which automator type on which field type.

Hi Marcus,

Thanks for the quick reply. The automaton I ran (I didn't try other entities that have multiple automators) was the google_places automator.

I did run updatedb and cr.

Composer.lock holds this information related to the branch I was on (and now restored to again):

 {
            "name": "drupal/ai",
            "version": "dev-1.0.x",
            "source": {
                "type": "git",
                "url": "https://git.drupalcode.org/project/ai.git",
                "reference": "8be49dd66b7ee604f826e0fb3b1fea16bb8f17ba"
            }

Hope this helps, let me know if there's anything more I can provide.

Could you give me the google_places version as well from composer.lock and I will try to replicate why it can't find it.

Hi Marcus,

Sure, the Google places composer.lock info reads:

{
            "name": "drupal/google_places",
            "version": "1.0.0-beta1",
            "source": {
                "type": "git",
                "url": "https://git.drupalcode.org/project/google_places.git",
                "reference": "1.0.0-beta1"
            },

Ah, I did not release the new version after the update to AI Automators. If you try composer update there should be beta2 now. It was prepared and I forgot... sorry about that.

Hi Marcus, no problem, and thanks for the guidance and the new release. I just updated and it works great again :)

So I don't break your site again :) The AI dev branch will be connected to the Google Places dev branch. If you want to keep it stable for now use the alpha versions with the beta version.

There will probably be a breaking change today again for AI Automators on dev branch, requiring dev branch of Google Places.

Sorry for the inconvinience, but the API changes a lot when we add stuff and recognize that we need more flexibility - this change is so we can handle moderation states in the the Automators for instance. It will probably be so until its out of experimental state.

Thanks, I'll use the alpha version of AI with the beta of google_places. Life on the bleeding edge :)

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

unassigning