Breaking change for child themes in 3.6.8

  • Hi, I recently updated and noticed the mobile menu toggle wasn’t working in my child theme. After some digging, I found the reason why.

    In v3.6.8 you’ve changed where the mobile menu hooks in. It used to hook into wp_footer but now hooks into astra_footer. See here.

    Now, my child theme replaced the astra_footer entirely as I have no need for it, so the mobile menu was not being appended to the DOM at all. The theme was expecting it to remain hooked into wp_footer. I’m not sure you should rely on child theme authors to keep all of your custom hooks present in their templates.

    This is the second time I’ve had to fix something related to the mobile menu after performing an update – the last time being when you introduced the drop-down style and did not honour the existing fly-out menu preference on the site. I’m sure these changes have caused some frustration to many site owners and child theme authors.

Viewing 1 replies (of 1 total)

  • Hi @luboslives,

    First of all, we would like to say sorry for the inconvenience you may have because of this.

    We made the changes for better compatibility with WordPress v5.8. We promise that, in the future, will handle such breaking changes more carefully.

    Kind regards,
    Herman ??

Viewing 1 replies (of 1 total)
  • The topic ‘Breaking change for child themes in 3.6.8’ is closed to new replies.