Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Redmine Plugin Extension and Development

You're reading from   Redmine Plugin Extension and Development If you'd like to customize Redmine to meet your own precise project management needs, this is the ideal guide to understanding and realizing the full potential of plugins. Full of real-world examples and clear instructions.

Arrow left icon
Product type Paperback
Published in Mar 2014
Publisher
ISBN-13 9781783288748
Length 114 pages
Edition Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Alex Bevilacqua Alex Bevilacqua
Author Profile Icon Alex Bevilacqua
Alex Bevilacqua
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Redmine Plugin Extension and Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Introduction to Redmine Plugins FREE CHAPTER 2. Extending Redmine Using Hooks 3. Permissions and Security 4. Attaching Files to Models 5. Making Models Searchable 6. Interacting with the Activity Stream 7. Managing Plugin Settings 8. Testing Your Plugin Releasing Your Plugin Index

Configuration management


The partial view we defined when initializing our plugin's settings field will be rendered when an administrator clicks on the Configure link for our plugin:

The partial that we'll create will be made up of a number of groups. Each group represents a settings key that we want to update a value for.

The fields that we'll define will be a subset of a predefined form, which is rendered if our plugin has defined a partial to be used for configuration. This partial is injected into the form at /path/to/redmine/app/views/settings/plugin.html.erb.

As the form tag has already been defined, all we have to provide are input tags that capture our settings, values. For this to work properly, we name the input fields settings[our_setting_name].

<p>
  <%= label_tag :settings_sort_category_tree, l(:allow_sort_category_tree) %>
  <%= check_box_tag 'settings[sort_category_tree]', 1, @settings[:sort_category_tree] %>
</p>
<p>
  <%= label_tag :settings_show_category_totals...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image