jasko40

Lindsay, Gutenberg’s block editor is included in WP now. So the only reason some are adding it as a plugin right now is as a test to repair the underline issue (I’m unsure if it fixes other items as well). They are using the plugin as a delivery system for updated files to test. Others can correct me if I’m wrong in describing it that way.

If you can’t wait for a new WP update fix, you could install the Gutenberg plugin for a temporary fix. But then after the wordpress update does become available you will just be deactivating and uninstalling the Gutenberg plugin. Hope that helps explain a little. If you do go this route, please report back here whether it helped fix the issue or not to help them further confirm this fix works, or not.

If your site is using Divi, there is a another option with a css workaround for now that you would then later delete once WP makes the update available. You can find that workaround listed in this topic but you need to place it in Divi’s Custom CSS under Theme Options, or in your own child theme css area.

The temporary css fix isn’t allowed to be published through the normal WP/Appearance/Customize/Additional CSS area. The Rparen error might stop it from being saved or published.

Thanks Tonya. I did just try the 18.8 Gutenburg update and it seems fine as well for my site/test. No underlining of links seen. I also tested creating a post and editing within blocks editor and really had no errors there either. I will likely remove the plugin and wait for the 6.6.1 update just to avoid forgetting a extra test plugin installed.

Although, I did notice that after adding either a list or image block, there is no small + symbol in the far right of editor just after your most recent block. My only choice was the large + icon for adding a new block in the top left of editor. This behaves differently for headings or paragraphs where after you add one of these blocks, that optional + symbol appears right after your new block at the bottom right to carryon adding new blocks. I can’t say whether this is something new with the test upgraded Gutenburg plugins or not. Just thought I would mention it. Nothing to do with our underlines issue we are talking about here.

Sounds like they are just waiting on confirming the fix from enough people so they don’t rush out another fix that might cause further troubles. Sounds reasonable to me at this point, however we feel about the bug getting through.

I’ve heard it normally suggested and warned to not rush out and install the next update on live sites immediately on release. But hosts managing wordpress these days seem to autoupdate them rather quickly. Seems they have a set it and forget it system going and don’t always recognize when a recent WP update might turn out to have issues and, maybe, be instead held back for a minute. I received notices last night and this morning from hosts about to update many sites to 6.6 automatically some time today unless I stopped them.

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;
}

Thank you Ethan/Jared. Your update does appear to resolve it. Fast work!

Same here. Same non-numeric value error line 176, top of admin, sometimes causing dashboard/update buttons to vanish.

Also trying to trash posts caused the same line 176 error, along with two others to pop on a white page. Had to back up a page. After backing up, refreshing the admin shows the post did trash.

Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/wpforms/includes/admin/class-am-notification.php:176) in …/wp-includes/pluggable.php on line 1251

Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/wpforms/includes/admin/class-am-notification.php:176) in …/wp-includes/pluggable.php on line 1254

Checking the cf7 items in Disable Rest API settings did work for us. We use that plugin for one site. Thank goodness for those willing to help in support forums by posting how they solved these. Thank you all.

Thank you!

Just a note, after installing WP-SpamShield 1.9.9.9.9, a GravityScan run on the site still reports the vulnerability and actually changed the priority from low to high. Not sure why. GravityScan is a site scanner from outside wordpress newly offered from WordFence. Yesterday was also my first use of that GravityScan, which initially pointed out the problem and caused me to find this support post and your plugin as a mitigation option. Thanks for doing what you do Scott!

• This reply was modified 7 years, 6 months ago by jasko40.

Soooo, WP 4.7.5 just came out and was auto installed as it had important security updates. But they didn’t bother to close the Host Header Injection in Password Reset issue?

• This reply was modified 7 years, 6 months ago by jasko40.
• This reply was modified 7 years, 6 months ago by jasko40.