Skip to:

Re: Confusion over element class token changes in backeard-compat

Thanks Andy I’ll have a rummage for that in a while.

Can you clarify though, why the change? as it does make preserving child theme extended from original theme files all the more awkward. I’ll be a little more indifferent to this when I get time to properly start from scratch but for the moment have to live with extending from existing markup and styles.

I would also love a little reassurance from the Dev team that creating real themes not just skins based on existing files with mix of views and controllers. I say this only as I’m a little concerned by the decision to move the default theme into the plugin buddypress folder for ease of updating as this suggests that crucial files one may have rewritten or customized might actually be updated by newer versions and these updates will have to be identified and transposed to ones custom files.

I can understand the decision to work this way keeping default theme within an upgrade structure but worry slightly that it’s not perhaps the best route for those that do intend to spend a bit more time than simply skinning; then again perhaps buddypress is best suited to simply skinning with a few adjustments made through functions.php etc which I could live with actually but only if developers stopped trying to output naughty markup such as empty div elements used to provide clearing A COMPLETELY UNNECESSARY APPROACH AND WRONG on many counts ;-) (sorry needed to get that off my chest :) )

Skip to toolbar