Reason:
This was actually addressed in our latest bug squashing effort and the fix is currently in code review. It should be part of the 5.1 release, but there is not ETA.
Fix:
The current work around is changing the permissions to 644.
This was actually addressed in our latest bug squashing effort and the fix is currently in code review. It should be part of the 5.1 release, but there is not ETA.
The current work around is changing the permissions to 644.