Typically in the software world “Release Candidate” means it’s what will be shipping. At most there may be some bugs discovered that will be fixed, but nothing major will change.
Apparently it’s piss off your customers week in the WordPress theme universe because StudioPress just dropped Genesis 2.0 final and it’s got all sorts of breaking changes from the betas and both release candidates. WTH?
(note: if you weren’t using the betas or release candidates, these change don’t affect you)
First off the obvious one is that how you enable HTML5 markup has changed from:
add_theme_support( 'genesis-html5' );
add_theme_support( 'html5' );
Ok, well that’s annoying as it breaks things as your site reverts to old markup which your updated CSS won’t recognize, but it’s a quick fix. Perhaps they COULD have included checking for either htm5 or genesis-htm5 in the genesis_html5() function, but they didn’t. They seem to have decided “it was only a release candidate” we can break against it.
But WAIT that’s not all! (In my best as seen on TV voice)
So what these means practically is that if you had been removing this actions with:
remove_action( ‘genesis_entry_header’, ‘genesis_post_info’;
Now you must specify a priority to match
remove_action( ‘genesis_entry_header’, ‘genesis_post_info’, 12 );
IMHO, It was a LOT easier before when you didn’t need to worry about the priorities. All the default actions were hooked to the default priority of 10 and you could move them if you wanted.
The same goes for:
remove_action( ‘genesis_entry_header’, ‘genesis_do_post_format_image’, 4 );
remove_action( ‘genesis_entry_content’, ‘genesis_do_post_image’, 8 );
remove_action( ‘genesis_entry_content’, ‘genesis_do_post_content_nav’, 12 );
remove_action( ‘genesis_entry_content’, ‘genesis_do_post_permalink, 14 );
remove_action( ‘genesis_after_entry’, ‘genesis_do_author_box_single’, 8 );
With breaking changes like this, I’d assume there are more, I’ll add them here as I find them and fix them 🙁