Feature #8817
Attachments/Plugin assets directory writable errors
| Status: | Closed | Start date: | 2011-07-14 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | Plugin API | |||
| Target version: | 2.6.1 | |||
| Resolution: | Fixed |
Description
These errors are a bit inscrutable because they don't give the actual path to the directory in question. I found "assets" subdirectories in many of the plugin's own directories, all of which were writable, so I didn't know what to make of the message.
Please change the messages to, e.g.,
"..../public/plugin_assets/" writableAssociated revisions
Add public/plugin_assets directory (#8817).
Removed svn:ignore for public/plugin_assets directory (#8817).
Set svn:ignore to * for plugin_assets subdirectories (#8817).
Adds path to plugin_assets directory in admin/info (#8817).
History
#1
Updated by Brian Lacy over 9 years ago
Agreed, this is pretty confusing for a new Redmine user. The messages should be much more specific about what directories aren't accessible.
Also, in my case its because the directories don't appear to exist (though I can't be certain, since I'm not 100% what they're supposed to BE). It would be nice if Redmine could identify this case differently than a permissions issue -- i.e. "The ./public/plugin_assets/ directory does not exist".
#2
Updated by Anthony Cartmell over 8 years ago
Agree. I don't have any plugins, so <redmine>/public/plugin_assets didn't exist. Creating this directory and making it writeable by redmine fixed the error message.
#3
Updated by Etienne Massip over 8 years ago
- Category set to Plugin API
#4
Updated by Etienne Massip over 8 years ago
- Assignee set to Jean-Philippe Lang
Think it should be bundled indeed since it is not automatically created?
#5
Updated by VVD VVD over 8 years ago
Anthony Cartmell wrote:
Agree. I don't have any plugins, so
<redmine>/public/plugin_assetsdidn't exist. Creating this directory and making it writeable by redmine fixed the error message.
Correct path is: @<redmine>/public/plugin_assets/
Work on Redmine 2.0.3 - tested 1 mins ago.
#6
Updated by Kyle Janse van Rensburg about 8 years ago
For anyone else that ran into this issues, this worked for me:
sudo nano /etc/apache2/mods-available/passenger.conf
and add the following line:
PassengerDefaultUser www-data
Passenger runs as nobody by default so changing it to www-data worked for me
#7
Updated by Tim Whitehead over 7 years ago
Anthony Cartmell wrote:
Agree. I don't have any plugins, so
<redmine>/public/plugin_assetsdidn't exist. Creating this directory and making it writeable by redmine fixed the error message.
It is part of Step8, so long as new users are reading the instructions... But it also mentions tmp & tmp/pdf which already existed for me using the git repo.
New install of v2.3.1 without plug-ins. Would it be possible to create this directory by default? and/or provide a clearer message on the information page.
#8 Updated by Anonymous about 6 years ago
New install of v2.3.1 without plug-ins. Would it be possible to create this directory by default? and/or provide a clearer message on the information page.
redmine 2.6 the same here
#9
Updated by Jean-Philippe Lang about 6 years ago
- Status changed from New to Resolved
- Target version set to 2.6.1
- Resolution set to Fixed
Fixed, public/plugin_assets is now present out of the box and the admin/info now displays the path to this directory.
#11
Updated by joe hakim rahme over 5 years ago
sudo nano /etc/apache2/mods-available/passenger.conf
and add the following line:
PassengerDefaultUser www-data
I confirm that this worked for me on Ubuntu14.10 with libapache2-mod-passenger installed.