workflow_script
workflow_script copied to clipboard
imagemagick convert script doesn't work
Steps to reproduce
- Install external scripts
- Add automated tagging to uploaded files
- Run the command 'convert %x -interlace plane -strip -quality 80 -resize 1000x1000> $(basename %x)_1.jpg' on files that are tagged accordingly to step 2.
Expected behaviour
Image files should be converted according to command settings and have it's original name with the suffix '_1'. This works properly when the command is run directly at the server.
Actual behaviour
Nothing happens at all - flow log is empty. The automated tagging applies, but not the external script.
Workflow Script app
Workflow Script app version: 1.4.0
Server configuration
Operating system: Ubuntu Server 20.04 LTS
Web server: Nginx
Database: MariaDB 10.3.22
PHP version: 7.4.3
Nextcloud Version: 19.0.3
Where did you install Nextcloud from: Nextcloud
Signing status:
No errors have been found.
List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: Testing on Local but the plan is to have this applied on files in external storage (SMB)
Are you using encryption: no
Server log (data/nextcloud.log)
Hej sebstrgg,
I am looking for exactly the same function - scale just uploaded pictures! It seems your one step beyond. On my side, I am not even able to activate the trigger on creating a new file. How did you do?
Some general tips, maybe it helps.
-
Can you first verify that the workflow is actually triggered by your action, e. g., by filling out the script part with
/usr/bin/php /var/www/nextcloud/occ notification:generate YOUR_USERNAME "some message: %n"This should send you a nextcloud notifcation if the action can at least trigger something. -
Use absolute paths for all executables
-
Make sure user
www-datacan access all files scripts locations etc.
This issue can be closed I think. As it has been not been active for a very long time.
Please close the issue, if that is ok for you.
- /usr/bin/php /var/www/nextcloud/occ notification:generate YOUR_USERNAME "some message: %n"
Would be great if this could be added to the readme! And other debugging steps in general I think, as it seems others are having difficulties in ensuring their flows are running correctly.