Support » Plugin: Gutenberg » Backward Compatiblity for old plugin

  • dedanirungu

    (@dedanirungu)


    Most of plugin that I developed are not working and will need reworking.

    We usually develop custom type that uses description section to get detailed information on particular post. We have been using wordpress because it made every thing easier as shown on the image link below. (NOTE I am using WooCommerce for example)

    https://imgur.com/AO0eBN3

    The page looks very different after installing Gutenberg as shown below.

    https://imgur.com/ZFWES0r

    This is very confusing because we do not intend to submit a post but we are only adding product description. The Classic Editor had advantage of Keeping It Simple and Smart(KISS).

    Gutenberg should only be used on adding blog post and should not replace every area custom types are used. There should be an option to choose whether to use Gutenberg or not when developing custom types.

    Example: We have customs type for Job, Faqs and Testimonials. Why would I need Gutenberg when posting? The post description is usually one paragraph or two and does not require column,blocks etc.

    Suggestion: Let use use Gutenberg on submitting post, but on custom types let us allow the use of classic editor where it is needed.

    • This topic was modified 5 months ago by  dedanirungu. Reason: To describe to issue much better
Viewing 4 replies - 1 through 4 (of 4 total)
  • Mel Choyce

    (@melchoyce)

    Hey dedanirungu! Can you talk a bit more about your plugins and what they do? Maybe folks here can help you figure out a good path forward.

    dedanirungu

    (@dedanirungu)

    I developed a plugins that creates custom types for frequently used data type eg faqs, testimonials, our services etc.

    This custom types are then displayed with additional fields where by I can decide to have the title and description or remove them all together.

    On Gutenberg editor all the customization is not rendered and in some instances the layout is not what I would expect for a CMS. This is confusing my employees when using the CMS.

    This is very frustrating.

    Mel Choyce

    (@melchoyce)

    On Gutenberg editor all the customization is not rendered and in some instances the layout is not what I would expect for a CMS. This is confusing my employees when using the CMS.

    Would you be comfortable sharing some screenshots of how your plugins render in Gutenberg?

    dedanirungu

    (@dedanirungu)

    We usually develop custom type that uses description section to get detailed information on particular post. We have been using wordpress because it made every thing easier as shown on the image link below. (NOTE I am using WooCommerce for example)

    https://imgur.com/AO0eBN3

    The page looks very different after installing Gutenberg as shown below.

    https://imgur.com/ZFWES0r

    This is very confusing because we do not intend to submit a post but we are only adding product description. The Classic Editor had advantage of Keeping It Simple and Smart(KISS).

    Gutenberg should only be used on adding blog post and should not replace every area custom types are used. There should be an option to choose whether to use Gutenberg or not when developing custom types.

    Example: We have customs type for Job, Faqs and Testimonials. Why would I need Gutenberg when posting? The post description is usually one paragraph or two and does not require column,blocks etc.

    Suggestion: Let use use Gutenberg on submitting post, but on custom types let us allow the use of classic editor where it is needed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this review.