Problem/Motivation

Release Drupal 9 stable version with fixes in rules.info.yml file:
core_version_requirement: ^8.8.2 || ^9

Comments

khaldoon_masud created an issue. See original summary.

tr’s picture

Category: Bug report » Task
Priority: Critical » Normal
Status: Active » Closed (duplicate)

Or ... you could search the issue queue and read #3162076: [meta] D9 compatibility, then help to finish the blocking issues listed there.

khaldoon_masud’s picture

When I uninstall rules, I get below error on entity view event, any idea what that is?

TypeError: Argument 1 passed to Drupal\Core\Plugin\Context\Context::__construct() must implement interface Drupal\Core\Plugin\Context\ContextDefinitionInterface, instance of __PHP_Incomplete_Class given, called in /app/web/core/lib/Drupal/Core/Plugin/ContextAwarePluginTrait.php on line 88 in Drupal\Core\Plugin\Context\Context->__construct() (line 50 of core/lib/Drupal/Core/Plugin/Context/Context.php).

khaldoon_masud’s picture

I was getting above error cause of user login block, after uninstalling rules module. It's strange! I disabled the user login block and problem is solved. For now, I'll try not to use rules module, until we have a stable Drupal 9 version.

rodmarasi’s picture

may i know whats the purpose of this issue

tr’s picture

Rules 8.x-3.x-dev works on Drupal 9, as stated on the project page, and it has worked on D9 since D9 was released; it is better than and has many improvements and bug fixes over -alpha6. Use it.

You need to use your critical thinking skills. "Stable" doesn't have any meaning. What's in a name? If I released the current -dev TODAY as a 8.x-3.0 full release, would you consider that "stable", even though it is in no way different from the current -dev? Or perhaps I could make one or two new "stable" releases every week (or even every day) - would you consider those "stable"? That's what many other modules do, so if you fall for that deception then there's nothing I can say to make you understand that a release "by any other name" would be as suitable as the current -dev.

Regardless, I spelled out in detail the criteria I'm using for a next fixed-point release in the issue I linked to in #2.

aseabrook’s picture

"Stable" doesn't have any meaning. What's in a name?

I don't know...maybe it instills confidence in users or organizations that if they install the module they're not going to get burned later on down the line when, after being perpetually stuck in alpha (*cough* rules-8.x *cough*), it just gets abandoned in the end?

I get it, beggars can't be choosers and if everyone is demanding for a stable ("greenlit", whatever you want to call it) release then they need to pony up and help out through code contributions...but, saying that "stable" doesn't have any meaning is misguided thinking.