You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
To make it simpler to understand and create the right cron configuration for Edgesense, I propose the following two changes:
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.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 dedicatededgesense_drupal
command somewhere in crontab.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.The text was updated successfully, but these errors were encountered: