x

Main chapters

  1. LimeSurvey Cloud vs LimeSurvey CE
  2. LimeSurvey Cloud - Quick start guide
  3. LimeSurvey CE - Installation
  4. How to design a good survey (Guide)
  5. Getting started
  6. LimeSurvey configuration
  7. Introduction - Surveys
  8. View survey settings
  9. View survey menu
  10. View survey structure
  11. Introduction - Questions
  12. Introduction - Question Groups
  13. Introduction - Surveys - Management
  14. Survey toolbar options
  15. Multilingual survey
  16. Quick start guide - ExpressionScript
  17. Advanced features
  18. General FAQ
  19. Troubleshooting
  20. Workarounds
  21. License
  22. Version change log
  23. Plugins - Advanced
 Actions

Cron (command): Difference between revisions

From LimeSurvey Manual

DenisChenu (talk | contribs)
m code
Sammousa (talk | contribs)
No edit summary
Line 8: Line 8:


This event need to be call with php cli instruction.
This event need to be call with php cli instruction.
<code>php /yourlimesurveydir/php application/commands/console.php plugin cron --interval=X<code>
<code>php yourlimesurveydir/application/commands/console.php plugin cron --interval=X<code>


'''Input'''
'''Input'''


The event receives the following information:
The event receives the following information:
 
''interval'' the interval parameter, set this to the interval (in minutes) you run this cron job. Plugins can use this information to self-limit their execution time, or get an idea of when the event will fire next.
''interval'' the interval parameter




[[Category:Plugins events]]
[[Category:Plugins events]]

Revision as of 17:38, 5 April 2014

 Hint: This features is available starting in version 2.06


When

This event happen when server admin set a crontab instruction.

How to use

This event need to be call with php cli instruction. php yourlimesurveydir/application/commands/console.php plugin cron --interval=X

Input

The event receives the following information: interval the interval parameter, set this to the interval (in minutes) you run this cron job. Plugins can use this information to self-limit their execution time, or get an idea of when the event will fire next.