access level warning message in File edit view

It still remains to be explained why the error happens, even if not functionality is affected at this point.
Up until 3.1.1, the warning message and the mysterious access level 0 did not show up.

Up until 3.1.1, the warning message and the mysterious access level 0 did not show up.

Exactly, it was added by v3.1.1, and it is intentional for the reasons explained previously

If newly created files do not have access level zero, then were are good here

As I've mentioned in an earlier post, the *existing* files where the warning message is showing already had the access level correctly set to Public.
I still think that the behaviour described in my opening post is not supposed to happen.

I still think that the behaviour described in my opening post is not supposed to happen.

The message was added because the file was not showing in frontend and users could not understand why it is not showing

The reason that file has this access level ?
Maybe because of upgrade from J1.5 or because of older FLEXIcontent bug that saved it with access level ZERO