🇮🇹Italy @xlyz

From what I understand the current implementation add the domain to the destination uri so that the user after the POST get redirected to the domain is currently using.

For instance if I have a site in english and italian, each with its own domain, and I'm using the english one, if I try to delete the italian translation of a node the delete link is built with the italian domain, and then destination=english_domain/current_path is added to bring back the user to the current page with the current language. Otherwise he'll switch to the language of the page he has deleted.

Current implementaion seems to create problem:
1. delete file does not works
2. if i try to delete a node I currently get this error:
> Redirects to external URLs are not allowed by default, use \Drupal\Core\Routing\TrustedRedirectResponse for it.
(on Drupal 10.5)

The proposed patch is not perfect (to user will switch to the language of the translation that need to edit / delete) but it's still better that the current implementation.

P.S. is a backport to 10.x planned?

for reference:

Beta releases

Beta releases are usually only created once:

• All critical data loss and security bugs are resolved
• The APIs are frozen enough so that contributed module and theme authors can start upgrading their projects.
• Most of the problems with the upgrade path are fixed and it's possible to successfully upgrade a copy of the Drupal.org database to the new Drupal version.

from Drupal > Getting started > Understanding Drupal > Understanding Drupal version numbers: What are alpha and beta releases, and release candidates? →

I could live with a beta :-)

I second #6 💬 Is 3 alpha ready for production and what is the roadmap for a production release Active .

Currently Keycloak OpenID Connect has dropped 8.x, and current release (2.2.1) requires v3.x, that is still alpha. In any case we need to pick a non supported solution. Not a good feeling :-).

xlyz → created an issue.

xlyz → created an issue.

xlyz → created an issue.

Hi.

I was not aware of commerce_sync → , so I implemented some plugins on my own. There are some differences with commerce_sync:
- I have not implemented the sync of promotions
- I do have implemented the handling of attributes
- Stores are not imported / updated automatically with products, but just referenced

I uploaded my plugins on drupalcode (commit 656d3106) if anyone would like to use them.

xlyz → made their first commit to this issue’s fork.

I'm pretty sure that this is not what is supposed to be. Currently there is no access to product attributes page in the dashboard:

Give me a couple of minutes to submit a merge request that moves product attributes to the Products section

xlyz → created an issue.

never mind, it was a typo:

$config['openid_connect.client.kc']['settings']['client_secret']='my secret here';

client, not clients!

xlyz → created an issue.

Hi

I can see the setting but it does not work. Has this feature been implemented?

xlyz → created an issue.