Are Appfinite themes Gen 2.0 compatible

Hi Wes,
Yup, I’ve been following these changes closely, and the README has been pulled out for 2.0. More on that stuff here.

Why this would happen is beyond me. I answer questions on the SP forum, and some questions would have been avoided altogether if people would have read that. Now that’s out. Gary’s not even a Studiopress employee, but thanks to him, some details emerge. The SP team are pretty silent about release details, changelogs, prices, etc. I don’t know if they’re understaffed or what. So I’m left to do my own code compares, or catch something on Twitter.

On a happier note, when I get some time between tasks, I will be sporting Epik on my own homepage, so I’m looking forward to that!

Dave

Wes,
I converted my own homepage to Epik 1.3 with Genesis 2.0 yesterday. It was the easiest time I’ve ever had changing the theme there. My own homepage is largely a landing page now, not too complex. But with so many fancy widgets available, I was expecting to do some careful organizing/thinking. Instead, things just fell into place. I did a few moves of items to different widgets. My responsive Portfolio Slider looked good right away. I added 2, count ’em 2 lines of CSS, and I was good to go! I played with all the color options, and I liked several, but went back to the default for now, which I think really looks great.

I’m extremely pleased!! I look forward to using this theme elsewhere too, on more complex sites. davidchu.net

Thanks!! Dave

Hey thanks for the optimal update to HTML 5 I bought it from the community area im a pro plus member at Studiopress
I was really glad I was included in your update for no fee.. you can count on a future purchase from me
Thanks because its this whole thing is just bigger than you know.. Its not easy to do that HTML 5 work around doable( I did do it once) sure but well thanks…
🙂

@dan You’re Welcome!

@dev77 Yes there was a major update. Basically it’s a new, completely redeveloped theme designed for Genesis 2.0/HTML5. So yes definitely backup your old files just in case. I wrote some basic info here about what you should do – https://appfinite.com/topic/optimal-1-3-for-genesis-2-0-html5-is-now-available/

Yeah I always recommend separating custom css as well. I personally think it’s much easier to manage.

Sorry for the late reply I’m currently busy working on updates and other projects for the site at the moment….which is why I haven’t been on the forums lately (in case anyone is wondering).

1. Your theme will still work with Genesis 2.0, you just need to make sure HTML5 is NOT enabled. By default it won’t be if you’re using an older theme. So you’ll still be able to use it as you can see here from the Developer himself – http://www.nathanrice.net/blog/genesis-loop-hooks/

“Note: if you’re using Genesis without HTML5 activated, all the old hooks and markup work as before. Genesis 2.0 is 100% backward compatible.”

Also check his comment on backward compatibility – http://www.nathanrice.net/blog/genesis-loop-hooks/#comment-2076

“At some point, not sure when, we’ll remove the backward compatibility and only offer auto-updates to people who are running a theme that supports HTML5. It’s just the way it has to be … we can’t litter the Genesis source code with conditionals for infinite backward compatibility forever. But before we do that, we’ll update all the StudioPress themes to work with HTML5, and will probably maintain the 2.0.x branch for a year or so with security updates, etc., so you’re not caught with an insecure version of Genesis.”

2. The old version should still work with Genesis 2.0. The new version of Optimal will only work with Genesis 2.0. There’s no reason to create a new version that works for an older version of the Genesis Framework since no one will be or should be using the old version of Genesis. It’s always recommended to use the latest version of Genesis even if you’re using an older child theme for security and many other reasons…..you probably already know this, but I’m sure others may be curious.