Not for Gutenberg yet

  • alittlebitoffiddle

    (@alittlebitoffiddle)


    7 years, 5 months ago

    Unfortunately I’ll have to look for other calendar resources. This does not work with my Gutenberg website anymore. Hoping this will change. I’ll go back to it then.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Yale Wishnick

    (@yale-wishnick)

    7 years, 5 months ago

    How can you say it is a great calendar when it does not work with WP 5

    What product are you using

    ywishnick@gmail.com

    Benjamin

    (@bsokic)

    7 years, 4 months ago

    Hi @alittlebitoffiddle,

    I’m sorry to hear that you’ve had a issue with our plugin. Our plugin is tested and compatible with the latest WordPress version 5.0.2, and so far we have not found any issue between our plugin and Gutenberg editor.

    Gutenberg was officially released as part of WordPress 5.0, so you should now see the new block editor by default if you have upgraded your WP installation.

    Please check again if everything is fine if you decide to continue using our plugin, or create a topic at wp.org and we will be happy to help if there is still a problem in your installation.

    Best regards,
    Ben

    • This reply was modified 7 years, 4 months ago by Benjamin.
    • This reply was modified 7 years, 4 months ago by Benjamin.
    takeok

    (@takeok)

    7 years, 2 months ago

    Similar issue here. With the latest version of this plugin enabled on WordPress 5.0.3 using a virgin copy of the Twenty Nineteen theme with NO OTHER PLUGINS enabled (only the Timely plugin) the site becomes completely unresponsive. The site appears to be getting hung up attempting to load the plugin’s Stylesheet. The Stylesheet never loads. I’ve deleted the plugin and reinstalled a fresh copy from the WordPress Dashboard and the issue persists.

    http://181.224.137.216/~yogahear/wp-content/plugins/all-in-one-event-calendar/public/themes-ai1ec/vortex/css/ai1ec_parsed_css.css?ver=2.5.36

    takeok

    (@takeok)

    7 years, 2 months ago

    Sorry it was a SiteGround issue with the domain mapping to a temp URL with an IP address (which has since changed) instead of the proper site domain.

    • This reply was modified 7 years, 2 months ago by takeok.
    • This reply was modified 7 years, 2 months ago by takeok.
    takeok

    (@takeok)

    7 years, 2 months ago

    [deleted]

    • This reply was modified 7 years, 2 months ago by takeok.
Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Not for Gutenberg yet’ is closed to new replies.