New to Translating WordPress? Read through our Translator Handbook to get started. Hide
Prio | Original string | Translation | — |
---|---|---|---|
↑ | Hide custom menu items based on user roles. PLEASE READ THE FAQ IF YOU ARE NOT SEEING THE SETTINGS. | You have to log in to add a translation. | Details |
Original untranslated
Hide custom menu items based on user roles. PLEASE READ THE FAQ IF YOU ARE NOT SEEING THE SETTINGS.
You have to log in to edit this translation. |
|||
↑ | Nav Menu Roles | You have to log in to add a translation. | Details |
Original untranslated |
|||
Alternatively, you could do this universally by adding the following snippet to your child theme's <em>function.php</em> file or by adding it via the <a href="https://wordpress.org/plugins/code-snippets/">Code Snippets</a> plugin: | You have to log in to add a translation. | Details | |
Original untranslated
Alternatively, you could do this universally by adding the following snippet to your child theme's <em>function.php</em> file or by adding it via the <a href="https://wordpress.org/plugins/code-snippets/">Code Snippets</a> plugin:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
You must do this for every effected instance of <code>wp_nav_menu()</code> in your theme templates. It is not possible for me to tell you where they are located, but <code>header.php</code> is a very common location for the main menu. | You have to log in to add a translation. | Details | |
Original untranslated
You must do this for every effected instance of <code>wp_nav_menu()</code> in your theme templates. It is not possible for me to tell you where they are located, but <code>header.php</code> is a very common location for the main menu.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Only works with WordPress less than 5.4. | You have to log in to add a translation. | Details | |
Original untranslated
Only works with WordPress less than 5.4.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
But for those that still are, they definitely need to include the now-core hook. | You have to log in to add a translation. | Details | |
Original untranslated
But for those that still are, they definitely need to include the now-core hook.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Since WordPress 5.4, I no longer replace the Walker at all and would advise other plugins and themes to do the same. | You have to log in to add a translation. | Details | |
Original untranslated
Since WordPress 5.4, I no longer replace the Walker at all and would advise other plugins and themes to do the same.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Prior to WordPress 5.4, I used this idea and modified my admin nav menu Walker to <em>only</em> adding the following lines (right after the description input): | You have to log in to add a translation. | Details | |
Original untranslated
Prior to WordPress 5.4, I used this idea and modified my admin nav menu Walker to <em>only</em> adding the following lines (right after the description input):
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Nav Menu Roles is therefore attaching directly to this hook without needing to replace the custom Admin Menu Walker, of which there can still be only one. If the Walker is replaced by a theme/plugin and the core hook is not included, then Nav Menu Roles cannot add it's fields. | You have to log in to add a translation. | Details | |
Original untranslated
Nav Menu Roles is therefore attaching directly to this hook without needing to replace the custom Admin Menu Walker, of which there can still be only one. If the Walker is replaced by a theme/plugin and the core hook is not included, then Nav Menu Roles cannot add it's fields.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
As of WordPress 5.4 the <code>wp_nav_menu_item_custom_fields</code> hook has been added to WordPress core. | You have to log in to add a translation. | Details | |
Original untranslated
As of WordPress 5.4 the <code>wp_nav_menu_item_custom_fields</code> hook has been added to WordPress core.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
This is likely due to a conflict with another plugin (or theme). | You have to log in to add a translation. | Details | |
Original untranslated
This is likely due to a conflict with another plugin (or theme).
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Add the following snippet to your theme's <code>functions.php</code> file: | You have to log in to add a translation. | Details | |
Original untranslated
Add the following snippet to your theme's <code>functions.php</code> file:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
If your membership plugin is not listed here, you may be able to use the above bridge plugins as a template. Scroll down to the bottom of the main plugin file and you will see a section for "Helper Functions". If you modify the 3 wrapper functions according to your membership plugin's logic, the rest of the plugin should handle the integration with Nav Menu Roles. | You have to log in to add a translation. | Details | |
Original untranslated
If your membership plugin is not listed here, you may be able to use the above bridge plugins as a template. Scroll down to the bottom of the main plugin file and you will see a section for "Helper Functions". If you modify the 3 wrapper functions according to your membership plugin's logic, the rest of the plugin should handle the integration with Nav Menu Roles.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
The roles in NMR are filterable distinct from the global <code>$wp_roles</code>. This allows for compatibility to be added between plugins that don't use the core roles to determine access, like some membership plugins. | You have to log in to add a translation. | Details | |
Original untranslated
The roles in NMR are filterable distinct from the global <code>$wp_roles</code>. This allows for compatibility to be added between plugins that don't use the core roles to determine access, like some membership plugins.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
<a href="https://github.com/helgatheviking/nav-menu-roles-woocommerce-memberships">WooCommerce Memberships</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://github.com/helgatheviking/nav-menu-roles-woocommerce-memberships">WooCommerce Memberships</a>
CommentFound in faq list item. You have to log in to edit this translation. |
Export as
Comment
Short description.