ProPeace/de.forumzfd.twinglecampaign
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Documentation to enable scheduled job in nonproductive sites

Browse source
This commit is contained in:
Daniel Scholten 2022-07-21 10:42:37 +02:00
parent cb4c11feee
commit 6a50ea2c16
No known key found for this signature in database
GPG key ID: CB579517CB2FF651
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -72,6 +72,8 @@ decrease this interval by changing the configuration of the scheduled job named
Furthermore, the synchronization may get triggered also if a donation for an unknown event arrives via the Twingle API
extension.
A CiviCRM site running [not in productive mode](https://docs.civicrm.org/sysadmin/en/latest/misc/staging-production/) will by default not run any scheduled jobs. In that case you can individually enable the TwingleSync job by adding the parameter runInNonProductionEnvironment=TRUE to the job.
## Known Issues
- The **Campaign Manager** displays a *«Campaign XY has been saved»* message even if the input validation failed and the
@ -81,4 +83,4 @@ extension.
- [ ] Make the Twingle Event Settings for contact matching, case creation and creation of soft credits an individual
setting in each project
- [ ] Make more payment methods available
- [ ] Make more payment methods available