I'm receiving this error when trying to run chown on a folder as a custom command. I just upgraded my installation and never received this error before. I noticed other issues in the forum with this error, but none that apply to v4.2.5.
Thanks for your post. This bug has been added to tracker.
You can post new topics in this forum