Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify cron-related configuration of the Drupal module #99

Open
tanius opened this issue Apr 2, 2016 · 1 comment
Open

Clarify cron-related configuration of the Drupal module #99

tanius opened this issue Apr 2, 2016 · 1 comment

Comments

@tanius
Copy link
Member

tanius commented Apr 2, 2016

To make it simpler to understand and create the right cron configuration for Edgesense, I propose the following two changes:

  • Move the "Run During Cron" tickbox from the "Script Configuration" (admin/edgesense/script-param) screen to the "Script Execution" (admin/edgesense/script-run) screen, since that one contains a section detailing options to call the script already.
  • Rename the "Run During Cron" tickbox to "Execute as part of Drupal's cron tasks." And document below it that "If you do not choose this option, you will have to make sure by other means that the script is executed periodically. See here for details."
  • In the "Script Configuration" (admin/edgesense/script-param) screen, change the wording "If you choose to not run the script during cron" to "If you choose to not execute the script as part of Drupal's cron tasks". Because, if not choosing that option, the script will most probably still be "run during cron", namely with a dedicated edgesense_drupal command somewhere in crontab.
  • In the "Script Configuration" (admin/edgesense/script-param) screen, change the three help texts that read "If you choose to not run the script during cron then please append "?edgesense_views_key=[…]" to the end of your URL's. For example: […]" to appear only in the case the user unticked the "Run During Cron" checkbox and only for fields where the user uses URLs instead of file paths. In all other cases, it is a lot of confusing text (the majority of the help text even) that is not needed. Also make it clear this suffix is not needed when using file paths.
@tanius
Copy link
Member Author

tanius commented Jul 8, 2016

And two more proposals:

  • Again in the "Script Configuration" (admin/edgesense/script-param) screen, add a short explanation why the "?edgesense_views_key=[…]" parameter is needed in case of "Run During Cron: No". It should be shown only if "Run During Cron: No" is configured, and could read: "This is needed in order to give edgesense_drupal access to these access-protected views, which it will not have by default when running outside the Drupal environment."
  • Again about the same configuration screen, make it clear that when using "Run During Cron: No", one must configure URLs for accessing the Users / Nodes / Comments. Paths will not be accepted (because these json files are not updated by Drupal cron then, see Updating of edgesense_*.json files stopped #102 ), and it is also neither possible nor accepted to append the "?edgesense_views_key=[…]" parameter to paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant