Viewing 5 replies - 1 through 5 (of 5 total)
  • Just to second this, I’ve had the same issue and error (though I don’t know how to go back to an older version of the plugin).

    @emilymoran84 and @apessoa

    Terribly sorry about that… The code that’s running here should only be running on a LifterLMS post type but we have the conditional checking for that in the wrong place.

    We’ve logged the issue in our GitHub repository at https://github.com/gocodebox/lifterlms-blocks/issues/40

    You can follow along there if you want specific blow by blows or more information about the bug itself.

    I’m hoping to be able to get this fixed and resolved in a release by end of day but it may not be until tomorrow the way things are looking.

    Thanks for reporting this and thanks for your patience.

    For whatever it’s worth, if your custom post type *supports* custom fields I think this issue will go away. If you are able to modify that you could do so without having to wait on our next update to close the bug.

    Best,

    @emilymoran84 and @apessoa,

    Version 3.37.5 will fix this bug. Please have an upgrade and let me know if you have any other issues or questions.

    Best,

    @thomasplevy Thank you so much for the prompt response and fix! Things are back up and running now 🙂 Much appreciated!

    @emilymoran84

    Great to hear!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘last update breaks gutenberg’ is closed to new replies.