🇬🇷Greece @giorgosk

giorgosk → created an issue.

Same problem, I have tried the patch and it seems to resolve it
set to RTBC

I have had other team member test this
I believe it is RTBC

Tested latest patch from #28 and steps from #3 still work on a drupal 10.x installation
perhaps we can get it committed ?

For people still wondering about Admin Toolbar Links Access Filter it is no longer needed based on the maintainer's Proposed resolution here https://www.drupal.org/project/admin_toolbar/issues/3485771 📌 Admin Toolbar Links Access Filter Deprecation Warning Active

I have tested #11 for an existing installation with previous patch #12
the scripts seems to load and work properly

Applied the latest patch from #7 and tested on site already using module
here is the steps I have tested
- structure > block layout
- place a block in any region/ or add new block
- configure block popup should allow yout edit the machine name. Save
- create templates/block/block-[MACHINENAME].html.twig
- make sure that this template is used (might need clear cache)

Tested on an existing project similar to steps by @myst1c and all works as expected

Getting the same problem with 3.0.0-rc20 released 26 July 2024 - also tried the last patch #25 (which probably was not created by for this version). Problem is using the inline form to add product variations and only one appears. Had to revert back to 8.x-1.0-rc17 version with the patch from #17 which worked.

Here is a patch that fixes this

GiorgosK → created an issue.

This happens if entity_usage module is enabled
after uninstalling both and installing entity_usage_light alone than settings form works as expected

GiorgosK → created an issue.

I tried it on a new installation and on initial setup I get the WSOD

Type	php
Date	Sunday, February 11, 2024 - 06:35
User	admin
Location	http://projectname.docksal.site/admin/lingotek/setup/community
Referrer	http://projectname.docksal.site/admin/lingotek/settings/accessToken
Message	Drupal\lingotek\Exception\LingotekApiException: Failed to get filters: Client error: `GET https://myaccount.lingotek.com/api/filter?limit=1000` resulted in a `404 Not Found` response: {"messages":["No view access."]} in Drupal\lingotek\Remote\LingotekApi->getFilters() (line 540 of /var/www/web/modules/contrib/lingotek/src/Remote/LingotekApi.php).
Severity	Error
Hostname	172.20.0.2

GiorgosK → created an issue.

I had what it appeared as the problem described above and was able to resolve it without any patches

it turned out that the menu item needed to be translatable

/admin/config/regional/content-language > Custom menu link

Adding a small check for cart being not null

Updated patch from 47
- drupal 10 compatibilities from https://www.drupal.org/node/3340566 →
- other drupal 10 fixes
- cart_view only fires on /cart page (as suggested above)
- applies to "drupal/commerce_google_tag_manager": "2.x-dev@dev",

can consider this patch D10 and GA4 compatible

@agoradesign I think the google_tag implementation is missing a few triggers with the most important one "purchase" missing
https://git.drupalcode.org/project/google_tag/-/tree/2.0.x/src/EventSubs...

For anyone still looking temp solution is

composer require drupal/physical:1.2

Add fix for problem with deprecated drupal_get_path

This did not work after all
ended up with this after upgrading to drupal 10.1

$ fin composer update
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - twig/twig[v2.0.0, ..., v2.12.5] require php ^7.0 -> your php version (8.1.21) does not satisfy that requirement.
    - Root composer.json requires drupal/core-recommended 10.1.6 -> satisfiable by drupal/core-recommended[10.1.6].
    - twig/extensions[v1.5.4, ..., 1.x-dev] require twig/twig ^1.27|^2.0 -> satisfiable by twig/twig[v1.27.0, ..., 1.x-dev, v2.0.0, ..., 2.x-dev].
    - You can only install one version of a package, so only one of these can be installed: twig/twig[v1.16.0, ..., 1.x-dev, v2.0.0, ..., 2.x-dev, v3.0.0-BETA1, ..., 3.x-dev].
    - drupal/core-recommended 10.1.6 requires twig/twig ~v3.6.0 -> satisfiable by twig/twig[v3.6.0, v3.6.1].
    - Root composer.json requires twig/extensions ^1.5.4 -> satisfiable by twig/extensions[v1.5.4, 1.x-dev].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Was able to composer require
fin composer require 'drupal/twig_extensions:2.x-dev@dev'
and than add the latest merge request for patching
uploading here for other people to link to (safer than the original patch URL)

NOTE: the patch has nothing new and applies cleanly on latest dev

Upgrading to v 2.0.x broke site functionality so decided to stick with v 1 for now
current patch did not apply cleanly here is an updated patch
removes the problems and things that are decoration changes (non essentials)

GiorgosK → created an issue.

Seems that this might be obsolete after the latest releases of linkit 6.0.x and 6.1.x
https://www.drupal.org/project/linkit/issues/3354873 🐛 Direct URL to media file entity does not work because relative URL does not pass URL path validation Fixed

Checkout dev version for now and I will soon prepare a proper release

tested it, seems to work, +1 to get it merged

GiorgosK → created an issue.

Actually there is a setting for that
/admin/commerce/config/checkout-flows
and edit used checkout flow and than edit the payment process to "Transaction mode: Authorize and capture"

GiorgosK → created an issue.

I think this is similar to https://www.drupal.org/project/administerusersbyrole/issues/3175317 →

#13 worked for inline_enitty_form 8.x-1.0-rc15

problem was content type with entity reference to a product with variations could only hold 1 variation when saving the content
any other variations was still in the database but the reference was lost from the product level

So technically this should be works as designed

In similar fashion we have successfully added a poll (views block) with this module and it displays correctly but it has lost its ability to vote using ajax. Instead clicking on the vote button reloads the whole page.

Noticed that the submit button and the form action has lost some of the ajax related attributes. Not trying to hijack the issue queue just think the problem and solution might be very similar or can be generalized.

Seems validation is still needed in latest version and it can result in problems

One can import a redirect from /page to /page which can result in infinite loop
Adding this link manually does understand the problem and does not allow it but when importing the validation does not happen

GiorgosK → created an issue.

Workaround: If one updates all view fields and changes in the style section

Customize field and label wrapper HTML
Customize label HTML
Customize field HTML

and sets the Element to none, no HTML is passed to select2 and there is no need for this patch.