[GeorgeSmith]

Thanks for sharing the solution. I had seen similar heading styling issues before, and it is helpful to know that setting the background to none for the affected heading elements can resolve the problem.

The CSS below should be useful for anyone experiencing the same issue:

.entry-content h2,
.entry-content h3,
.entry-content h4,
.entry-content h5 {
background: none;
}

It is also good that the solution has been posted here for future users who encounter the same issue after a theme or WordPress update.

Make reply private: No

Website: famousstages.com

[GeorgeSmith]

Thanks for sharing the solution! This is a useful fix for anyone experiencing the same heading underline issue.

The .entry-content selector is important here because applying text-decoration: none to the headings alone may not override the styling responsible for the visual effect. Using:

.entry-content h2, .entry-content h3, .entry-content h4, .entry-content h5 { background: none; }

should remove the unwanted styling in the affected content areas.

It would also be great if future theme updates included a simple setting to enable or disable heading underlines, especially for sites where headings aren’t intended to look like links.

Website: softileo.com

[GeorgeSmith]

For this type of migration, Esotera could be worth testing, especially if the main goals are easier WordPress management and improved performance. However, the theme alone won’t guarantee better Core Web Vitals.

I would first create a staging version of the site and compare the current Webflow performance with the WordPress setup. Pay particular attention to image optimization, font loading, JavaScript, plugin usage, caching, and mobile performance.

Since maintaining the existing look and user trust is important, I’d also recommend recreating the key pages carefully and testing the staging site before making the switch. A lightweight theme combined with a well-optimized WordPress setup can provide a solid foundation for both performance and easier editing.

Website: softileo.com

[GeorgeSmith]

Thanks for the detailed clarification, Zed. It’s reassuring to know that the XSS issue was addressed in the updated classic themes. For anyone still seeing security warnings, checking that they’re running at least the patched versions—Mantra 3.3.3, Parabola 2.4.2, Tempera 1.8.3, or Nirvana 1.6.4—seems like the best first step. Keeping WordPress and themes updated is definitely important for avoiding outdated vulnerability alerts.

Website: softileo.com

[Author]

Posts