Overview
If you don't want to use the command line to create, edit or delete Cronjobs in the Crontabfile, this Module enables you to edit it in a Drupal-Form. You can enable Site-administrators to edit the Cronjobs, without giving them command-line access to your server.
Features
- Creating Cronjobs with configurable time presets
- Creating Cronjobs with custom time settings
- Show current active cronjobs
- Edit or delete active cronjobs
Sandbox Link: http://drupal.org/sandbox/laborb/1851792
Requirements
It is reqired that the webserver user is allowed to edit his crontab-file.
This module is developed for Drupal 7, but i am shure, i can convert it to Drupal 6, too.
GIT repository link
git clone --recursive --branch 7.x-1.x http://git.drupal.org/sandbox/laborb/1851792.git crontab_manager
I haven't reviewed other modules yet, but I will start imediatly to do so. I will edit the description and add my reviews as soon as possible.
Comments
Comment #1
mohs3n71 commentedauto review :
http://ventral.org/pareview/httpgitdrupalorgsandboxlaborb1851792git
you have some errors , first fix them
manual review :
in your crontab_manager.config.inc
in this section :
when you want explain about a parameter you should use @param ...
and some thing about .info file : it's not necessary to add version , drupal.org system will add it.
and also i think there is no need to add .module file in files[]
thank you ,
Mohsen
Comment #2
mohs3n71 commentedComment #3
labor b commentedFixed the errors, removed the files and version from .info.
I am not sure about the parameter thing in my config.inc, there are 2 variables to set up presets, but they are no parameters of a function, so i think @param would be not right here, or is it?
Comment #4
revureviewsite commentedHI,
First of all you should have to fixed this issue
The following git branches do not match the release branch pattern, you should remove/rename them. See http://drupal.org/node/1015226
remotes/origin/7.x-0.8
Thanks
Alok
Comment #5
pere orgacrontab_manager_timevalidate(), I'd replace every$return = FALSE;withreturn FALSE;and just return TRUE at the end (and drop the initial$return = TRUE;). A lot easier to follow.crontab_manager_form(), please do it consistently.Comment #5.0
pere orgaadded Sandbox link
Comment #6
labor b commentedthanks for you review, i updated the project page and the files.
Comment #7
asifnoor commented1. plz add Requirements to README file like having webserver edit permissions to cron tab file.
Comment #8
labor b commentedthank you, fixed it.
Comment #9
sashainparisHi,
I gonna try to be complementary with other reviews.
My PAReview test returns a small issue: http://ventral.org/pareview/httpgitdrupalorgsandboxlaborb1851792git
In the README.txt file, I would expect more details about the Risk of use and Context where to use it or not:
It seems the values are tested at form_validate(), but are not filtered at all before saving. I did not find any trace of the following functions in the code: check_*(),, filter_*(). You might consider using check_plain() before saving to file.
Hoping this will help.
Regards,
Alexandre
Comment #10
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
If you reopen this please keep in mind that we are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (found some problems with the project) or "reviewed & tested by the community" (found no major flaws).
Comment #10.0
klausichanged typos.