Attempting to edit a content type throws a PHP Call to undefined method error

Hmm, looks like not all cache backends implement invalidateTags.

What we're doing is to cache all the heavy lifting about entity types and bundles and what subscriptions they support. But we need to invalidate those caches, when any content type setting gets changed. That's why we call

$this->cacheBackend->invalidateTags(['danse.cache:' . $this->pluginId]);

So, I wonder what should be done instead, any suggestions much appreciated.

I'm also getting this when I try to update a content type or comment type. It even happens when I'm not making any DANSE-related changes, which is frustrating.

The good news is that even though the error occurs, changes do seem to be applied when you reload the page (by going to the URL bar and hitting return to force the page to that URL).

Unfortunately, I don't know enough about Drupal Caching to understand why the error is occurring or how to fix it.

I'm reaching out on Slack, maybe somebody can help us there.

In the meantime, I've disabled the cache invalidation which causes the exception. That means, you won't see this error anymore. The downside is that changed DANSE settings will not be reflected for users until you flush your cache once.

Got some help on Slack. There is a cache tag invalidator service in core, that allows us to do all that regardless of the used cache backend. I've implemented that in the dev release. Please give that a try.

After updating to the latest dev release, the content type edit page no longer throws the PHP error upon saving.

However, after allowing subscription for content type (in this case it was for the publish and comment events), navigating to an existing node of that content type now throws the following PHP error:


LogicException: The database connection is not serializable. This probably means you are serializing an object that has an indirect reference to the database connection. Adjust your code so that is not necessary. Alternatively, look at DependencySerializationTrait as a temporary solution. in Drupal\Core\Database\Connection->__sleep() (line 2042 of /public_html/core/lib/Drupal/Core/Database/Connection.php).


Since updating I have run drush updated and cleared the cache several times. The error persists.

The second error sounds like this one: 🐛 LogicException: The database connection is not serializable. Fixed

Can you confirm, that you see the same stack trace there?

It is indeed the same.

I had not encountered this issue prior to the latest dev release.

However, I've only been performing some very limited testing of this module to date. Consequently, it may have been present or present in different places, but my testing hasn't triggered it before now.

@Janner I think we should be able to set this one to RTBC, can't we? And with regard to the other error, please have a look at the other issue and if that's RTBC'd as well, we can publish another release.

Thanks

Also confirming that the error is gone on my end. Thank you for all your hard work on this. :)

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