5 Comments

  1. Digamber

    I would just like to say – i like most of the new FSE features, i think it’s the first step in stepping out of Elementors shadow and i can see how gutenberg/blocks would be the go to page building experience for most users.

    As a developer it’s an exciting and scary time.

    What caught my eye in this article is “plugin developers too” .
    Would like to put my two cents in here – as the theme/block becomes the most dominant aspect of wordpress – more mature plugins that take advantage of templating will need to scramble to come up with a solution.

    Wondering if there are discussion regarding how plugins would overwrite / provide mechanisms to customize templates – WooCommerce Templating comes into mind for me. I would imaging they would struggle to convert everything into blocks – even if they are enthusiastic to do so.

    Report

  2. Eleonore Ubin

    Would suggest to read and contribute to “proposal for updated theme directory requirements”:

    https://make.wordpress.org/themes/2021/07/20/discussion-request-for-feedback-on-requirement-changes/

    Functionality and Features

    Do not include:
    * Custom post types
    * Custom blocks
    * Custom roles
    * Custom user contact methods
    * Custom mime types
    * Shortcodes
    * Functionality that is not related to design and presentation

    This might have quite some impact on future theme development if you can’t include own blocks etc.

    Report

    • Justin Tadlock

      All of those things, including blocks, have never been allowed in themes. Given that it has had little impact on theming in the past, I don’t think it will have much going forward.

      If most were allowed, users would lose their content or access to it, depending on the case, when they switched themes. This is one of the guidelines with the least amount of gray area.

      Report

      • Eleonore Ubin

        register_post_type() – 137 Themes
        wpdirectory.net/search/01FC6RCT7H68Y8YGAWS7867JWQ

        add_shortcode() – 1260 Themes
        wpdirectory.net/search/01FC6R858K9MYNC8W8TX1CZRZF

        Report

        • Justin Tadlock

          I should probably clarify that “have never” is really “almost have never”. Basically, they’ve been disallowed for almost the entirety of the Themes Team’s existence. There was a time before the team became formalized. There were also a few exceptions. Namely, shortcodes for use in templates (but not for content) were allowed for a while. Eventually, the team just banned them altogether because it was an increasingly uncommon use case. But, the team did take a hard stance against shortcode for use in content.

          There are a few “special cases” where CPTs were given an exception, especially in the early years. And, they did allow for other special cases, such as storing options as CPTs at one point. I’m absolutely certain a few disallowed cases slipped through the cracks.

          I didn’t feel it necessary to dive deep into the full decade-plus history and each exception since it’s not really relevant to what you brought up. I could, considering I was a team member for most of those years and a team rep/lead for a good portion of that.

          But, the point still stands. This is not some type of new rule. It has been the standard since the early days of the Themes Team once it formalized the initial guidelines.

          Nevertheless, your regex for those searches is not an exact match for using register_shortcode() and register_post_type(). There are far too many false-positives.

          Report

Comments are closed.

%d bloggers like this: