4 ms·

This functionality should become part of wp-core. Currently you need a plugin like CCTM, Types, Pods or ACF to upgrade WP from a blogger platform into a general

by cies 11y ago

This functionality should become part of wp-core. Currently you need a plugin like CCTM, Types, Pods or ACF to upgrade WP from a blogger platform into a general purpose CMS. Once part of wp-core it opens the road for plugins to extend on this functionality much easier, since all can depend on it being there.

jawngee 11y ago
Custom post type are part of the core though, there's just no admin UI for it. That's really all these plugins provide. https://codex.wordpress.org/Post_Types https://codex.wordpress.org/Post_Types You should be defining them in your theme anyways for source control.
- AustinG08 11y ago
  Exactly. It already is a general purpose CMS just by having the Page post type as well as the Post post type. I think it arguably is a great CMS for it's custom post type capabilities. I love me some WordPress.
- cies 11y ago
  I stand corrected. Still I think many other CMSes have this functionality in core and thus allow plugins to extend on it.
- CM30 11y ago
  No, you should be defining custom post types in a custom plugin for source control. That way, your code still works if they change theme, or you replace it when you remake the theme a few years down the line. Otherwise the client will inevitably switch theme, then find all their custom content inaccessible. And I do think even though this API exists, it should definitely be improved upon and given a built in interface. I mean, don't other CMS scripts like Drupal provide a way to add custom fields and things in core, via a visual interface?
  - jawngee 11y ago
    Yes, you should because dealing with keeping that in sync between dev, staging, production is a major hassle. If you are changing your theme and using custom post types, you still have to modify the theme to support the custom post types. So copy and paste, or isolate the custom post types to a separate file and include in your functions.php. If you're doing it any other way, then you honestly don't really know what you are doing.
    - joeguilmette 11y ago
      There are pros and cons for both methods. Personally, I much prefer to put functionality in a plugin and the theme limited to the frontend presentation. To suggest that I don't know what I'm doing is, well... Incorrect. Syncing production, staging, and dev is an unrelated and solved problem.
    - CM30 11y ago
      Not really. If you're not running a test site, put the theme and custom plugins inside another folder and commit that to Git or SVN. If you are running a test site, oommit the wp-content folder, with the uploads directory and any third party code set as ignored. And the way I suggest is also what a lot of WordPress experts suggest, as seen here: http://justintadlock.com/archives/2013/09/14/why-custom-post-types-belong-in-plugins http://justintadlock.com/archives/2013/09/14/why-custom-post... http://www.wpbeginner.com/opinion/wordpress-custom-post-types-debate-functions-php-or-plugins/ http://www.wpbeginner.com/opinion/wordpress-custom-post-type... https://www.smashingmagazine.com/2012/11/complete-guide-custom-post-types/ https://www.smashingmagazine.com/2012/11/complete-guide-cust...
deleted 11y ago
[deleted]
mercer 11y ago
The CCK module for Drupal became part of core recently. I haven't used Drupal since that happened, but I'm very curious what the experience has been like. I recently bought the developer version of ACF and migrated a Drupal 6 site with many custom content types and fields to Wordpress. Quite a bit of work, but loads of fun to do. So far, I'm quite happy with the result, and I much prefer the simplicity and familiarity that it provides for the client (the content 'admin'), among other things. But the fact that ACF relies on one single developer makes me a bit nervous. I'd also love for it to become part of core...

by cies 11y ago

jawngee 11y ago

Custom post type are part of the core though, there's just no admin UI for it. That's really all these plugins provide. https://codex.wordpress.org/Post_Types https://codex.wordpress.org/Post_Types You should be defining them in your theme anyways for source control.

AustinG08 11y ago
Exactly. It already is a general purpose CMS just by having the Page post type as well as the Post post type. I think it arguably is a great CMS for it's custom post type capabilities. I love me some WordPress.
cies 11y ago
I stand corrected. Still I think many other CMSes have this functionality in core and thus allow plugins to extend on it.
CM30 11y ago
No, you should be defining custom post types in a custom plugin for source control. That way, your code still works if they change theme, or you replace it when you remake the theme a few years down the line. Otherwise the client will inevitably switch theme, then find all their custom content inaccessible. And I do think even though this API exists, it should definitely be improved upon and given a built in interface. I mean, don't other CMS scripts like Drupal provide a way to add custom fields and things in core, via a visual interface?
- jawngee 11y ago
  Yes, you should because dealing with keeping that in sync between dev, staging, production is a major hassle. If you are changing your theme and using custom post types, you still have to modify the theme to support the custom post types. So copy and paste, or isolate the custom post types to a separate file and include in your functions.php. If you're doing it any other way, then you honestly don't really know what you are doing.
  - joeguilmette 11y ago
    There are pros and cons for both methods. Personally, I much prefer to put functionality in a plugin and the theme limited to the frontend presentation. To suggest that I don't know what I'm doing is, well... Incorrect. Syncing production, staging, and dev is an unrelated and solved problem.
  - CM30 11y ago
    Not really. If you're not running a test site, put the theme and custom plugins inside another folder and commit that to Git or SVN. If you are running a test site, oommit the wp-content folder, with the uploads directory and any third party code set as ignored. And the way I suggest is also what a lot of WordPress experts suggest, as seen here: http://justintadlock.com/archives/2013/09/14/why-custom-post-types-belong-in-plugins http://justintadlock.com/archives/2013/09/14/why-custom-post... http://www.wpbeginner.com/opinion/wordpress-custom-post-types-debate-functions-php-or-plugins/ http://www.wpbeginner.com/opinion/wordpress-custom-post-type... https://www.smashingmagazine.com/2012/11/complete-guide-custom-post-types/ https://www.smashingmagazine.com/2012/11/complete-guide-cust...

deleted 11y ago

[deleted]

mercer 11y ago

The CCK module for Drupal became part of core recently. I haven't used Drupal since that happened, but I'm very curious what the experience has been like. I recently bought the developer version of ACF and migrated a Drupal 6 site with many custom content types and fields to Wordpress. Quite a bit of work, but loads of fun to do. So far, I'm quite happy with the result, and I much prefer the simplicity and familiarity that it provides for the client (the content 'admin'), among other things. But the fact that ACF relies on one single developer makes me a bit nervous. I'd also love for it to become part of core...