Hi,
The files are created with inherent permissions, as defined by the web server (umask), using the WP_Filesystem wrapper, which is the default WordPress file system wrapper.
If there is a FS_CHMOD_FILE constant defined in the wp-config.php directory, WordPress will try to chmod the created files to those permissions. If that is by any chance defined in your case, that would probably explain it.
I suggest trying:
– Checking if the umask value is indeed defined correctly
– Defining the FS_CHMOD_FILE constant, to force the desired permissions
– Checking the wp-content/uploads/asp_upload directory permissions as well, and changing them if needed
– Deleting the style.instances.css file, and saving the search options again. It will be re-created upon save, hopefully with the right permissions.
I have tried to replicate the isssue, but the files are created with the correct permissions on all of my test environments.