@pbabin I tried that patch as well and it didn't fix the issue for me. Did you have to rebuild the facet or do anything else beyond apply the patch? We did a drush cr
I have the exact same error as you on Drupal 10.3 and facets 2.0.7. Which patch worked for you? So far none of the ones I've tried have worked. Did you have to run cron or rebuilt the facets view or do anything else?
I have the same issue as well. Running MariaDB 10.6.16, Drupal 10.2.7, and Commerce 2.39. tx_isolation is reporting READ-COMMITTED, I've set it in the settings.php file and the Status report page still reports REPEATABLE-READ as being set.
I am still able to reproduce using @aaron.ferris' approach. The issue disappears until I re-enable admin_toolbar_search, then it comes back. I think this is why disabling and reenabling admin_toolbar works, because it disables admin_toolbar_search as well.
Seems to be related to admin_toolbar_search/admin_toolbar_tools.
Running Drupal 10.2.7 and Devel 5.0 w/ Admin Toolbar 3.4.2.
It may be possible, but it could require some redesign on the TakePOS and Dolibarr side. Once we go live with the Beta and perform a few bugfixes, we will look at implementing feature additions.
Will get to this as soon as we can, thanks everyone!
Thanks AmyJune!
I can confirm this is required. I would have confirmed him but it seems like I do not have the Community role.
The issue 3116449 is giving me an access denied error. What is the current status of the feature and is there a patch?
Would also be interested in this as well
I figured it out. Thanks!
montag64 → created an issue.
It might be worth mentioning that the JSON parser expects the values to process to be inside an array. For cases like this:
{
"id": "347139",
"asset_id": "1525",
"floor_id": "7256",
"floor_plan_id": "22925",
"map_id": "347139",
"unit_number": "126",
"area": 731,
"created_at": "2018-05-02T19:22:54+00:00",
"updated_at": "2018-05-02T19:22:54+00:00",
"view_image_url": null
}'item_selector: false' can be set in the migration, and this resolves the issue. It took me way too long than I would like to admit to try to understand why I was always getting null fields when calling an API.