• Resolved jasko40

    (@jsko40)


    Updating to 6.6 caused all links to be immediately underlined on a staging divi themed site.

    To cover questions you might have, after the WP 6.6 update: (a couple standard steps were done)

    • I did clear all plugin caches (siteground host plugin and in hosting account, & browser).
    • I did resave Permalinks.
    • I did a quick search and it seems this was maybe a similar issue after the 6.1 update over a year back to some other themes. They proposed a temporary workaround then of adding the following CSS:

    a:where(:not(.wp-element-button)) {
    text-decoration: none;
    }

    However, when I tried that it did not correct, and I also got an expected Rparen error flagged by wordpress in the divi options css area.

    I used browser tools to check a couple of the links and they indeed do instead show something similar causing underlines (on line28, it says):

    :root :where(a:where(:not(.wp-element-button))) {
    text-decoration: underline;
    }

    So, I added the following near the top in my themes optional css area:

    :root :where(a:where(:not(.wp-element-button))) {
    text-decoration: none;
    }

    This cleared the underline issue. This also repeats the flagged red mark/error about expected Rparen error. (I don’t understand this error yet) However, leaving it in the CSS with the error as such it appears to have fixed the underlining at least. So, great! But does anyone think this means I still have something wrong with this staging site, or is this a WordPress version update issue, or more likely a divi theme issue I should speak to them about? Also, if anyone is even familiar with expected Rparen error…that I’m just riding with at the moment, that might help. Thanks.


    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 33 total)
  • Moderator t-p

    (@t-p)

    This may be a plugin or theme conflict. Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.

    If you can install plugins, install and activate “Health Check”: https://www.ads-software.com/plugins/health-check/
    It will add some additional features under the menu item under Tools > Site Health.
    On its troubleshooting tab, you can Enable Troubleshooting Mode. This will disable all plugins, switch to a standard WordPress theme (if available), allow you to turn your plugins on and off and switch between themes, without affecting normal visitors to your site. This allows you to test for various compatibility issues.
    There’s a more detailed description about how to use the Health Check plugin and its Troubleshooting Mode at https://make.www.ads-software.com/support/handbook/appendix/troubleshooting-using-the-health-check/

    Tonya Mork

    (@hellofromtonya)

    Hello,

    Thank you for your report. This issue is reported and known in WordPress Core Trac https://core.trac.www.ads-software.com/ticket/61660. This issue appears to be fixed in Gutenberg and is planned for 6.6.1. I invite you to track and, if you’re interested, help test in the Trac ticket.

    • This reply was modified 4 months, 1 week ago by Tonya Mork. Reason: fixed typo

    I am also face same issue on divi theme. How can I solve it?

    Same issue here. Did update all plugins, did not fix it. Did disable all plugins, did also not fix it.

    So this must be something in the update that is causing this. Someone found a fix?

    Did contact Divi team and they have a Temp fix for this:

    As a temporary fix, add the following code to the?Custom CSS?field under WP Dashboard > Divi > Theme Options:

    :root :where(a:where(:not(.wp-block-navigation))),:root :where(a:where(:not(.wp-element-button))) {text-decoration: initial !important;}

    I am using the Twenty Twenty-Four theme. The links were fine for me with Blue & underline. After upgrade to 6.6, all link were black & underlined. I added CSS to change the color. Some changed, some did not. Seems random. Asking for support I was told my PHP was corrupt. All link colors are flaky.

    All help much appreciated.

    Tonya Mork

    (@hellofromtonya)

    Hello @rdiebel @hoenens @sishorif @jsko40,

    The issue has been reported and is being tracked in this WordPress Core Trac ticket https://core.trac.www.ads-software.com/ticket/61660. A fix is identified and ready for testing.

    If possible, appreciate you testing the fix (which is available in plugin format) and giving feedback if it resolves the issue you’re experiencing. How? Details are found here https://core.trac.www.ads-software.com/ticket/61660#comment:16.

    I have 110 sites I manage, so adding the code is problematic, especially since it will need to be removed once 6.6.1 is pushed out. What is the ETA for the version release?

    • This reply was modified 4 months, 1 week ago by daphnetalbot.
    Tonya Mork

    (@hellofromtonya)

    Hello @daphnetalbot,

    What is the ETA for the version release?

    The status right now: need to validate the proposed fix before scheduling 6.6.1 release. Why? To ensure the fix does indeed resolve the issue and without side effects.

    A good way to find out is to test the fix on affected sites. A test plugin is available with the proposed fix. It’s a plugin that can be downloaded, unzipped, and installed/activated on an affected site. Then when done testing, it can be removed from the site.

    Are you able to test the fix (which is an installable plugin) on one or more of the sites you manage? Details are here:

    If possible, appreciate you testing the fix (which is available in plugin format) and giving feedback if it resolves the issue you’re experiencing. How? Details are found here?https://core.trac.www.ads-software.com/ticket/61660#comment:16.

    I am a one-woman operation and do not have the time to help you with the test or install/uninstall temporary fixes. I would like to know an estimated ETA for the 6.6.1 release. Is there a guestimate on that?

    Also seeing this everywhere. When is a release for 6.6.1 planned? I can’t believe it’s been nearly 24 hours and the most popular CMS in the world has yet to release a fix.

    Tonya Mork

    (@hellofromtonya)

    I appreciate your frustrations.

    The pause in releasing the proposed fix in 6.6.1 is due needing feedback. Need to know if the proposed fix does indeed fix the issue on affected sites.

    This where folks affected by the issue can help. That said, I appreciate that not everyone affected is able to help test it (for whatever reason).

    Thank you reporting the issue and for your patience.

    Thread Starter jasko40

    (@jsko40)

    Before testing 18.5.0-rc.1 , all text links, button links with text in them, and menu links were all underlined. I would show more images of the before and after plugin test, but this forum editor makes it insanely difficult to simply add an image where you would want it. So I won’t bother for now. Please excuse random empty image boxes in this update.

    I was able to test the supplied Gutenburg plugin test (vers 18.5.0-rc.1). After install the underlining issue appears to be fixed! I’m also not currently noticing any new problems created by it yet.

    WordPress does say there is the 18.8.0 version of the plugin available. Should I also upgrade to that and test that? Or just go ahead and wait until wordpress 6.6.1 is available since I don’t typically have a separate Gutenburg installed? I can also utilize the workaround css supplied by Divi until then.



    This is what WordPress upgrades area currently shows with the 18.5.0-rc1 installed.

    …example view from a simple side menu list that no longer has the offending underlines.

    So both the workaround from divi using CSS or Gutenburg test plugin each work for now.

    The css temporary fix from divi (shown below) was removed and the underlining came back before the plugin test:
    :root :where(a:where(:not(.wp-block-navigation))),:root :where(a:where(:not(.wp-element-button))) {
    text-decoration: initial !important;
    }

    Great there are fixes. We are hosting over 400 sites. A plugin or CSS temporary workaround is not practical. I hope that the WordPress team are able to release a 6.6.1 patch within 24 hours of releasing 6.6. I find it very suprising that a bug as basic as this wasn’t picked up during pre-release testing.

    Tonya Mork

    (@hellofromtonya)

    I was able to test the supplied Gutenburg plugin test (vers 18.5.0-rc.1). After install the underlining issue?appears to be fixed!?I’m also not currently noticing any new problems created by it yet.

    That’s great news @jsko40. Thank you for testing the proposed fix ??

    Also, I added your test report to the WordPress Core Trac ticket.

    WordPress does say there is the 18.8.0 version of the plugin available. Should I also upgrade to that and test that? Or just go ahead and wait until wordpress 6.6.1 is available since I don’t typically have a separate Gutenburg installed? I can also utilize the workaround css supplied by Divi until then.

    Until 6.6.1 is released, you can choose the option that works best for you: upgrade to the newest version of the Gutenberg plugin, use the Divi workaround, or wait for 6.6.1. If not upgrading the plugin, it can be deactivated and removed from site.

Viewing 15 replies - 1 through 15 (of 33 total)
  • You must be logged in to reply to this topic.