| 1 | {* |
| 2 | +--------------------------------------------------------------------+ |
| 3 | | CiviCRM version 4.7 | |
| 4 | +--------------------------------------------------------------------+ |
| 5 | | Copyright CiviCRM LLC (c) 2004-2015 | |
| 6 | +--------------------------------------------------------------------+ |
| 7 | | This file is a part of CiviCRM. | |
| 8 | | | |
| 9 | | CiviCRM is free software; you can copy, modify, and distribute it | |
| 10 | | under the terms of the GNU Affero General Public License | |
| 11 | | Version 3, 19 November 2007 and the CiviCRM Licensing Exception. | |
| 12 | | | |
| 13 | | CiviCRM is distributed in the hope that it will be useful, but | |
| 14 | | WITHOUT ANY WARRANTY; without even the implied warranty of | |
| 15 | | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. | |
| 16 | | See the GNU Affero General Public License for more details. | |
| 17 | | | |
| 18 | | You should have received a copy of the GNU Affero General Public | |
| 19 | | License and the CiviCRM Licensing Exception along | |
| 20 | | with this program; if not, contact CiviCRM LLC | |
| 21 | | at info[AT]civicrm[DOT]org. If you have questions about the | |
| 22 | | GNU Affero General Public License or the licensing of CiviCRM, | |
| 23 | | see the CiviCRM license FAQ at http://civicrm.org/licensing | |
| 24 | +--------------------------------------------------------------------+ |
| 25 | *} |
| 26 | {htxt id="id-menu_url-title"} |
| 27 | {ts}Destination{/ts} |
| 28 | {/htxt} |
| 29 | {htxt id="id-menu_url"} |
| 30 | {ts}Enter the destination URL. Generally you should use relative URLs for CiviCRM pages (e.g. links to profiles). Use complete URLs for external pages. Leave this field empty if you are creating a menu section that does not have a clickable destination.{/ts} |
| 31 | {/htxt} |
| 32 | |
| 33 | {htxt id="id-parent-title"} |
| 34 | {ts}Parent Section{/ts} |
| 35 | {/htxt} |
| 36 | {htxt id="id-parent"} |
| 37 | {ts}Select the menu item corresponding to the section this item should be placed in. If this is a top-level menu, leave this field empty.{/ts} |
| 38 | {/htxt} |
| 39 | |
| 40 | {htxt id="id-has_separator-title"} |
| 41 | {ts}Separators{/ts} |
| 42 | {/htxt} |
| 43 | {htxt id="id-has_separator"} |
| 44 | {ts}Check this box to add a separator line between this menu item and the one below it.{/ts} |
| 45 | {/htxt} |
| 46 | |
| 47 | {htxt id="id-menu_permission-title"} |
| 48 | {ts}Permissions{/ts} |
| 49 | {/htxt} |
| 50 | {htxt id="id-menu_permission"} |
| 51 | {ts}You can assign one or more permissions to this menu item. Multiple permissions are additive by default. EXAMPLE: If you assign <em>access CiviContribute</em> and <em>administer CiviCRM</em> to a menu item, a user will need to have BOTH permissions to access it. You can change this behavior to "either / or" by changing the Operator below.{/ts} |
| 52 | {/htxt} |
| 53 | |
| 54 | {htxt id="id-permission_operator-title"} |
| 55 | {ts}Permission Operator{/ts} |
| 56 | {/htxt} |
| 57 | {htxt id="id-permission_operator"} |
| 58 | {ts}Set the Operator to "OR" if you've assigned multiple permissions and want access to be granted for any one of them. EXAMPLE: If you assign <em>access CiviContribute</em> and <em>administer CiviCRM</em> to a menu item, and set the Operator to "OR", users who have either of those permissions will have access.{/ts} |
| 59 | {/htxt} |