The CPT slug “question” is bad coding style.

  • vovastik

    (@vovastik)


    1 year ago

    The CPT slug “question” is bad coding style.
    A unique name should have been created.
    You should fix this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    1 year ago

    Thanks for your feedback. The WPSSO Core plugin actually matches the CPT with a Schema type if one is available, so the “question” CPT matches the “question” Schema type. This is true for all other CPTs that a user or other plugin may create for their content, like “event”, “recipe”, etc.

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    1 year ago

    FYI, another example of using a non-plugin specific CPT or CF name for interoperability is the WooCommerce “product” CPT and “rating” CF names, which are both used by several plugins, making it easier to support content across different plugins.

    js.

    Thread Starter vovastik

    (@vovastik)

    1 year ago

    From your answer it seems that WPSSO FAQ should work fine with AnsPress, that’s literally what it’s designed for.
    But the CPT “question” from WPSSO FAQ has no tags, while the CPT “question” from AnsPress has tags. As a result, when these two plugins are together, it is impossible to use question tags. What to do?
    At least spare us from WPSSO Core errors. I can stop using WPSSO FAQ, but I can’t stop using AnsPress because AnsPress is the core of several of my projects. Right now the WPSSO FAQ is preventing me from buying additional licenses for my favorite WPSSO Core Premium plugin.

    P.S.
    Non-unique naming is a dead end. Proven by Bootstrap.

    • This reply was modified 1 year ago by vovastik.
Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘The CPT slug “question” is bad coding style.’ is closed to new replies.