| 开发者 | amitworx |
|---|---|
| 更新时间 | 2026年8月18日 06:55 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
bbact_project identifies a post type in the database. Treat that key as permanent after content has been created. The public URL can be adjusted independently with the Frontend URL base field.
The plugin does not send data to external services and does not require an account.
Yes. You can manage both from the same dashboard and connect a taxonomy to one or more custom post types.
The URL slug is used when first creating a type and helps generate its internal key. The Frontend URL base controls the public permalink path. The Internal key is the WordPress identifier, for example bbact_project; it should remain unchanged after you create content.
Changing the URL slug can generate a new internal key. WordPress then treats it as a new post type, so posts associated with the old key are no longer shown in the new menu. Restore the original internal key to access that content again. To change only public URLs, use Frontend URL base instead.
The key is generated on first save so you can verify the intended slug before creation. Keep it stable after content exists, because WordPress uses it to associate posts, taxonomies, and metadata.
Save your permalink settings at Settings > Permalinks after changing a Frontend URL base. This refreshes WordPress rewrite rules.
Yes. Enable Show in REST for a custom post type or taxonomy to make it available to the block editor and REST API.
Not yet. The plugin is designed to grow toward custom-field management, but version 1.0.0 focuses on custom post types and taxonomies.
No. Deactivation does not delete posts, terms, or saved definitions. The registered types are inactive until the plugin is reactivated, so their content may not be accessible in the usual WordPress menus while it is inactive.
No. BBA Custom Types works entirely within your WordPress installation and does not require an account or third-party service.