To whom it may concern, dbout sponsorship, I read this on project page
"Development proudly sponsored by German Drupal Friends & Companies:
webks: websolutions kept simple (https://www.webks.de)
and
DROWL: Drupalbasierte Lösungen aus Ostwestfalen-Lippe (OWL), Germany (https://www.drowl.de)
Supporting organizations:
DROWL.de
proudly developed the original Drupal 7 module for the community!"
As things are today, Should we maybe update this?
If conversation gets complicated, I 'll open a separate issue of course
Thanks Anybody
"Please stick to Drupal best practices and coding standards."
Sure thing! Your support will make the difference
Best!
following
afagioli → created an issue.
I'm already using the project and I want it to be well-maintained.
Sorry to see this module is still so far back.
Can we somehow move forward?
refreshing...
Doc link at #3 gives "404 - Not found"
Thanks for accepting
afagioli → created an issue.
Contacted today maintaner nuez
afagioli → created an issue.
afagioli → created an issue.
Successfully tested as per https://www.drupal.org/node/3126948 →
I can't clearly get the meaning of this document.
A definitions paragraph as "This page aims to...." would help.
This task is huge
#19, I use it on many instances, pretty same twin instances, limited use cases.
Installing is not enough to get experienced I'm afraid.
@Maintainers, your efforts on docs will make the difference
MAtter of fact, is not that easy to understand how this module works.
I hope more people will contribute to the Docs. Big value for both users and developers
No today, so you are right to get this buried
Doc updated > https://www.drupal.org/node/3522083 →
Cool!
thanks
Do we have the use case "Ability to add new emails" today?
Can you please describe the flow to resend an invoice?
Thanks, @jsaclsick
Hi @jsaclsick,
I have a question for those with experience regarding the current implementation of the commerce_invoice use case.
As you may have noticed from recent issues, I’ve been gathering contributions for the newly created documentation of this module.
If you believe the version in the form needs updating, please feel free to adjust it.
Once this question has been addressed, the issue can be closed.
For now, I’m switching it back to "Needs Work", with the required action being "Define use case."
Thanks in advance for your input!
Question to experienced:
How would you describe this use case?
Answer should be added to " https://www.drupal.org/node/3522083 → > Send via mail "
This reopening is only related to the documentation side.
Question to experienced:
How would you describe this use case?
Answer should be added to " https://www.drupal.org/node/3522083 → > Send via mail "
Thanks a lot
Can we move this forward? Seems to be handy to have an easy to fix
final design should be then exposed here https://www.drupal.org/node/3522060 →
reformulated #3 in https://www.drupal.org/node/3522078 →
Double check is welcome
Nice confirm. Thanks
afagioli → created an issue.
At first sight, this pages seems to be in need of a refresh (labeling, reference to old component, etc)
Honoring page title, I'd suggest a short reference to the actual "module install".
IE: the module is to be installed via composer....
afagioli → created an issue.
"Having different checkboxes wouldn't really help as it could be the email should still be sent on both transitions, and some invoices could be sent on confirm, others on paid?"
Having 2 checkboxes would help when I have 3 differents projects:
project A: owner needs to send a mail when a new order is confirmed
project B: owner needs to send a mail when a new order is confirmed and later on once a payment is received
project C: owner needs to send a mail when a order is paid.
We need flexibility. Maybe even flexibility more that #8 cases.
afagioli → created an issue.
With such a promt action from your side, this issue can be happily closed
Thanks a lot for your efforts!
#18 it's done
https://www.drupal.org/node/3522060 →
A guide for the Commerce Invoice module is now available at:
https://www.drupal.org/node/3522060/edit →
The guide contains:
- Usage instructions for end users
- Design documentation and implementation details for developers
Contributors with a deeper knowledge of the module are welcome to help improve the documentation.
afagioli → created an issue.