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 :-).
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.
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
never mind, it was a typo:
$config['openid_connect.client.kc']['settings']['client_secret']='my secret here';
client, not clients!
Hi
I can see the setting but it does not work. Has this feature been implemented?