Picture explaining where to find a useful constant in HelloAsso website

Module HelloAsso

2025-10-02T13:29:48Z

Hystepik: /* HelloAsso membership synchronization */

Module HelloAsso

2025-10-02T12:40:32Z

Hystepik: setup of api for membership

Module HelloAsso

2025-09-18T13:39:56Z

Hystepik:

Module Stancer DoliCloud

2024-09-02T09:14:47Z

Hystepik:

{{TemplateDocDev}}
{{TemplateDocUtil}}
=Informations=
{{TemplateModuleInfo
|modulename=Stencer
|editor=DoliCloud
|web={{URLNLTechno}}
|webbuy=
|status=development
|minversion=20
|note=
}}

=Features=
Add into Dolibarr a Stencer online payment page (credit/debit cards). This can be used to allow your customers to make ad-hoc payments or payments related to a specific Dolibarr object (invoice, order etc...).

=Prerequisites=
This module requires an instance of Dolibarr version 20 or +.

=Installation=
{{InstallModuleEn}}

=Setup=
{{ActivationModuleEn}}

==Setup of Stencer Api==
Generate the API keys required to make online payment with Stencer. They can be found on your Stencer account in the menu Developers

[[File:StencerApiKey.png|alt=|border]]

==Setup of Dolibarr module==
1) Create a bank account to record any payment done using Stencer.

2) Go on the setup page of Stencer module in Dolibarr and set the created bank account as the default bank account.

==Setup test mode==
To Setup the test mode, the only thing to do is fill "Stancer secret test API key" field in setup page

==Setup live mode==
1) Enable production mode in setup page

2) Fill "Stancer secret live API key" field in setup page

=Usage=
The only thing to do to use the module is to use any Dolibarr default link to make an online payment. All the links provided by Dolibarr to make online payment will support payment using Stencer.

Here is an example of customer payment page:*

[[File:PaymentPageStancer.png|border|1214x1214px]]

=Development and contributions=
The development of this Open Source application is not included inside the standard GIT repository of Dolibarr but inside a repository dedicated to modules not supported by the Dolibarr development team but supported by {{TemplateURLDoliCloud}} on GitHub:

*Repository: https://github.com/DoliCloud/DoliMods.git

Your Pull request for fixes or enhancements are welcome.

=Troubleshooting=
[[Category:Modules complémentaires]]
[[Category:DoliCloud]]

Module Stancer DoliCloud

2024-09-02T06:32:35Z

Hystepik: Hystepik moved page Module Stencer to Module Stancer DoliCloud

2024-03-21T09:38:25Z

Hystepik: /* Installation */

Module EMail Collector

2024-03-21T09:36:32Z

Hystepik: /* Create an email collector */

{{TemplateDocUser}}
{{TemplateModEN}}
{{BasculeDevUserEn|
name=EMailCollector|
num=50320|
devdoc=[[Module EMail Collector (developer)]]|
userdoc=This page}}

=Introduction=
This module permits to collect emails from a mailbox using the IMAP protocol and record event or data in your Dolbarr using information found into email.

=Installation=
{{NoInstallModuleEn}}

=Setup=
{{ActivationModuleEn}}

If available, it is recommended to enable the option "'''Use the PHP-IMAP library for IMAP instead of native PHP IMAP. This also allows the use of an OAuth2 connection for IMAP (module OAuth must also be activated).'''" so when creating an email collector, you will be able to choose between IMAP login with user/pass or with an OAuth2 token.

==Create an email collector==

Create as many email collectors you need.

'''Authentication mode'''

*If you choose "Password", you must set an IMAP login and password.
*If you choose "OAuth2", you must create an OAuth2 entry for IMAP and set it into field Oauth service.

To create your OAUth2 entry and choose the correct permission for this entry see documentation of [[Module OAuth]]

'''Source directory'''

*To collect received email, enter here "INBOX"
*To collect email sent, enter here "Sent"

'''Target directory'''
A good practice is to move the collected email into another folder to avoid to have them collected twice.
You must create the output target IMAP directory manually before running your email collector.

For example, with Gmail, to create a new IMAP directory:

*Sign in to your Gmail account.
*At the top right of the Gmail window, click Settings See all settings.
*Click Labels.
*Create Label and check the box "Show in IMAP"

'''Filters'''

Choose criteria to define which email is qualified for the collect.

'''Operations to do'''

Choose the action to do on collected emails.

=Usage=
Let the job scheduler being executed automatically and see your data being recorded into Dolibarr.

To avoid to wait the batch, you can force to execute the email collector manually from the Email collector record with the button "Run now". When making test, a good practice is to set the maximum number of email collected to a low value.

A test mode is available. This mode does not cause any modification of your mailbox (just reading) nor modification in Dolibarr. On the other hand, it allows you to see the different stages of selection, the filter and the processing that would be applied if we were not in test mode.

=Boundary Value Analysis=

===User Stories===
{| class="wikitable"
!Story
!KO / OK
!Errors / Problems
|-
|Collect received mails (created from scratch by someone)
|OK
!
|-
|Collect email you sent from the "Email sent", by your email client, to someone.
|OK
!
|-
|Send email from Dolibarr (example from the backoffice for a ticket) and don't collect it from the "Email sent" because it may be a double: When the email sent and saved from Dolibarr is also saved into the "Emails sent", we must not re-import it.
|OK
!
|-
|Collect and link email received to ticket already created after we have sent a reply email and the customer responds on email address.
|KO
|Problem : The email is not linked to ticket and another ticket is created
|}

===Filters===
{| class="wikitable"
|+
!Filters
!KO / OK
!Errors / Problems
|-
|From
|OK
!
|-
|To
|OK
!
|-
|Cc
|KO
|Search string not understood - Unknown search criterion: CC
|-
|Bcc
|KO
|Search string not understood - Unknown search criterion: BCC
|-
|ReplyTo
|OK
|Works every time even if the Reply to string isn't in the mail
|-
|Subject
|OK
!
|-
|Body
|OK
!
|-
!
!
!
|-
|Already read
|OK
!
|-
|Unread
|OK
!
|-
|Unanswered
|OK
!
|-
|Answered
|OK
!
|-
|Size (Smaller than)
|KO
|Search string not understood - Unknown search criterion: SMALLER
|-
|Size (Larger than)
|KO
|Search string not understood - Unknown search criterion: LARGER
|-
|Message from a conversation initiated by a first email sent from Dolibarr
|OK
!
|-
|Message from a conversation initiated by a first email NOT sent from Dolibarr
|OK
!
|-
|Message sent from Dolibarr
|OK
!
|-
|Message NOT sent from Dolibarr
|OK
|Message not processed but not an error
|-
!
!
!
|-
|Is not answer (initial email)
|OK
!
|-
|Is an answer of an initial email
|OK
!
|-
|}

Module EMail Collector

2024-03-21T09:33:38Z

Hystepik: /* User Stories */

{{TemplateDocUser}}
{{TemplateModEN}}
{{BasculeDevUserEn|
name=EMailCollector|
num=50320|
devdoc=[[Module EMail Collector (developer)]]|
userdoc=This page}}

=Introduction=
This module permits to collect emails from a mailbox using the IMAP protocol and record event or data in your Dolbarr using information found into email.

=Installation=
{{NoInstallModuleEn}}

=Setup=
{{ActivationModuleEn}}

If available, it is recommended to enable the option "'''Use the PHP-IMAP library for IMAP instead of native PHP IMAP. This also allows the use of an OAuth2 connection for IMAP (module OAuth must also be activated).'''" so when creating an email collector, you will be able to choose between IMAP login with user/pass or with an OAuth2 token.

==Create an email collector==

Create as many email collector you need.

'''Authentication mode'''

*If you choose "Password", you must set an IMAP login and password.
*If you choose "OAuth2", you must create an OAuth2 entry for IMAP and set it into field Oauth service.

To create your OAUth2 entry and choose the correct permission for this entry see documentation of [[Module OAuth]]

'''Source directory'''

*To collect received email, enter here "INBOX"
*To collect email sent, enter here "Sent"

'''Target directory'''
A good practice is to move the collected email into another folder to avoid to have them collected twice.
You must create the output target IMAP directory manually before running your email collector.

For example, with Gmail, to create a new IMAP directory:

*Sign in to your Gmail account.
*At the top right of the Gmail window, click Settings See all settings.
*Click Labels.
*Create Label and check the box "Show in IMAP"

'''Filters'''

Choose criteria to define which email is qualified for the collect.

'''Operations to do'''

Choose the action to do on collected emails.

=Usage=
Let the job scheduler being executed automatically and see your data being recorded into Dolibarr.

To avoid to wait the batch, you can force to execute the email collector manually from the Email collector record with the button "Run now". When making test, a good practice is to set the maximum number of email collected to a low value.

A test mode is available. This mode does not cause any modification of your mailbox (just reading) nor modification in Dolibarr. On the other hand, it allows you to see the different stages of selection, the filter and the processing that would be applied if we were not in test mode.

=Boundary Value Analysis=

===User Stories===
{| class="wikitable"
!Story
!KO / OK
!Errors / Problems
|-
|Collect received mails (created from scratch by someone)
|OK
!
|-
|Collect email you sent from the "Email sent", by your email client, to someone.
|OK
!
|-
|Send email from Dolibarr (example from the backoffice for a ticket) and don't collect it from the "Email sent" because it may be a double: When the email sent and saved from Dolibarr is also saved into the "Emails sent", we must not re-import it.
|OK
!
|-
|Collect and link email received to ticket already created after we have sent a reply email and the customer responds on email address.
|KO
|Problem : The email is not linked to ticket and another ticket is created
|}

===Filters===
{| class="wikitable"
|+
!Filters
!KO / OK
!Errors / Problems
|-
|From
|OK
!
|-
|To
|OK
!
|-
|Cc
|KO
|Search string not understood - Unknown search criterion: CC
|-
|Bcc
|KO
|Search string not understood - Unknown search criterion: BCC
|-
|ReplyTo
|OK
|Works every time even if the Reply to string isn't in the mail
|-
|Subject
|OK
!
|-
|Body
|OK
!
|-
!
!
!
|-
|Already read
|OK
!
|-
|Unread
|OK
!
|-
|Unanswered
|OK
!
|-
|Answered
|OK
!
|-
|Size (Smaller than)
|KO
|Search string not understood - Unknown search criterion: SMALLER
|-
|Size (Larger than)
|KO
|Search string not understood - Unknown search criterion: LARGER
|-
|Message from a conversation initiated by a first email sent from Dolibarr
|OK
!
|-
|Message from a conversation initiated by a first email NOT sent from Dolibarr
|OK
!
|-
|Message sent from Dolibarr
|OK
!
|-
|Message NOT sent from Dolibarr
|OK
|Message not processed but not an error
|-
!
!
!
|-
|Is not answer (initial email)
|OK
!
|-
|Is an answer of an initial email
|OK
!
|-
|}

Module EMail Collector

2024-03-21T09:31:20Z

Hystepik: /* Boundary Value Analysis */

{{TemplateDocUser}}
{{TemplateModEN}}
{{BasculeDevUserEn|
name=EMailCollector|
num=50320|
devdoc=[[Module EMail Collector (developer)]]|
userdoc=This page}}

=Introduction=
This module permits to collect emails from a mailbox using the IMAP protocol and record event or data in your Dolbarr using information found into email.

=Installation=
{{NoInstallModuleEn}}

=Setup=
{{ActivationModuleEn}}

If available, it is recommended to enable the option "'''Use the PHP-IMAP library for IMAP instead of native PHP IMAP. This also allows the use of an OAuth2 connection for IMAP (module OAuth must also be activated).'''" so when creating an email collector, you will be able to choose between IMAP login with user/pass or with an OAuth2 token.

==Create an email collector==

Create as many email collector you need.

'''Authentication mode'''

*If you choose "Password", you must set an IMAP login and password.
*If you choose "OAuth2", you must create an OAuth2 entry for IMAP and set it into field Oauth service.

To create your OAUth2 entry and choose the correct permission for this entry see documentation of [[Module OAuth]]

'''Source directory'''

*To collect received email, enter here "INBOX"
*To collect email sent, enter here "Sent"

'''Target directory'''
A good practice is to move the collected email into another folder to avoid to have them collected twice.
You must create the output target IMAP directory manually before running your email collector.

For example, with Gmail, to create a new IMAP directory:

*Sign in to your Gmail account.
*At the top right of the Gmail window, click Settings See all settings.
*Click Labels.
*Create Label and check the box "Show in IMAP"

'''Filters'''

Choose criteria to define which email is qualified for the collect.

'''Operations to do'''

Choose the action to do on collected emails.

=Usage=
Let the job scheduler being executed automatically and see your data being recorded into Dolibarr.

To avoid to wait the batch, you can force to execute the email collector manually from the Email collector record with the button "Run now". When making test, a good practice is to set the maximum number of email collected to a low value.

A test mode is available. This mode does not cause any modification of your mailbox (just reading) nor modification in Dolibarr. On the other hand, it allows you to see the different stages of selection, the filter and the processing that would be applied if we were not in test mode.

=Boundary Value Analysis=

===User Stories===
{| class="wikitable"
!Story
!KO / OK
!Errors / Problems
|-
|Collect received mails (created from scratch by someone)
|OK
!
|-
|Collect email you sent from the "Email sent", by your email client, to someone.
|OK
!
|-
|Send email from Dolibarr (example from the backoffice for a ticket) and don't collect it from the "Email sent" because it may be a double: When the email sent and saved from Dolibarr is also saved into the "Emails sent", we must not re-import it.
|OK
|
|-
|Collect and link email received to ticket already created after we have sent a reply email and the customer responds on email address.
|KO
|Problem : The email is not linked to ticket and another ticket is created
|}

===Filters===
{| class="wikitable"
|+
!Filters
!KO / OK
!Errors / Problems
|-
|From
|OK
!
|-
|To
|OK
!
|-
|Cc
|KO
|Search string not understood - Unknown search criterion: CC
|-
|Bcc
|KO
|Search string not understood - Unknown search criterion: BCC
|-
|ReplyTo
|OK
|Works every time even if the Reply to string isn't in the mail
|-
|Subject
|OK
!
|-
|Body
|OK
!
|-
!
!
!
|-
|Already read
|OK
!
|-
|Unread
|OK
!
|-
|Unanswered
|OK
!
|-
|Answered
|OK
!
|-
|Size (Smaller than)
|KO
|Search string not understood - Unknown search criterion: SMALLER
|-
|Size (Larger than)
|KO
|Search string not understood - Unknown search criterion: LARGER
|-
|Message from a conversation initiated by a first email sent from Dolibarr
|OK
!
|-
|Message from a conversation initiated by a first email NOT sent from Dolibarr
|OK
!
|-
|Message sent from Dolibarr
|OK
!
|-
|Message NOT sent from Dolibarr
|OK
|Message not processed but not an error
|-
!
!
!
|-
|Is not answer (initial email)
|OK
!
|-
|Is an answer of an initial email
|OK
!
|-
|}

Module HelloAsso

2024-03-20T10:30:44Z

Hystepik: /* Usage */

Module HelloAsso

2024-03-20T10:29:57Z

Hystepik: /* Usage */

Module HelloAsso

2024-03-20T10:29:43Z

Hystepik: /* Usage */

File:Exemple payment page Helloasso.png

2024-03-20T10:23:41Z

Module HelloAsso

2024-03-19T12:56:40Z

Hystepik:

Module HelloAsso

2024-03-19T09:46:20Z

Hystepik: /* Setup */

{{TemplateDocDev}}
{{TemplateDocUtil}}
=Informations=
{{TemplateModuleInfo
|modulename=HelloAsso
|editor=DoliCloud
|web={{URLNLTechno}}
|webbuy=
|status=development
|minversion=20
|note=
}}

=Features=
Add into Dolibarr, a HelloAsso online payment page (credit/debit cards). This can be used to allow your customers to make ad-hoc payments or payments related to a specific Dolibarr object (invoice, order etc...)

=Prerequisites=
This module requires an instance of Dolibarr version 20 (develop) to be functional.

=Installation=
{{InstallModuleEn}}

=Setup=
{{ActivationModuleEn}}

== Setup for sandbox mode ==

== Setup for live mode ==

=Usage=

=Development and contributions=
The development of this Open Source application is not included inside the standard GIT repository of Dolibarr but inside a repository dedicated to modules not supported by the Dolibarr development team but supported by {{TemplateURLDoliCloud}} on GitHub:

*Repository: https://github.com/DoliCloud/DoliMods.git

Your Pull request for fixes or enhancements are welcome.

=Troubleshooting=

Module HelloAsso

2024-03-19T09:45:34Z

Hystepik: /* Setup */

{{TemplateDocDev}}
{{TemplateDocUtil}}
=Informations=
{{TemplateModuleInfo
|modulename=HelloAsso
|editor=DoliCloud
|web={{URLNLTechno}}
|webbuy=
|status=development
|minversion=20
|note=
}}

=Features=
Add into Dolibarr, a HelloAsso online payment page (credit/debit cards). This can be used to allow your customers to make ad-hoc payments or payments related to a specific Dolibarr object (invoice, order etc...)

=Prerequisites=
This module requires an instance of Dolibarr version 20 (develop) to be functional.

=Installation=
{{InstallModuleEn}}

=Setup=
{{ActivationModuleEn}}

===Setup for sandbox mode===

===Setup for live mode===

=Usage=

=Development and contributions=
The development of this Open Source application is not included inside the standard GIT repository of Dolibarr but inside a repository dedicated to modules not supported by the Dolibarr development team but supported by {{TemplateURLDoliCloud}} on GitHub:

*Repository: https://github.com/DoliCloud/DoliMods.git

Your Pull request for fixes or enhancements are welcome.

=Troubleshooting=