Just a very strange phenomena:

After installing workbench moderation it is impossible to type in more than one term in taxonomy fields in content types were workbench is switched on. If i disable worbench on this content type, input of taxonomy terms works again.

If I go to the "edit" page of the administration of a content type, i get only a blank page ... this problem is independent if workbench is enabled or disabled on this content type. So maybe this is not related to workbench.

Comments

MartinMa created an issue. See original summary.

becw’s picture

becw commented
Status: Active » Postponed (maintainer needs more info)

If you update to the latest development, is this issue still present? The issue with entering taxonomy terms may be related to #2650388: Using Inline Entity Form widget on Moderated type causes "LogicException: The database connection is not serializable. ", which was fixed yesterday. That bug would not have affected the content type configuration edit pages, though.

martinma’s picture

martinma commented

Thanks for your quick response.

Now i can add more taxonomy terms but if i add a new node i get following messages:

Notice: Undefined index: weight in Drupal\Core\Config\Entity\Query\Query->Drupal\Core\Config\Entity\Query\{closure}() (line 97 of core/lib/Drupal/Core/Config/Entity/Query/Query.php).
.....

Notice: Undefined index: weight in Drupal\Core\Config\Entity\Query\Query->Drupal\Core\Config\Entity\Query\{closure}() (line 97 of core/lib/Drupal/Core/Config/Entity/Query/Query.php).

Warning: uasort(): Array was modified by the user comparison function in Drupal\Core\Config\Entity\Query\Query->execute() (line 98 of core/lib/Drupal/Core/Config/Entity/Query/Query.php).

But i am still not able to create a new content type (i didnt report this in my first bug report) and to get to the first menu of editing content types.

When i restored a backup where worbench was still enabled the website didnt work and i got following error message:

The website encountered an unexpected error. Please try again later.
Recoverable fatal error: Argument 4 passed to Drupal\workbench_moderation\EntityOperations::__construct() must implement interface Symfony\Component\EventDispatcher\EventDispatcherInterface, none given, called in /medjxcwh/drupal.mediaweb.at/core/lib/Drupal/Component/DependencyInjection/Container.php on line 273 and defined in Drupal\workbench_moderation\EntityOperations->__construct() (line 59 of modules/workbench_moderation/src/EntityOperations.php).

Restoring an older version of the website without workbench installed all worked well.

Unfortunately its a production site (but only around 20 pages to restore)

Crell’s picture

Crell commented

At this point, WBM is not a supported release. Please DO NOT USE IN PRODUCTION, as BC is not guaranteed, at all. Not until we tag a beta at least.

I suspect the errors you're seeing are due to pre-existing transitions that didn't have a weight field on them, which was added very late last week. (I think right before the alpha2 tag.) The code isn't designed to handle a transition that doesn't have a weight associated with it, hence kaboom. The second error is due to the signature of class's constructor changing for a new dependency. A full cache rebuild (to rebuild the container) should resolve that, but again, please do not use WBM in production yet.

Crell’s picture

Crell commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

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