Project

General

Profile

Actions

Feature #8817

closed

Attachments/Plugin assets directory writable errors

Added by Dave Abrahams almost 13 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Category:
Plugin API
Target version:
Start date:
2011-07-14
Due date:
% Done:

0%

Estimated time:
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/" writable
Actions #1

Updated by Brian Lacy almost 13 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".

Actions #2

Updated by Anthony Cartmell almost 12 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.

Actions #3

Updated by Etienne Massip almost 12 years ago

  • Category set to Plugin API
Actions #4

Updated by Etienne Massip almost 12 years ago

  • Assignee set to Jean-Philippe Lang

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

Actions #5

Updated by VVD VVD over 11 years 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.

Actions #6

Updated by Kyle Janse van Rensburg over 11 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

Actions #7

Updated by Tim Whitehead almost 11 years 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.

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.

Actions #8

Updated by Anonymous over 9 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

Actions #9

Updated by Jean-Philippe Lang over 9 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.

Actions #10

Updated by Jean-Philippe Lang over 9 years ago

  • Status changed from Resolved to Closed

Merged.

Actions #11

Updated by joe hakim rahme about 9 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.

Actions

Also available in: Atom PDF