Redmine

+1

+1

+1

+1

+1

Would you guys expect to be able to do something like:

Page A can only be viewed by users A B C?
Page B can only be views by users D F G and Group Z?

Or is a simple "Page protected" flag per page plus a "view protected page" permission good enough?

The second option is good for the beginning because it seems to be easy to implement and it's better than nothing.
Ideal to have them both.

+1
The secound option should be good enough - it could be similar to the new private issues feature.

The first option sounds really good - but like Kamil I'm not sure this is as easy to implement as option 2.
IMHO it would require a complete change of the permission system to really fit in. Right now I'm not aware of any Redmine-Feature that maintains a seperate permission list per object - although under some circumstances it would be great to have that.

+1

Are there any news on this feature?

there is the redmine_wiki_permissions plugin that can do this. i've recently put in a pull request so it works properly with 1.4. i haven't tried with 2.0. it shouldn't conflict with other plugins anymore.

+1
redmine_wiki_permissions plugin does not work with redmine >2.0

Tried to install redmine_wiki_permissions in 2.5 with rails 3.2 and came as far as

• install with _rails install
• move the redmine_wiki_permissions folder from vendor/plugins to plugins
• add dispatcher to Gemfile

Now I'm getting

redmine_wiki_permissions/init.rb:7:in `<top (required)>': undefined method `to_prepare' for Dispatcher:Module (NoMethodError)

on startup. I guess the dispatcher gem isn't 3.2 compatible

Any ideas? I'd really have the wiki permissions back now that my upgrade from redmine 1.0 to 2.5 has worked (basically installing rvm, doing a fresh redmine install and migrating the database).

+1