Enable logging set the wrong wrapper location

[unmaykr-a]

Not sure what triggered it, I restarted/updated my server a few hours before this. When looking at the new crons that I added and enabling logging on them, the wrapper was automatically set to /app/data/cron-log-wrapper.sh
On the old logged crons it's correct /opt/cronmaster/data/cron-log-wrapper.sh

This behavior did not change until I restarted the container. The volumes are mapped normally
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./scripts:/app/scripts
- ./data:/app/data
- ./snippets:/app/snippets

[floriancargoet]

I had the same problem today.
The logging script is /app/data/cron-log-wrapper.sh but it should be the path from the host, not from the container.
Same for saved scripts, they are defined as /app/scripts/my-script.sh instead of the path from the host.

I rolled back from 2.2.0 to 2.1.0, it appears to have fixed it. But since 2.2.0 was only released last week and this issue is older, I'm not sure that's it…

[rako123]

Same problem here with 2.2.0.
Running new jobs with logging enabled failed on my Ugreen NAS.
The logging script is /app/data/cron-log-wrapper.sh and scripts are /app/scripts/my-script.sh instead.
New scripts failed with Error 1.

Rolled back to version 2.1.0
This fixed the issue and I could schedule the new script and script runs with logging and no error

[DotNetRob]

Still the same issue on the latest version, rolled back to 2.1.0 again. Would be nice to get a fix since there has been security fixes in the last few versions.