Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • It sounds like you received a security warning about Gravity SMTP and removed the plugin.

    Just to clarify: this does not necessarily mean Wordfence “planted” anything or that the warning was fake. Gravity SMTP did have reported vulnerabilities in older versions, including versions up to 2.1.4.

    If you no longer use Gravity SMTP, removing it was a reasonable step. You may also want to:

    – make sure the plugin is fully deleted, not just deactivated
    – update all other plugins, themes, and WordPress core
    – check your site users for unknown admin accounts
    – rotate any SMTP/API credentials that may have been used with the plugin
    – review your security logs for unusual activity

    If you believe the plugin was installed without your permission, that would be a separate security concern. In that case, check who has admin access to the site and review recent plugin installation activity if logs are available.

    If caching has already been ruled out, then the next thing I’d check is whether the JavaScript required for the slider is actually being loaded and initialized for logged-out visitors.

    Since the slider came from an older Joomla/HTML site, it’s possible that:

    • The required JavaScript file is not loading on the front end.
    • A JavaScript error elsewhere on the page is preventing the slider from initializing.
    • The slider depends on a library (such as jQuery) that is not available when logged out.

    Could you check the browser console while viewing the page in a private/incognito window and let us know if any JavaScript errors appear?

    Also, if this is custom code added through an HTML block, please share the slider’s HTML and JavaScript so we can take a closer look.

    @kerfred If you prefer the appearance from earlier versions, you can achieve something very close to it with a small admin-side CSS customization. For example, the following code restores the previous visual relationship between the selected state and the focus ring:

    add_action( 'admin_enqueue_scripts', function () { 
    wp_add_inline_style(
    'wp-admin',
    '
    input[type="radio"]:checked {
    background: #fff !important;
    }

    input[type=radio]:checked::before {
    background-color: var(--wp-admin-theme-color) !important;
    }

    input[type="radio"]:focus {
    border-color: var(--wp-admin-theme-color) !important;
    box-shadow: 0 0 0 0px #fff, 0 0 0 1px var(--wp-admin-theme-color) !important;
    }
    '
    );
    } );

    This would be a site-specific customization rather than a change to WordPress core, but it may provide a suitable workaround if you prefer the pre-7.0 appearance.

    From what I can see, the radio button still shows both the selected state and the focus state, but the visual styling has changed in WordPress 7.0.

    In previous versions, the selected radio button had a blue center fill, a small circular white space around it, ad then the radio button border. The focus outline was very close to the border, which made it appear as part of the selected state.

    In WordPress 7.0, the selected state appears as a white center with blue around it and the radio button border. When the radio button receives focus, an additional blue focus ring is displayed outside the control with a small gap between the radio button and the ring.

    The focus ring disappears when focus moves elsewhere on the page, while the selected state remains. This is similar to the behavior in previous versions; the main difference is the updated visual design, which makes the focus indicator more distinct from the selected state.

    As for restoring the previous appearance, that would ultimately be a design decision for the WordPress project. At the moment, what you’re describing appears to be an intentional styling change rather than a functional regression.

    I’ve attached a screenshot to help illustrate the difference.

    version 6.9.4

    version 7.0

    Hi,

    This warning is usually caused by a Post Excerpt block being rendered without the expected excerptLength attribute being present.

    Could you provide some additional details?

    • What version of WordPress are you running?
    • Does the warning occur on the front end, in the editor, or both?
    • Are you using a custom theme or any plugins that modify Query Loop or Post Excerpt blocks?
    • If you switch temporarily to a default theme such as Twenty Twenty-Five, does the warning persist?

    Also, if possible, please share the full Site Health > Info > WordPress version information and the complete warning message from the log.

    That will help determine whether this is coming from WordPress core, a theme, or a plugin altering block attributes.

Viewing 5 replies - 1 through 5 (of 5 total)