• rgomezp

    (@rgomezp)


    Hi, the custom notices I had working on previous versions of wordpress stopped working with the latest update to WordPress (with Gutenberg). They would appear on post update/publish. Any insights into this problem? Thanks

    • This topic was modified 6 years ago by rgomezp.
    • This topic was modified 6 years ago by rgomezp.
Viewing 3 replies - 1 through 3 (of 3 total)
  • I can confirm that set_transient() is not working anymore indeed.

    Thread Starter rgomezp

    (@rgomezp)

    @wpsolr do you happen to know why? and any potential work-arounds?

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    Transients appear to work fine for me. Note that transients are also part of the unit testing performed on every version of WordPress, so any breakage with them would be rather quickly noticed. Additionally, WordPress itself uses transients for a number of items, including updating, caching elements of themes, error displays, feeds, and the main wp-cron process.

    There’s nothing wrong with transients. They haven’t had any changes in years.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Notices Broke with WP5/Gutenberg’ is closed to new replies.