plugin: Dynamic CPT & Taxonomy Generator

[Rima1889]

This pull request adds a new WordPress plugin: Dynamic CPT & Taxonomy Generator.

Features:

• Create new Custom Post Types (CPTs) from the admin dashboard.
• Optionally add a taxonomy when creating a new CPT.
• Add a new taxonomy to an existing CPT.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

[fellyph]

Hi @Rima1889

The blueprint is broken:

BlueprintStepExecutionError

Plugin /wordpress/wp-content/plugins/https-github.com-WordPress-blueprints-trunk-at-blueprints-dynamic-cpt-and-tax-generator could not be activated - WordPress exited with exit code 0. Inspect the "debug" logs in the console for more details. Output headers: {
  "x-powered-by": [
    "PHP/8.3.30"
  ],
  "content-type": [
    "text/html; charset=UTF-8"
  ]
}

BlueprintStepExecutionError: Error when executing the blueprint step #2: Plugin /wordpress/wp-content/plugins/https-github.com-WordPress-blueprints-trunk-at-blueprints-dynamic-cpt-and-tax-generator could not be activated - WordPress exited with exit code 0. Inspect the "debug" logs in the console for more details. Output headers: {
  "x-powered-by": [
    "PHP/8.3.30"
  ],
  "content-type": [
    "text/html; charset=UTF-8"
  ]
}
    at Object.run (https://playground.wordpress.net/assets/optional/blueprint-editor-DrPs94WP.js:1391:816)
    at async Je0 (https://playground.wordpress.net/assets/optional/blueprint-editor-DrPs94WP.js:1396:1541)
    at async at0.bootPlayground (https://playground.wordpress.net/assets/optional/blueprint-editor-DrPs94WP.js:1396:4570)
    at async mR0 (https://playground.wordpress.net/assets/optional/blueprint-editor-DrPs94WP.js:1400:551)
    at async https://playground.wordpress.net/assets/main-CXiRHcWy.js:92:28920

[fellyph]

Thanks for the update. I pulled this PR locally and found why the Playground preview is still failing.

The blueprint itself is loaded from the PR commit, but the installPlugin step installs the plugin from https://github.com/WordPress/blueprints at ref: "trunk":

"pluginData": {
  "resource": "git:directory",
  "url": "https://github.com/WordPress/blueprints",
  "ref": "trunk",
  "refType": "branch",
  "path": "blueprints/dynamic-cpt-and-tax-generator"
}

That directory does not exist on trunk yet, so Playground cannot activate the plugin and reports the BlueprintStepExecutionError.

For the PR preview to work, the plugin resource needs to point at a ref that actually contains these files. For example, while this PR is open:

{
  "step": "installPlugin",
  "pluginData": {
    "resource": "git:directory",
    "url": "https://github.com/Rima1889/blueprints",
    "ref": "dynamic-cpt-and-tax-generator",
    "refType": "branch",
    "path": "blueprints/dynamic-cpt-and-tax-generator"
  },
  "options": {
    "activate": true,
    "targetFolderName": "dynamic-cpt-and-tax-generator"
  }
}

After the blueprint is merged, this can point back to WordPress/blueprints + trunk if that is the desired long-term source. The key fix is that the install source must include blueprints/dynamic-cpt-and-tax-generator at the selected ref.