Jili mine Online casino.Claim Your Free 999 Pesos Bonus Today

allowing User Role to edit menus, but not other admin-level capabilities

katriel — Wed, 18 May 2016 11:21:15 +0000

Hi,
I created a new user role based on Editor. The new role should have all the capabilities of Editor – but should also be able to edit menus.

To do so, I choose the checkbox for edit_theme_options and then click update, but the change doesn’t stick and the new user role has no access to edit the menus.

What am I doing wrong?
The site is https://recoveryoptions.us/
Much thanks.

https://www.ads-software.com/plugins/user-role-editor/

menu translation disappeared (urgent!)

whitetiger25 — Wed, 13 Apr 2016 17:03:39 +0000

I have my website in 5 languages.

Yesterday I edit one of my menus, then I realized that in the menu I just saved I lost all my translation of the menu items. The contents are okay, but now the menu stuck in one language on which I lastly made changes.

Please anybody can help me?

https://www.ads-software.com/plugins/qtranslate-x/

Remove part of seller dashboard

LforLars — Fri, 01 Jan 2016 16:17:49 +0000

Hi,

I’ve been trying to modify some parts of the seller dashboard.
And things are going quite well, but I’m running into some issues with removing for example the “Other options” menu when adding a new product.

Any chance you have something similar to this guide?
https://docs.wedevs.com/docs/dokan/developer-documentation/adding-removing-url-dokan-dashboard/

Thanks in advance,

Lars

https://www.ads-software.com/plugins/dokan-lite/

wp catalogue in edit menus

smartgomez — Fri, 14 Nov 2014 00:05:56 +0000

i hope you are able to help mi with to costumize the menu mean while i am using the shortcut into a page.

Why i am not able to see the wp catalogue categories in the Edit menus onto the appearence-menus
what i need to do for to activate ?

WP 4.0
WP catalogue 1.7.2

https://facildepromover.com/fuentes-de-ingresos/

https://facildepromover.com/wp-content/uploads/2014/11/wp-ctalogue-edit-menus.jpg

thanks

https://www.ads-software.com/plugins/wp-catalogue/

Categories and Links drop-down in Edit menu not working

juicy99 — Tue, 24 Dec 2013 15:31:04 +0000

I have been making changes on the menu with no issues until upgrading to Version 3.8. When you open Edit Menus only Pages is open and the following drop-downs no longer work: Links, Categories, Screen Options and Help, and Pages will not collapse, so I am unable to Edit the Menu. I am using Genesis Theme Version: 2.0.1 · Released: August 21, 2013

Edit Menus page – No Custom Links option

deonsa — Tue, 03 Dec 2013 03:20:44 +0000

Hi,

I’m using multisite and when I go to any of the sites in the network, I don’t see the Custom Links option on the Edit Menus page.

I’ve tried deactivationg plugins and switching to default theme, to no avail.

Any suggestions would be appreciated.

Adding Custom Post Type on freshly installed WP

emsone — Sun, 13 Oct 2013 21:16:55 +0000

Hey folks!

I recently ran into a weird problem with registering a custom post type through a plugin on a fresh WP system: When activating the plugin as the first thing after installing, the custom post type wouldn’t show under Appearance->Menus. Normally custom post types show in the menu item box on the left (if not disabled when calling register_post_type), but in this case the entry was missing. Deactivating and re-activating the plugin didn’t help. Setting the show_in_nav_menus parameter explicitely to true didn’t help either. After fiddeling around with the code for a while I figured changing the post_type parameter of the register_post_type function will add the CPT to the menu item box.

In the end it became clear that there wasn’t a problem with the plugin code, but something super odd: when activating the plugin after loading the Appearance->Menus page at least once, the new custom post type is added perfectly fine to the menu item box. It seems as if on first load of the Menus page WP does soemthing that is vitally important to integrate CPTs into the menu configuration interface.

As this is such an odd behaviour, I considered sharing it and maybe saving someone else a headache. I didn’t find anything on the forum…

Here’s the plugin code I used for testing:

add_action( 'init', 'create_cp_A', 8 );

function create_cp_A() {

	$labels = array(
		'name'               => _x( 'A Posts', 'post type general name' ),
		'singular_name'      => _x( 'A Post', 'post type singular name' ),
		'add_new'            => _x( 'Add New', 'book' ),
		'add_new_item'       => __( 'Add New A Post' ),
		'edit_item'          => __( 'Edit A Post' ),
		'new_item'           => __( 'New A Post' ),
		'all_items'          => __( 'All A Posts' ),
		'view_item'          => __( 'View A Post' ),
		'search_items'       => __( 'Search A Posts' ),
		'not_found'          => __( 'No A Posts found' ),
		'not_found_in_trash' => __( 'No A Posts found in the Trash' ),
		'parent_item_colon'  => '',
		'menu_name'          => 'A Posts'
	);
	$args = array(
		'labels'        		=> $labels,
		'description'   		=> 'CP for testing purposes',
		'public'        		=> true,
		'menu_position' 		=> 5,
		'supports'      		=> array( 'title', 'editor', 'author', 'thumbnail', 'excerpt', 'comments', 'revisions' ),
		'has_archive'   		=> true,
		'exclude_from_search'		=> false
	);
	register_post_type( 'cp_A', $args );
}

Cheers

jQuery Solves: How to allow Editors to edit Menus (only!)

MyTeeFunny — Tue, 19 Feb 2013 07:46:00 +0000

PREFACE:
I previously posted this, but while that version of the code worked, it broke the rules of having CSS styles NOT in the < head > section. So I reworked it to use jQuery instead, so there is no issue or problems with standards validation. I hope!

THE NEW AND IMPROVED VERSION USING jQUERY:
A jQuery Solution for non-Admins (ie, Editor) to have access to APPEARANCE Menus and ONLY Menus (or more!). Admin’s or those roles given ‘edit_theme_options’ capabilities, have access to the Appearance sub-menus for Themes, Widgets, Menus, and Background. This CSS solution allows you to hide one or more of the sub-menus, preventing unwanted access to the options you don’t want Users to have and allowing access to those you do.

I’m going to present the jQuery code piece that does the job first, so you don’t have to read the What, Why and How here. I’ll put the info and write up about it after the code.

THE CODE:

MORE INFORMATION:
Place the PHP/jQuery code snippet in your admin-footer.php file, JUST BEFORE the ending element tag. The admin-footer.php file is located in the wp-admin directory.

To choose which Appearance sub-menu(s) you want to allow access to, simply comment out the jQuery line for that option or menu item. To remove or deny access to an option/menu item, leave it active (not commented out). The code snippet has Help Comments that explains this as well.

ABOUT THE CODE:
The IF statements are used to check and see if the logged in user is an Admin or non-Admin user. True Admins should only have access to the “manage_options” capability and all other users or roles should not.

If a user is not an Admin BUT HAS the ‘edit_theme_options’ capability added to their assigned role (ie, Editor), only then will the jQuery statements will be processed to either Remove or Keep the options you want them to have based on whether or not which jQuery lines have been commented out or not. It’s that simple.

AN IMPORTANT POINT:
For this jQuery Solution to have any affect on what sub-menus are displayed, the ‘edit_theme_options’ capability must be given to the role (or roles) that need or want to have access to the Appearance sub-menus (for Themes, Widgets, Menus, and Backrounds).

There are various plugins available that can modify or extend roles, or you can do it yourself by editing another file and adding the proper code to it. For your convenience, I will add how to do this here if you don’t want another plugin to install, or just to test this jQuery Solution first…

Edit and add the follwing code snippet to the functions.php file in your WordPress Theme. Put the code at the end of the functions.php file, so it’s not nested by accident in any logic statements or functions.

CODE FOR ASSIGNING EDITOR ROLE THE ‘edit_theme_options’ CAPABILITY:

add_cap('edit_theme_options');

	// For more CAP types and info, go to www.ads-software.com - Search for:  ROLES and CAPABILITIES
   ?>

That’s it. Now login as a user with the Editor role to test it! (The jQuery Solution needs to be installed too!)

Hope you find this useful to your needs!

PS ~ This would make a great add-on feature or enhancement to any of the Role & Capabilities Plugins out there…

Solution to: How to allow Editors to edit Menus (only!)

MyTeeFunny — Mon, 18 Feb 2013 09:51:39 +0000

Hallelujah! I finally found a way to allow Editors (or other roles) to just have the ability to edit Menus – without access to Themes, Widgets or Background, that is normally only allowed to Admins.

Actually, the solution allows you to Enable or Disable ANY of the APPEARANCE options (sub-menus: Themes, Widgets, Menus, Background) that is reserved only for Admins.

My search for a way to do this (Google, StackExchange, WP Forums, etc.) came up empty handed because granting the ‘edit_theme_options’ capability is not granular and is (until now) an “All or Nothing” solution as posted and commented on throughout all the posts, articles, forums and comments that I had come across.

In other words, if you granted ‘edit_theme_options’ to a role, such as an Editor, the role had access to all options: Themes, Widgets, Menus, and Background – no matter what.

Then in a moment of inspiration and Thanks to Firebug, I had thought of the idea of why not hide those elements via CSS for which you cannot control? Bingo.

After about 3 hours research and figuring out CSS selectors (and several 1 hour breaks to help my wife paint the kitchen – Hey: Happy Wife = Happy Life! And I’m very happy, btw), I figured out a quick, easy and elegant solution. Actually, I spent more time writing the comments than figuring out the CSS selectors to use…

The Rest of the Story is in the comments of the code snippet. Yes, I prefaced the actual short amount of code with a LONG Comment Intro. But there’s a reason for it. Hey, it’ my code and I can comment if I want to! lol

Here you go:

The whole Code with Comments follows. However I noticed sliding the view back and forth to read the comments/code is a real pain, so after the Code section, is the Comments by it’s self, for your reading pleasure…

Then I realized the WP Wizards out there probably just want the code snippet by itself, no explanations required. So for that, scroll to the very end of this post to get it.

 provided should override anything previous.
 * Finally, the Dashboard for any User comes from the wp-admin directory and files.  Ergo, the admin-footer.php
 *
 * NOTE: Where to put this?  Try AFTER:   AND BEFORE: 
 *
 * This addition to the wp-admin footer uses CSS selectors to HIDE {display:none} the APPEARANCE sub-menu options
 * you don't want non-Admins to have by default, because the 'edit_theme_options' capability is "all or nothing".
 * This modification/addition fixes that.  Simply comment out the CSS style line below for the option you WANT to
 * allow, leaving any remaing active lines to hide that option from being available.  The IF statements are used
 * to check and see if the logged in user is an Admin or non-Admin user.  (True Admins should only have access to
 * the "manage_options" capability.)
 *
 * But how does one give non-Admins (such as Editor's) specific and limited Admin functions or options such as the
 * 'edit_theme_options' capability?  While there may be other plugins available that can do this, the plugin I have
 * found that works well for me is the Advanced Access Manager (AAM) plugin.  While not intuitive (Okay, not much
 * in the way of "on page" Help, FAQ's or Readme's, but once you figure out how it works, it is very simple to use.
 * I've not delved into it much, as I only set the Editor role to have certain Admin functionality.  Caveat emptor!
 *
 * Oh what the heck...  The quick and dirty on the Advanced Access Manager (AAM) plugin after initial activation:
 * (1) To remove the "Config File is not Writable" message, you will need to give write permissions to this file:
 * .../wp-content/plugins/advanced-access-manager/config.ini  (minimum 666/777  depending on server hosting, etc.)
 * (2) To remove the "Module Directory is not Writable" message, you will need to give write permissions to this
 * directory:  .../wp-content/plugins/advanced-access-manager/model  (chmod 777 on directory only, NO recursive!)
 *
 * The "Read more..." links takes you to the author's website Forum for Troubleshooting with no clear answers...
 * Fortunately I provided clear answers.  (Note the Premium version requires the above file and directory to have
 * the permissions set to work right.  What's good for Premimum must be good for the free Basic version, right?)
 *
 * NOTE:  I suggest enabling permissions BEFORE making changes with AAM, then revert back to protected settings
 *	  AFTERWARDS for the file and directory permissions.  I mean, who wants to open things up for hackers?
 *	  It shouldn't a big bother to do this, as how often do you really need to modify the Roles? Set & Forget.
 *
 * Now, to understand how AAM works:  Select ACCESS MANAGER option under the AWM GROUP (anything else displays info
 * and upselling to Premium version of AAM and another plugin by the author.  Plus a Javascript error message. lol).
 *
 * Once you're in the Access Manager, there are three (3) panels displayed: (A) Options List panel with Tabs, then
 * (B) General panel in the upper right, and (C) Role Manager panel (below General).  What you need to know (as I
 * finally figured out) is to FIRST go to the General panel and CHANGE the current role from Administrator to the
 * Editor (or whatever role you want to edit/change).  Then in the Options List panel, select the CAPABILITIES tab
 * to display the current capabilities of the current role you selected previously in the General panel.  What will
 * happen is the Options List panel will now display the CURRENT options available for the role selected, including
 * any and all previous modifications made and SAVED previously with AAM.  If no previous changes, its WP defaults.
 *
 * One thing you need to know:  The buttons in the lower right area of the Options List panel (Admin, Editor, etc.)
 * sets all the options to the WORDPRESS DEFAULTS for the ROLE of the button clicked.  Use them only to set the WP
 * original defaults for the role, then in the General Panel, click the SAVE button to make it happen.  As long as
 * you don't click Save, no harm or change is made.  Whew!  (Author is not fluent in English, so syntax is... odd.)
 *
 * So now that you've selected the Role (ie, Editor) in the General panel and then selected the Capabilities tab in
 * the Options List panel, you are now ready to add/edit/modify capabilites of the Role by checking or un-checking
 * options as you desire.  Once you are done, click the SAVE button in the General panel.  That's it.  Now you have
 * just added/removed capabilites for that Role.  (My suggestion is to NEVER edit the Administrator's Role unless
 * you absolutely and positively know what you are doing.  Can you say Lockout?  Besides, Admin's are supposed to
 * be ALL POWERFUL, so why diminish it?  Google:  BOFH Stories  (Very Educational, lol)
 *
 * Another sweet thing about AAM btw, is that it sees/picks up on other Admin type plugins and lists them under the
 * Capabilites tab under the MISCELLANEOUS Section (well, Author spells is MISCELANEOUS :^).  So if you want, you
 * can easily give/extend those Admin functions to Editors or other Roles as you like. (ie, Calendar Event plugins)
 *
 * Finally, if you don't want to Add Another Plugin, you can edit and modify the (or Theme's) functions.php file to
 * add the following snippet to just give/allow the Editor Role the 'edit_theme_options' capability:
 *
   add_cap('edit_theme_options'); // More CAP types and info at WP.org - Search for:  ROLES and CAPABILITIES
   ?>
 *
 * The End
 *
 * PS ~ You're welcome!
 * PSS ~ Why all the verbage? 'Cuz you'll read the post, cut & paste to use it, then forget where & why you did it.
 *	 Now it's in the Mod's comments! (Unless you delete the comments!  Then you're up a creek without a paddle.)
 */

if ( is_user_logged_in() ) { // This IF may be redundant, but safe is better than sorry...
	if ( current_user_can('edit_theme_options') && !current_user_can('manage_options') ) { // Check if non-Admin

	// NOTE: All

Just They Comments, Please:

A Solution for non-Admins (ie, Editor’s) for accessing (Admin’s) Menus and ONLY Menus (or more if you like). A Short Story told Long… You can remove the comments if you want, or choose to keep them for reference sake! (Verbosity is due to that while many may be WP Wizards, most are not. Plus, I like the sound of my typing…)

Why in the Footer? Because CSS is hierarchial in nature, what comes after usually supercedes what came before. The Footer is the last piece/section to load, therefore any