I have managed to deal with the non-existant config errors and it is working now, so this is fixed as far as I am concerned. Thanks.
@gapple, thanks for the drush suggestion. This confirms that csp.settings is not being installed. I have tried completely uninstalling and reinstalling the module but the error persists. I get a WSOD when installing the module using extend, dblog mainly reports a lot of non-existent config entity name
errors.
@gapple, when you wrote "What are the values in your configuration for csp.settings:enforce.reporting and csp.settings:report-only.reporting?" were you referring to settings in the configuration file that should be at https:///admin/config/system/csp? This file is inaccessible because of this issue or is absent.
Other issues resulting in the above TypeError seem to be resolved by eliminating the offending null value.
I have the same, i.e. Drupal : 11.1.5 and csp installed with composer require 'drupal/csp:^2.2', and the error persists.
johnwt โ created an issue.
I have now, I get:
Error: Class "Drupal\flexible_permissions\Cache\MemoryCacheFactory" not found in Drupal\Component\DependencyInjection\Container->createService() (line 261 of /var/www/web132/drupal/web/core/lib/Drupal/Component/DependencyInjection/Container.php) #0 /var/www/web132/drupal/web/core/lib/Drupal/Component/DependencyInjection/Container.php(179): Drupal\Component\DependencyInjection\Container->createService()
This is how I attempted the upgrade:
**:~/drupal$ composer require 'drupal/group:^3.3'
./composer.json has been updated
Running composer update drupal/group
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/group ^3.3 -> satisfiable by drupal/group[3.3.0, ..., 3.3.x-dev].
- drupal/group[3.3.0, ..., 3.3.x-dev] require drupal/flexible_permissions ^2.0 -> found drupal/flexible_permissions[dev-2.0.x, 2.0.0, 2.0.1, 2.0.x-dev (alias of dev-2.0.x)] but the package is fixed to 1.1.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
**:~/drupal$ composer require 'drupal/group:^3.3' -W
./composer.json has been updated
Running composer update drupal/group --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 2 updates, 0 removals
- Upgrading drupal/flexible_permissions (1.1.0 => 2.0.1)
- Upgrading drupal/group (3.2.2 => 3.3.3)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 2 updates, 0 removals
- Upgrading drupal/flexible_permissions (1.1.0 => 2.0.1): Extracting archive
- Upgrading drupal/group (3.2.2 => 3.3.3): Extracting archive
The entire site then became inaccessible with the message:
"The website encountered an unexpected error. Try again later."
I reverted to group 3.2.2 in order to be able to access the site. dblog had the errors:
Error: Class "Drupal\flexible_permissions\Cache\MemoryCacheFactory" not found in Drupal\Component\DependencyInjection\Container->createService() (line 261 of /var/www/web132/drupal/web/core/lib/Drupal/Component/DependencyInjection/Container.php).
and
Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "router.route_provider", path: "options_request_listener -> router.route_provider -> cache_tags.invalidator -> cache.flexible_permissions_memory -> cache.backend.corefix_memory_no_serialize -> maintenance_mode_subscriber -> url_generator". in Drupal\Component\DependencyInjection\Container->get() (line 149 of /var/www/web132/drupal/web/core/lib/Drupal/Component/DependencyInjection/Container.php)
and two more error messages referring to flexible_permissions.
Module is still not upgradable from 3.2.2 to 3.3. due to requiring flexible permissions 2.0.1 which is replace by a core API.
Still the same when attempting to update to 3.3.1
johnwt โ created an issue.
What is the situation now? I am on D10.3 and using the core Workflows module but I am having difficulties with getting nod visibilities to correspond to workflow states. Is this Workflow module still maintained and will it work in D11?
In D7 the contributed Workflow module together with roles seems to be what works. A problem seems to be that the contributed Workflow module does not seem to be up to date, it says it is a D8 version and needs a lot of work. Instead there is a Workflows module (note the "s") in the core. This enables workflow states to be set but doesn't seem to set corresponding permissions for each node.
3398288-write-a-proper-readme-md/README.md says go to Administration ยป Structure ยป Homebox but in Drupal 10.2.4 I only have Administration ยป Structure ยป Homebox Types which contains an invitation to add a Homebox Type.
also still present in 3.0.0-alpha2