🇫🇷France @quimic

Paris
Account created on 26 December 2011, almost 13 years ago
#

Recent comments

🇫🇷France quimic Paris

I have the same issue. Upgrade status report Radix itself (not the sub-theme) as being incompatible.

🇫🇷France quimic Paris

I confirm the all day events issue but I cannot seem to be able to apply the provided patch. I get a "corrupt patch at line 61" error.

🇫🇷France quimic Paris

The #2 patch can no longer be applied on 2.0.6 and up.

🇫🇷France quimic Paris

It looks like the Commerce tokens give me inconsistent values, so I need to investigate further to understand what is happening here.

🇫🇷France quimic Paris

Okay, so now there is no error any more.

BUT, the condition of the sequence flow should have matched and it did not.

More specifically:
I payed an order that contains a specific product variation type
I check for that variation type in my model, and display (or log) a message if it matches

I did not get the message. "Negating" the condition in the sequence flow does give me the message.
So it means that the values comparison fails.

🇫🇷France quimic Paris

Thank you Jurgen.
I now get an "opposite" error, from ECA Commerce. It complains about receiving an array instead of a string.
TypeError: explode(): Argument #2 ($string) must be of type string, array given in explode() (line 71 of [...]/modules/contrib/eca_commerce/src/Plugin/ECA/Condition/Commerce.php)

🇫🇷France quimic Paris

Thank you Jurgen. I would not be able to assess if this is the right fix.

I can confirm that after applying the patch, the form validates and I can now save the model I described (display a message if a paid order contains a specific product variation type).

But when I trigger the model (by paying an order), I get an error from the commerce module:
TypeError: in_array(): Argument #2 ($haystack) must be of type array, string given in in_array() (line 36 of [...]/modules/contrib/commerce/modules/product/src/Plugin/Commerce/Condition/OrderVariationType.php)

🇫🇷France quimic Paris

Wow, thank you for the instant fix!

🇫🇷France quimic Paris

I decided to see if I would get a similar error using the Classic Modeler, and indeed I do, but I get a little more details on what might cause it.
When I use the "Order Paid" event and try to add the "Commerce: Order contains product variation types (ECA Commerce)" condiftion, I get a white page with the "The website encountered an unexpected error. Please try again later." message.
Looking in the log, I see "TypeError: Cannot access offset of type string on string in Drupal\eca_commerce\Plugin\ECA\Condition\Commerce->filterFormFields() (line 145 of [...]/modules/contrib/eca_commerce/src/Plugin/ECA/Condition/Commerce.php)."

Using the "Commerce: Order contains product types (ECA Commerce)" brings the exact same error.

Hope this helps.

🇫🇷France quimic Paris

@nicxvan Whatever value I enter in the entity field, I get the same error message when saving. No entry in the log.

🇫🇷France quimic Paris

I can confirm the issue is still present, with the same error messages.

🇫🇷France quimic Paris

I get the debug messages (Drupal 9.5.9) but I cannot seem to apply the #5 patch. It gets rejected.

🇫🇷France quimic Paris

I confirm the exact same problem. All interaction with FTP (including backups) generate that same error.

Production build 0.71.5 2024