Feature #8817

Attachments/Plugin assets directory writable errors

Added by Dave Abrahams almost 2 years ago. Updated 9 months ago.

Status:NewStart date:2011-07-14
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Plugin API
Target version:-
Resolution:

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/" writable

History

#1 Updated by Brian Lacy almost 2 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 12 months 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 12 months ago

  • Category set to Plugin API

#4 Updated by Etienne Massip 12 months ago

  • Assignee set to Jean-Philippe Lang

Think it should be bundled indeed since it is not automatically created?

#5 Updated by VVD VVD 10 months ago

Anthony Cartmell wrote:

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.

Correct path is: @<redmine>/public/plugin_assets/

Work on Redmine 2.0.3 - tested 1 mins ago.

#6 Updated by Kyle Janse van Rensburg 9 months 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

Also available in: Atom PDF