For interested people about permissions per order type per store, I'm starting a new module to provide more granular permissions. I've been thinking about releasing it as contributed project/module, but I'll give a chance to get some love, since it could require some minor improvements and also, new ideas are welcomed:
Hello @aporie
Thanks for your reply...
at the end, I discovered that, when using this module into a project where it is also using Commerce Stock → , it is needed to go to /admin/commerce/config/stock/settings and set the "Deposit" product variation type as "Always in stock". Otherwise, it will always redirect to the /cart page, which it was in my case.
Again, thanks for your help...
First attempt
Created a small patch to allow adding defaults to the commerce_store entity type.
Nothing changed, but just making patch to apply in latest release.
Updated patch. A minor improvement to make theming even better.
Forgot to include change by @van.dordafog. Updated.
I think adding title INSIDE certain layouts could break the whole layout itself. For example, for modules providing CSS styles using "display: flex" or something close, then the title wrapper could inherit such CSS rules.
IMHO, better to just wrap all into an extra div to make theming easier. Patch on the way...
Just for Project Update Bot. Patch was commited.
Looks like patch wasn't working with latest stable, but it's ok. Just local issue.
Nice feature. IMHO, the contrib module ( https://www.drupal.org/project/paragraphs_summary → ) could be a sub-module into Paragraphs project. very useful.
If you need tihis patch to work with #3362561, here an attempt:
For any reason, same patch from dev didn't apply in release. Added here, just in case.
First attempt. Please review/test attached patch.
LATEST NEWS:
Module is now complete. The handlers system works as expected; also each handler is able to have its own set of conditions. Both (handlers and conditions) are pluggable, so you can to define your own ones.
Also, the D9 and D10 compatibility has been fixed.
A new module version will be released very soon...
At this moment, the sub-module auctioneer_common_handlers provides 2 options (both with Tokens support):
- Sending an email.
- Sending a message to a Telegram conversation/channel/group.
IMHO, it's enough for now. Anyway, we can to add more "default ones" later. It's just a matter of new feature requests :)
@andypost
Thanks for your comment :)
Well, at beginning, I believed the same. But after doing some tests, I noticed it was not as "flexible" as expected (for example, the fields and the token replacements). It could require some code to "transform" or make it compatible with all desired features (and the incoming ones). So, at the end, dealing with a custom one made it easier/more flexible to manage...
LATEST NEWS:
This new branch is "usable", said in a way... The latest needed relevant features were added, and there is at least one handler (email) to be added on provided events. Planning to add at least one more handler in next days, so basically there won't be big changes.
Any feedback/improvements are welcome!
UPDATE:
This is being worked. We're almost done. But with a different approach: At the end, we've decided to use a pluggable system to allow the creation of custom handlers for both: auction_type and bid_type. So, basically we've based most of the "workflow" as Webform module does, 'cause it looks simple, effective and it allows to do more than just sending an email.
As mentioned above, most of the work is done. Still needed a bit of cleaning-up before creating a new module release. If you're interested about checking the progress of this, take a look to the 2.0.x branch, at https://git.drupalcode.org/project/auctioneer/-/tree/2.0.x. Be warned: Do not use previous branch for production environments yet... We're sending several changes that could affect your website. Use it for testing, reviews or if possible, to provide any feedback about it.
Cheers.
Forgot to remove a line.
There is a failing test about the same langcode for child entities. IMHO, it's not "valid", because this patch is in the way to allow having asymmetric content. I've removed some lines. Feel free to improve/blame :)