Bowo

@systmuk the ability to remove admin bar items from other plugins is available in the Pro version of ASE: https://www.wpase.com/features/

@dleigh Great to hear that. Looks like a fluke indeed.

If DLM has been useful in developing your sites, please kindly consider leaving a quick review for it at https://wordpress.org/plugins/debug-log-manager/#reviews. Thank you.

@photoman6300 I see that you’re using the Pro version of ASE. This wp.org forum is strictly limited for supporting the free version of ASE per the forum’s guidelines. Please login to your account dashboard and open a support ticket there. Thank you.

@dids-wp thank you for the suggestion. This is well-noted for now.

Do you / does your site have a lot of drafts at any given moment?… I’m trying to understand your use case.

@ric11212 this is a known issue with menu items that contains a counter, e.g. ‘Updates’ and ‘Comments’. Admin Menu Organizer currently strips them out.

@stanfordgriffith thank you for reporting this. Another user reported a similar issue recently. I’ve taken a closer and deeper look. This comes down to how the Divi Builder is adding the “Edit wtih Divi” action link.

In /divi-builder/includes/builder/feature/BlockEditorIntegration.php on line 420-477, they have this function that adds the edit link.

public function add_edit_link( $actions, $post ) {
    // Maybe change this with et_fb_current_user_can_save or equivalent.

    if ( ! $this->_can_edit_post( $post ) || ! et_builder_enabled_for_post_type( $post->post_type ) ) {
        return $actions;
    }

    if ( (int) get_option( 'page_for_posts' ) === $post->ID ) {
        // Post is assigned as the blog page so it does not have editable content.
        return $actions;
    }

    $post_id         = $post->ID;
    $is_divi_library = 'et_pb_layout' === get_post_type( $post_id );
    $edit_url        = $is_divi_library ? get_edit_post_link( $post_id, 'raw' ) : get_permalink( $post_id );

    if ( et_pb_is_pagebuilder_used( $post_id ) ) {
        $edit_url = et_fb_get_vb_url( $edit_url );
    } else {
        if ( ! et_pb_is_allowed( 'divi_builder_control' ) ) {
            // Do not add Divi activation link when user lacks Toggle Divi Builder capability.
            return $actions;
        }
        $edit_url = add_query_arg(
            array(
                'et_fb_activation_nonce' => wp_create_nonce( 'et_fb_activation_nonce_' . $post_id ),
            ),
            $edit_url
        );
    }

    $edit_action = array(
        'divi' => sprintf(
            '<a href="%s" aria-label="%s">%s</a>',
            esc_url( $edit_url ),
            esc_attr(
                sprintf(
                    __( 'Edit &#8220;%s&#8221; in Divi', 'et_builder' ),
                    _draft_or_post_title( $post->ID )
                )
            ),
            esc_html__( 'Edit With Divi', 'et_builder' )
        ),
    );

    $actions = array_merge( $actions, $edit_action );

    // I'm leaving this here in case we wanna change item position.
    // $edit_offset = array_search( 'edit', array_keys( $actions ), true );
    // $actions     = array_merge(
    // array_slice( $actions, 0, $edit_offset + 1 ),
    // $edit_action,
    // array_slice( $actions, $edit_offset + 1 )
    // );.

    return $actions;

}

The first check in that function is:

$this->_can_edit_post( $post )

Which is this function on line 43-54 in the same file:

protected function _can_edit_post( $post ) {
    if ( function_exists( 'gutenberg_can_edit_post' ) ) {
        return gutenberg_can_edit_post( $post );
    }

    // In case WordPress is lower than version 5.0.
    if ( ! function_exists( 'use_block_editor_for_post' ) ) {
        return false;
    }

    return use_block_editor_for_post( $post );
}

It basically checks if a post can be edited with the block editor, if it can, the function will return false, which in turn, inside add_edit_link() will cause the function to stop early without adding the “Edit with Divi” link.

So, this is not an issue caused by ASE’s Disable Gutenberg module, or any other plugin that does a similar feature, even Divi Builder’s own “Settings >> Advanced >> Enable Classic Editor”. If a post can be edited with the block editor, the “Edit with Divi” link simply won’t appear.

I’m guessing it’s because the Divi Builder has a frontend editor, which mau cause issue with Gutenberg, that also performs a sort of “frontend editor” interface.

I sugges reporting this to Divi Builder and see what they have to say about it. Feel free to reference this thread.

@edviser thank you for the detailed analysis.

You are correct that when “Disable Smaller Components” is enabled, and “Disable the plugin and theme editor” is unchecked, ASE will try to restore DISALLOW_FILE_EDIT to false, in other words, enable PHP editing of plugins and themes, which is the default state on a fresh WordPress install. The priority for this action is set to PHP_INT_MAX (the latest to be executed on the admin_init hook.

In general, a conflict can happen if you enable a(ny) similar feature in another plugin. In your case, I simply advise to use the feature available in ASE. If more users have a similar feedback as yours, I may consider modifying how ASE works, i.e. when “Disable the plugin and theme editor” is unchecked, do not attempt to re-enable the plugin and theme editor like on a fresh WordPress install.

@ellegaarddk Thanks for the suggestion. This looks like a good fit for ASE. Certainly well-noted for now.