For accessibility reasons, Wordpress 4.4 changes the HTML markup of the settings sections in an way that’s incompatible with our theme settings pages. As a result, our themes will fail to display the settings sections once you update to 4.4.
As you might know by now, themes in the official repository are no longer allowed to implement a theme options page. All new themes were required since early this year to implement support for the Customizer and some weeks ago this rule became mandatory for themes already published in the repository as well.
We’ve given this a great deal of thought and we decided not to transfer theme options to the Customizer interface. We built our themes settings to fit and work in a certain way and we feel the Customizer structure just isn’t right for them.
So Mantra 2.4.1 saw the light of day a couple of days ago and brought with it a couple of fixes, support for WordPress 4.1+ ‘title-tag’ and the addition of our social media links to the theme’s admin page.
However this release includes a small glitch concerning child themes so you may want to postpone the update until 188.8.131.52 becomes live.
It’s a time for joy and celebration, not just because a new Mantra update is here to correct and improve some long outstanding issues but also because this month, 4 years ago, our little Mantra opened its digital eyes and met with the Wordpress repository for the very first time. And boy what I ride it has been since…
Mantra is now 4 years old and although her little sisters are starting to surpass her, she’s still older, wiser and still has a few issues up her sleeves.
One of the most important changes in the latest update is the removal of shortcodes. The keep the [mantra] or [cryout] shortcodes working on your site, we’ve moved this functionality to a separate plugin…
Mantra receives a small maintenance update, tweaking and changing things here and there.
The most noteworthy thing related to the 2.3.3 update (but not part of the update itself) is the corrupt Mantra archive lurking around on Wordpress’ servers. One of its evil purposes is to leave your pages content-less (but be ready for other nasty surprises as well). The fix?