Account created on 29 July 2023, over 1 year ago
#

Merge Requests

More

Recent comments

@christianadamski
Thank you for the simplification. Implemented the new changes.

Hello @cgireeshs please provide the details about the steps to reproduce this issue.

Hello @chunhuaicheng

It seems to be issue with postgresql database syntax error.
It works fine with MariaDB & MySQL.

Hello @jnettik @pixelwhip
I have fixed some issue mentioned in the PR.

Hello @finnsky it is the same code patch added until issue was not merged to be used.

Hello @pbabin,
In one of our project we faced similar problem.
The solution was implemented using custom module to bind another extra field which stores the crop positions data.
Once the data is synced we wrote code to use those field value and apply crop to image.

Hello @chaitanyadessai,
Thank you for the patch.

We should use the Drupal RouteObjectInterface as per Drupal 10 instead of \Symfony\Cmf\Component\Routing\RouteObjectInterface.
I have updated the code.

Hello @divya.sejekan please use the latest patch added I have tested it in plain drupal setup.
It is working as needed.

Yes it seems webauthn 2.x is using webauthn-lib library 4.x but no relevant code is added in that module version.

Hello @gábor-hojtsy,
I manage to update the pipeline to include Drupal 11 for composer stage.
While we still need to see about D11 test cases.

Closing this issue since no relevant code changes needed.

The issue is already fixed we can close this one.

Hello @rajab-natshah,
The patch you have added does not belong to this module source code.
I am not able to apply this patch!

Hello,
As per understanding from version 1.0.6 to 1.0.7
We can see that now services have new parameters introduced.

In version 1.0.6

  access_policy.validator:
    class: Drupal\access_policy\AccessPolicyValidator
    arguments: ['@entity_type.manager', '@access_policy.content_policy_manager', '@plugin.manager.access_policy.access_rule']

In version 1.0.7 we have additional parameter

  access_policy.validator:
    class: Drupal\access_policy\AccessPolicyValidator
    arguments: ['@entity_type.manager', '@access_policy.content_policy_manager', '@plugin.manager.access_policy.access_rule', '@plugin.manager.access_policy_operation']

My question is to @gilbertdelyon are you using this service access_policy.validator somewhere in your custom module?

Also @partdigital we still need to fix the Test cases where service is using only 3 parameters for testing.

Also there is no `cart` column in database table also.
I have verified it

See below:

MySQL [drupal]> DESC commerce_order;
+-------------------------------------+---------------+------+-----+---------+----------------+
| Field                               | Type          | Null | Key | Default | Extra          |
+-------------------------------------+---------------+------+-----+---------+----------------+
| order_id                            | int unsigned  | NO   | PRI | NULL    | auto_increment |
| type                                | varchar(32)   | NO   | MUL | NULL    |                |
| uuid                                | varchar(128)  | NO   | UNI | NULL    |                |
| order_number                        | varchar(255)  | YES  | MUL | NULL    |                |
| version                             | int unsigned  | YES  |     | NULL    |                |
| store_id                            | int unsigned  | YES  | MUL | NULL    |                |
| uid                                 | int unsigned  | YES  | MUL | NULL    |                |
| mail                                | varchar(254)  | YES  |     | NULL    |                |
| ip_address                          | varchar(128)  | YES  |     | NULL    |                |
| billing_profile__target_id          | int unsigned  | YES  | MUL | NULL    |                |
| billing_profile__target_revision_id | int unsigned  | YES  | MUL | NULL    |                |
| total_price__number                 | decimal(19,6) | YES  |     | NULL    |                |
| total_price__currency_code          | varchar(3)    | YES  |     | NULL    |                |
| total_paid__number                  | decimal(19,6) | YES  |     | NULL    |                |
| total_paid__currency_code           | varchar(3)    | YES  |     | NULL    |                |
| state                               | varchar(255)  | YES  | MUL | NULL    |                |
| data                                | longblob      | YES  |     | NULL    |                |
| locked                              | tinyint       | YES  |     | NULL    |                |
| created                             | int           | YES  |     | NULL    |                |
| changed                             | int           | YES  |     | NULL    |                |
| placed                              | int           | YES  |     | NULL    |                |
| completed                           | int           | YES  |     | NULL    |                |
+-------------------------------------+---------------+------+-----+---------+----------------+
22 rows in set (0.006 sec)

@jsacksick
Yes I am using the latest version.
"drupal/commerce": "^2.38"

I had similar issue post installation on existing site.
While the patch is not able to solve the problem!

I can see Proposed resolution is to
Update mathieuviossat/arraytotexttable package.
So the PR in this issue can fixed it.

Updates:

Issues seems to be fixed

As per latest test with below:
Drupal 10.2.1
PHP 8.2.9 (cli) (built: Aug 17 2023 22:52:44) (NTS)

There is no conflicts as such since Drupal core already manage to fix the issue with conflicting PHP 8.2 packages.
Platform requirements changes
Drupal now supports PHP 8.3 and recommends at least PHP 8.2.
https://www.drupal.org/project/drupal/releases/10.2.0

Hello @gabor

The issue we faced in our drupal project was able to fixed by updating the dependency by specifying the exact version "mathieuviossat/arraytotexttable": "~1.0.10" so composer can skip the search of other package and no conflict was occur after this.

While it could be major issue with laminas/laminas-text


 drupal/upgrade_status[4.0.0-alpha1, ..., 4.x-dev] require mathieuviossat/arraytotexttable ~1.0.0 -> satisfiable by mathieuviossat/arraytotexttable[v1.0.0, ..., v1.0.10].

    - mathieuviossat/arraytotexttable[v1.0.0, ..., v1.0.4] require zendframework/zend-text ~2.5 -> satisfiable by laminas/laminas-text[2.7.0, ..., 2.11.x-dev], zendframework/zend-text[2.5.0, ..., 2.8.x-dev].

Production build 0.71.5 2024