I've just tried attaching a pdf file to a database entry on our Moodle QA Testing site then logging in as a guest. I had no problem opening the pdf file.
Is your database activity on the front page or have you modified the guest role at all? Perhaps you can check whether you can reproduce the problem on the QA Testing site.
I am afraid I may not have been entirely clear with my role definitions. I require either visitor access or guest access (but auto logged in).
The database activity is on the frontpage (hidden in the main menu box).
What I require is that of moodle.org theme database. No logon required to view or download.
Currently a visitor can view entries but when clicking on the attached file and sent to the logon page. They need to be able to download the file without being logged in.
If the database is part of a course allowing guest access, then guests can view and download the files as desired without prompting as I have the auto login guests set to yes.
But as the database in on the frontpage, there is no option to "allow guest access" as there is with courses. Therefore visitors are not automatically logged in as a guest. They have the option to login as a guest on the login screen which then allows them download, but this is assuming the visitor knows about the guest option or could be bothered.
I need visitors to be able to view databse entries and download attached files, either remaining as a visitor or being auto logged in as a guest, just like I can without being logged in on moodle.org (themes database).
Does it have anything to do with the default front page roles as my is set to guest, although didn't make any difference from when it was set to none. Can't say I truely understand this setting and it's impact.
PS. I have been able to replicate the problem on the QA site by adding a databse activity to the frontpage label.
OK, so it's a problem with the database being a front page activity. Assuming you've not done so already, please report the issue in the Moodle Tracker, explaining how to reproduce it on the QA site and also including a link to this discussion.
As it's a 2.0 issue, I'm going to move this thread to the testing and QA forum to ensure testers are aware of the problem.
I have it listed as "Major" importance in the tracker, should it be upgraded?
I need this resolved as to move to 2.0.
Glenn, thanks for reporting the issue in the Moodle tracker. I think 'Major' is the correct priority level, based on the following statements (from the tracker documentation):
- Blocker - Blocks development and/or testing work, production could not run.
- Critical - Crashes, loss of data, severe memory leak.
- Major - Major loss of function.
- Minor - Minor loss of function, or other problem where easy workaround is available.
- Trivial - Cosmetic problem like misspelled words or misaligned text.
Please be patient for the issue to be fixed. Otherwise, if you require an urgent fix you may wish to consider contacting one of our Moodle Partners.