Forum Replies Created

  • In reply to: Widgets capability for Editors


    As I was dissatisfied with the result I deleted my addition to the functions.php file.

    But this did not disactivate the changes…

    After a few difficult hours I remembered that User Role Editor had a button to reset a role to its original “core” state.


    Where had the changes been implemented after vanishing from the functions file ?

    In reply to: Widgets capability for Editors


    Thank you for your reply.

    I did some Google research.

    I found:

    I copied and pasted the code in the child-theme’s functions.php, so it is now :

    add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles' );
    function theme_enqueue_styles() {
    wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' );
    wp_enqueue_style( 'child-style', get_stylesheet_uri(), array( 'parent-style' ) );
    $role = get_role('editor');

    function custom_admin_menu() {

    $user = new WP_User(get_current_user_id());
    if (!empty( $user->roles) && is_array($user->roles)) {
    foreach ($user->roles as $role)
    $role = $role;

    if($role == "editor") {
    remove_submenu_page( 'themes.php', 'themes.php' );
    remove_submenu_page( 'themes.php', 'nav-menus.php' );

    add_action('admin_menu', 'custom_admin_menu');

    First time in my life I venture into a php file!

    The result is the Appearance menu is now accessible to Editors with the following submenus :

    customize, widgets, header, background, Graphene options !!! and Graphene FAQ.

    I want only Widgets to be accessible.

    It was the case with the Restrict widgets plugin, the Appearance menu offered only the Widget possibility. But I mentioned earlier Restrict widgets may be a bit inconvenient for the 5 or 6 Editors I have to train.

    I have tested User Role Editor and Capability Manager Enhanced but I saw nowhere any mention of widgets.

    I read that Members created the same problem that I mentioned : too many capabilities

    Thank you for your help. If I can’t find a better solution, Restrict Widgets will be a quite acceptable choice.

    In reply to: Replace Graphene slider


    Thanks for your helpful reply.

    I have no child theme yet as I know nothing about PHP. I’ve started to study tutorials about child themes and I’ll come back to the forum when I feel a bit more confident with them.

    In reply to: Replace Graphene slider


    I have found a reasonable solution to my problem. And it is very simple.

    The Graphene slider CAN do what I want : display only photos on which you can click to open external URLs as well as internal links.

    All is done is the TinyMCE Editor.

    I create as many pages as I have images to display. The titles of the pages will appear as captions.

    The pages are left EMPTY. The photos are FEATURED images linked to the pages.

    For each individual photo I have 2 settings to select in the specific options of the slider (we are still with TinyMCE. My version is not in English so I am not sure about the real wording).

    The first option is about global parameters or first image or custom links or Featured image. Selection should be featured image.

    Then we have something twice about URL of the custom image (?). The first text area can remain empty, The second is used to write or paste the permalink or URL of the document which will be opened by a click on the slider image.

    The relevant pages are selected in the Graphene options by their ID numbers.

    I am only 75% satisfied with this solution… I would like the link to open in a new page (target blank). But I don’t know how to do it.

    In reply to: TinyMCE 100% bug : Not acceptable


    In reply to: TinyMCE 100% bug : Not acceptable


    The second intervention has been the right one. I am 100% satisfied…

    Thank you Kenneth for your precise and patient help.

    In reply to: TinyMCE 100% bug : Not acceptable


    It took a little time before I could get in touch with the host server support. They asked me for my IP address and further details about the problem. Today’s reply informed me they had disabled mod_security and everything should be OK now.

    But it not!

    Still the same…

    In reply to: TinyMCE 100% bug : Not acceptable


    I had already searched French-speaking forums and found that the 406 message was often related to mod_security, so I changed .htaccess according to suggestions. With no effect.

    But what I noticed in many posts in the forum you recommended,

    is that contact with the host server support about this problem had always proved successful.

    So it is what I am going to do.

    I’ll keep you informed. Thanks a lot.

    In reply to: TinyMCE 100% bug : Not acceptable

    If that’s the correct plugin I linked to, then you should open a ticket here:

    But wait! Did you say this happened even with this plugin turned off? If that’s the case, then there’s probably something wrong with your WordPress install. Did I read that correctly?

    That’s correct.

    And I’ve just tested again. I disabled TinyMCE Advanced and created a new page using the text editor which displays a one-line tool menu. I wrote a title and typed % in the text area.

    On saving the page it closes and a new page is displayed with the “406 Not Acceptable” message. When coming back to the editor page the title and the text have been deleted.

    So it seems TinyMCE Advanced is not the cause

    Wordpress has recently been updated to the 4.6.1–fr_FR version, but the problem existed before. I don’t know if it can be linked to the coding of accented characters in the French language but I found no mention of it in French-speaking WordPress forums.

    In reply to: TinyMCE 100% bug : Not acceptable


    I did carefully everything you said. I used Firefox and Chrome.

    The problem was the same with the twentysixteen theme, it was the same when all plugins were disabled, it was still there after I turned the plugins back on and disabled Tinymce and tried again.

    The version of TinyMCE Advanced is 4.4.1

    The problem appears whatever the location of the % symbol in a Post or a Page : title and text.

    As I don’t work with statistics it’s not a crucial problem…

    Thank you for your help. I suppose somebody somewhere should be informed, even if I represent only 0.0…01% WordPress users!

Viewing 10 posts - 11 through 20 (of 21 total)