customer cron jobs get prefixed with the user's home directory
If a customer creates a cron job with a command that doesn't start with /, the web user's home directory is automatically prepended to the command. This fact (which is useful by itself) is unfortunately not mentioned in the frontend, and thus not obvious to the user.
For me, this was a problem for two types of commands:
1.) "$HOME/some-script.sh" => quoted to avoid problems with spaces in the home directory; one can never know ;-) This can be easily worked around by prefixing another /: /"$HOME/..."
2.) cd /some/dir && ./do_something.sh This can be worked around too: /bin/true && cd /some/dir && ...
It would be nice if prefixing of the home directory was made optional (via a checkbox); this can be switch on by default, so existing cron jobs will continue to work.
But there should at least be a note in the frontend about this.