Bug #7173
Can't access administrator settings on a fresh AtoM install, error 500
Status: | Verified | Start date: | 08/30/2014 | |
---|---|---|---|---|
Priority: | Critical | Due date: | ||
Assignee: | Dan Gillean | % Done: | 0% | |
Category: | Administration / settings | Estimated time: | 2.00 hours | |
Target version: | Release 2.1.0 | |||
Google Code Legacy ID: | Tested version: | 2.1 | ||
Sponsored: | No | Requires documentation: |
Description
I noticed this while trying to squash some other bugs!
Steps to reproduce:
1. Clone a new copy of AtoM qa/2.1.x
2. Set it up at normal
3. Try logging in as an administrator
4. Go to Admin->Settings
5. Error 500 is given
Expected result:
You should be able to log in as admin and go to admin->settings after a fresh install.
Work around:
1. Add a new archival description
2. Attach a digital object
3. You can now get to admin->settings
Jesús, I'm assigning to you because I'm 99% sure this is an issue related to how you told me we create the uploads/ folder now only after the first digital object upload. I think that some code in admin->settings is assuming that uploads/ already exists and hence is crashing. Perhaps we could move the create uploads/ folder code to sfInstallPlugin?
Related issues
History
#1 Updated by Mike Gale over 7 years ago
- File Screenshot-1.png added
#2 Updated by Jesús García Crespo over 7 years ago
Thanks, Mike! You just stepped on my ticket! :P
#3 Updated by Jesús García Crespo over 7 years ago
- Status changed from New to QA/Review
- Assignee changed from Jesús García Crespo to Dan Gillean
#4 Updated by Dan Gillean over 7 years ago
- Status changed from QA/Review to Verified