Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Yakforms Yakforms
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • YakformsYakforms
  • YakformsYakforms
  • Wiki
  • Expiration of webforms

Expiration of webforms · Changes

Page history
Update Expiration of webforms authored Jul 06, 2020 by theo lem's avatar theo lem
Show whitespace changes
Inline Side-by-side
Expiration-of-webforms.md
View page @ 8fa01b13
...@@ -15,6 +15,8 @@ The following variables can be modified at the top of `framaforms_cron()` in ord ...@@ -15,6 +15,8 @@ The following variables can be modified at the top of `framaforms_cron()` in ord
* `cron_frequency` : amount of time between two cron runs. The module will check at each call to Drupal cron when `framaforms_cron()` was last run. `-1 day` means that "framaforms_cron should be run only if the last run is older that 1 day". You can also set it to `-1 week`, `-2 days`, `-2 months`, to your liking, but don't forget the `-` sign. * `cron_frequency` : amount of time between two cron runs. The module will check at each call to Drupal cron when `framaforms_cron()` was last run. `-1 day` means that "framaforms_cron should be run only if the last run is older that 1 day". You can also set it to `-1 week`, `-2 days`, `-2 months`, to your liking, but don't forget the `-` sign.
**If you do not wish to implement webform expiration in your Framaforms instance** (meaning all webforms and submissions will live forever in your database), you can : **If you do not wish to implement automatic webform deletion in your Framaforms instance** (meaning all webforms and submissions will live forever in your database), you can simply browse to `yoururl.ex/admin/config/system/framaforms` and set the expiration period to 0. Forms won't be deleted after that.
* Go to `yourdomainname.example/admin/cron` and set the cron run to "never", deactivating Drupal cron alltogether.
* If other modules need cron runs, you'll need to dive into the code : you can comment the whole `framaforms_cron()` function or just add `return;` as its first line to avoid running it. **If you want to deactivate the expiration of webforms altogether** (meaning forms will stay published even after the expiration date), simply browse to `yoururl.ex/admin/config/workflow/rules/reaction/manage/rules_expiration_form1_expired` and delete the "Unpublish content" action. Forms won't ever expire after that.
\ No newline at end of file
This is **not recommanded** if your instance is used intensively : your database will grow forever and a lot of this data can be useless.
\ No newline at end of file
Clone repository
  • Changing an instance language
  • Common issues
  • Configuring Yakforms
  • Custom scripts
  • Enhancing Yakforms
  • Expiration of webforms
  • From Framaforms to Yakforms
  • Installing Yakforms through the installation profile
  • Module : yakforms
  • Module : yakforms_public_results
  • Module : yakforms_share_results
  • Module : yakforms_spam
  • Produce a release
  • Translating Yakforms
  • Working with the Yakforms feature
View All Pages