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.
To solve this…
The saddest moment in Nirvana’s life has come: the settings page – it’s gone! Due to higher forces that are beyond our control, the theme has just lost part of her soul.
However, do not panic. We have prepared for this moment and set up an alternative solution. As we have previously announced, we decided to retain the settings page functionality and move it to the separate Cryout Serious Theme Settings plugin.
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.
To be able to continue providing theme updates…
We don’t often send our themes to the doctor, but when we do we make sure they return all patched up. This is true for Nirvana 1.1.3 which returns so full of fixes and patches that one must wonder how it managed to function at all in the first place.
Well, the secret is that there’s so much functionality in Nirvana (and our other themes) that there’s bound to be something functional even when there’s so much that is buggy…
The good news is that Nirvana is now less buggy and you can enjoy the fixes listed in the changelog…
Tempera is tempted to read The Tempest but she’s been feeling very temperamental lately and blames it on the high temperature. She’ll hire a temp to do the reading for her while also massaging her temples in her underground Temple.
More temp stuff plus a a fresh changelog after the jump.
The Zombie Apocalypse is here! For the fifth year in a row… well not the actual apocalypse but your eponymous beloved, friendly, next door all bloody neighbour Wordpress theme.
Lost for a couple of days into the undead abyss of not-updated themes, we’ve put all coffee aside for a week and worked on bringing it back from the other side. This is version 2.0 of your favorite B-movie styled theme and a few things have changed but they’re all for the best…
Parabola learned from experience to circumvent her younger sisters’ critical mistakes and brings you only the desert in this round of themes updates.
Among the most important additions are support for WPML and Polylang multilingualism in custom content areas and her newly achieved skills in the commerce sector with the inclusion of the WooCommerce compatibility (child theme) code and styling. For everything else…
Tempera decided to spend her entire vacation going to summer school. The most important feature she brought back is support for WPML and Polylang multilingualism. You will now find all of Tempera’s custom text fields in Polylang’s translations section.
The second important change is the inclusion of the WooCommerce compatibility child theme code and styling. This should improve handling WooCommerce content, making the use of the separate child theme unnecessary. For the rest of the changes see the changelog…
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…
Wordpress’ Theme Review Team seems to always be involved in a lot of decision making. That’s good, decisions have to be made and a direction needs to be set and maintained.
However lately the decisions seem to be taken hastily, without analysing all the effects (and maybe consequences) they have. We’ve had scuffles with Wordpress before, but we’ve moved on, adapted, clarified or changed things. But this new decision directly affects themes – meaning it touches us the most.
