Comment 1 for bug 1224750

I think the manual is probably incorrect on this one. It doesn't make sense to have a Site Files directory of files that are "accessible" to Public users. In Mahara a file artefact being "accessible" could mean one of two things. The first is that it could mean a user can view the file, but this is controlled entirely by whether the file is used in a Page that the user can view, so that can't be what's meant here. The second is that it could mean a user can use the file in their Pages, but Public users can't create or edit pages, so it can't mean that either.

I think the intended purpose of the hard-coded "Public" folder is that it's meant to be files that are accessible to all *logged-in* users in the site. In other words, if mahara.org wanted there to be a Mahara logo that was available to all users to add to their Pages, we could put that logo in the "Public" folder in Site Files.

I haven't yet tested to see if that's how the code currently works.