For a new WordPress install hosted on ApisCP, when attempting to crop an image via the WordPress dashboard it produces an error due to it not being able to write to the
/wp-content/uploads/* directories. The ownership for those directories is admin-xxx rather than apache. In either case, whether the directories are owned by apache or admin-xxx, the WordPress dashboard is still not able to write to these directories.
I am able to solve the problem by recursively adding write permissions for
How can I best solve this issue permission/ownership issue?
Which user actually owns the application?
Is it better to do this via the Terminal versus the ApisCP dashboard forms? I noticed that setting permissions on folders recursively only applies the change one level deep (the folder it directly applies to and the folders nested at the first level).