In my previous host, files and folders in /wp-content/upload/ had permissions 755. When I migrated to ec2 bitnami the /upload/ folder retained the 755 permission structure. Yet, now Wordpress users can no longer upload new files into an existing 755 folder (eg, upload a new image to an existing album for which folder with 755 permission already exists) or upload a file for which a new folder needs to be created first (eg, a new user cannot upload her avatar, as the system does not allow to create new folder in which to place the file).
I saw that the permissions in the orginal bitnami folder /wp-content/upload/ (prior to migration) was 775. Do I need to change all permissions in the files and folders contained in /wp-content/upload/ to 775? Or can I leave permissions as they are and do something else to enable uploads? Changing permissions of all files and folders is quite cumbersome.
Please note that Wordpress Codex recommends not to have 775 folders:
No directories should ever be given
777, even upload directories. Since
the php process is running as the
owner of the files, it gets the owners
permissions and can write to even a
Would changing the owner group to daemon:daemon help (from bitnami:bitnami)?