Skip to content

UI of some built-in WordPress editors is broken when Slim Seo is active #216

Description

@jetcraft-io

Issue Description:

First of all, thank you for providing such a great plugin. I've been using it well. I'm reporting an issue that I've encountered below.

When Slim Seo is activated, there's an issue where the UI of some WordPress built-in editors gets broken/damaged.

This issue is not detected by PHP debugging. Based on my hypothesis, it seems to be caused by a specific file (located at the path below) which should normally be added on pages where a WordPress built-in editor is embedded. However, when Slim Seo is active, this file appears not to be loaded.

https://your-site-domain/wp-includes/css/editor.min.css?ver=6.7.2

To confirm this, I deactivated all other plugins. The issue was reproducible when only the page with the embedded WordPress built-in editor and the Slim Seo plugin were active. Therefore, I believe the cause is almost certain.

This issue does not occur on regular page or post writing screens, or on pages like those using Elementor's Text Editor Widget. This is likely because these pages already load the necessary style files at the WordPress core level.

However, the problem seems to occur on pages where plugins that load styles directly within the HTML source, as shown below, are active.

<div id="wp-kboard_content-wrap" class="wp-core-ui wp-editor-wrap tmce-active">
    <link rel='stylesheet' id='dashicons-css' href='https://your-site-domain/wp-includes/css/dashicons.min.css?ver=6.7.2' media='all' />
    **<link rel='stylesheet' id='editor-buttons-css' href='https://your-site-domain/wp-includes/css/editor.min.css?ver=6.7.2' media='all' />**
    <div id="wp-kboard_content-editor-tools" class="wp-editor-tools hide-if-no-js">
    </div>
</div>

It seems difficult to request the source code of plugins that load styles in the manner shown above to be fixed, because other SEO plugins do not cause such conflicts.

This issue appears to be relatively significant as it severely damages the visual appearance on the frontend. In fact, with this issue occurring, normal service was difficult, so I have temporarily switched to and activated another SEO plugin as a substitute.

I sincerely hope this issue can be resolved soon.

Image

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions