- This topic has 4 replies, 3 voices, and was last updated 4 years, 3 months ago by .
- The forum ‘General Discussion’ is closed to new topics and replies.
These forums are for general discussion on WordPress and Genesis. Official support for StudioPress themes is offered exclusively at My StudioPress. Responses in this forum are not guaranteed. Please note that this forum will require a new username, separate from the one used for My.StudioPress.
I've been using Genesis for at least 10 years, and many of my older customer sites are still functioning with old themes named Pixel Happy and Back Country. Recently I tried to update Genesis to 3.x on a site using the Back Country child theme (she was still running Genesis 2.x), and the site got really wonky. It was as if none of the custom CSS in the child theme was being read. I wound up restoring her version of Genesis back to an older version, but of course we'd like to stay current. What is the best approach to take for updating other sites who also use these very old themes? Is there no solution but to change the underlying theme to a new one? (I use Dynamik by Cobalt Apps as my child theme of choice now.) I've trained my customers to always keep things updated so I know I'm going to hear about similar breaks on other sites over the next few months. Thanks for any tips.
If those are XHTML sites, they won't work with Genesis 3.x. The new version only supports HTML5 themes.
Also, if you were able to update and the CSS disappeared, it's possible the child theme is loading the parent Genesis theme. There is no longer a style sheet provided with Genesis.
Hi Victor, thanks for your reply.
I don't know if those older themes are XHTML-based. I purchased them from StudioPress. Some names are Pixel Happy, Pretty Young Thing and Back Country, all dating back at least 6+ years, some probably 10 years old now.
So basically it sounds as if I should warn customers that if they update, as I've taught them to always do, things are going to look wonky and they're going to need my help to bail them out. Have a feeling there are going to be some unhappy customers!
Use your browser's inspection tool and look at the HTML. The very first line will tell you if they're HTML or not.
If they are XHTML, the upgrade to the Genesis Framework isn't even offered.
I'm in a similar situation: Executive 2.0 (XHTML, not Pro) theme with Genesis 2.10.1.
I want to upgrade to Genesis 3.x which requires an HTML5 theme so it seems I must upgrade to Executive Pro (HTML5).
Any guidance or best practices in upgrading from Executive 2.0 to Executive Pro?
© 2023 WPEngine, Inc.