When both Mollom and webprofiler modules are enabled on dev systems, we see the following error while trying this drush command.

mollom-webprofiler-permissions.png

The same command when only webprofiler is enabled:

webprofiler-permissions.png

We have seen the Mollom error at other times and are concerned about Mollom's stability.

CommentFileSizeAuthor
#2 mollom-update-php.png307.98 KBesod
webprofiler-permissions.png45.07 KBesod
mollom-webprofiler-permissions.png468.62 KBesod
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

esod created an issue. See original summary.

esod’s picture

esod CreditAttribution: esod as a volunteer and commented
FileSize
mollom-update-php.png307.98 KB

Here is another place where these two modules don't play well together.

mollom-update-php.png

Admittedly having mollom and webprofiler enabled on the same system is not a common occurrence because the services the two modules provide are quite different. But mollom is a part of our build and its being enabled is included when we build our local systems. We'd also like to have Web profiler enabled locally as a part of our build, but that's currently not possible because of this issue.

bostonid’s picture

bostonid CreditAttribution: bostonid at Thinkbean commented

Just a note to say we too have a need for mollom and webprofiler running together. We have managed it by performing the following on sites which throw the errors you are seeing:
manually delete the mollom folder
drush pmu webprofiler
composer require "drupal/mollom ~8.1"
drush en mollom
(optional) drush en webprofiler

Not a fix but a workaround suggestion.

yukare’s picture

yukare CreditAttribution: yukare commented

On drupal 8.2 we use composer from root, not from each module. Is not possible just remove the vendor folder from mollom and run the proper commands on drupal root? This will remove the need of add another autoloader in mollom.

eshta’s picture

eshta CreditAttribution: eshta at Acquia commented
Status: Active » Postponed (maintainer needs more info)

So am I understanding correctly that the problem is due to the faulty use of composer.json in the Mollom module? If so, would resolving https://www.drupal.org/node/2840112 also resolve this bug?