• Update 3.0.5 of the nice Magazine Basic theme published in august 2015 proves to be child unfriendly.
    After installing this update I was confronted with as series of fatal errors so I will be forced to recode the child as well. This is not the idea behind using a child to make adaptations to a theme.
    At the moment I am still working on the adaptation of Compact Magazine. This Magazine Basic Child can be seen in use at Bootjesgek.nl.

    First thing I found is unnecessary renaming functions called mb to bavotasan:
    mb_theme_options( ‘excerpt_content’ ) into:
    $bavotasan_theme_options[‘excerpt_content’]
    But this is not the last. At this moment I wonder if it be a good idea to solve these problems by recoding the child or wait for Bavota to withdraw this update?
    You can follow me at: 124media.wordpress.com

Viewing 3 replies - 1 through 3 (of 3 total)
  • Theme Author bandicootmarketing

    (@tinkerpriest)

    The latest version of MB required an update to namespacing and the core framework to make sure it was compatible with the Customizer, which is now required by WP.org.

    The update will cause some issues with any child theme that might still be using the old namespacing, but in the long run, this version will present fewer issues moving forward.

    For those of us using child themes, what do we need to modify to resolve these issues? It would be helpful to know.

    Thread Starter McCage

    (@mccage)

    Dear Bavota,
    Thanks for the quick response. I understand you made a study of the complicated issues of name spacing and core framework.
    Maybe you could help us out by publication of a list of changes that were made in the MB parent referring to these aspects.
    I agree with lutetia; after all we are not all experienced theme developers. Some of us use a MB child to power only one website.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Magazine Basic Update not child friendly’ is closed to new replies.