WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #10142, comment 125


Ignore:
Timestamp:
09/04/2015 07:51:08 AM (4 years ago)
Author:
flixos90
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10142, comment 125

    v2 v3  
    77> In first case I needed name of color and slug based on name, that was obvious, but I also needed place for storing HEX value of color. And what with "Black and white" and "multicolor"? Second case was much more complex, with dedicated importer from corpo CRMs (50+ products, 50000+ outposts), each outpost and product with UID (different between each database and another database with mappings, independent imports from each database, nice mess). CPT was obvious choice for outposts and taxes for products, but I needed place for storing UIDs. Few months later had to be made import with product before debut on the market, so I needed also an option to show only products already on stock.
    88
    9 I guess it depends on the way you see posts vs terms. As I mentioned above, I would have created `Color` and `Product` as post types being, adding a dropdown of all `colors` as a meta field for the `paintings` post type and a dropdown of all `products` to the `outpost` post type to create the relationships.
     9I guess it depends on the way you see posts vs terms. As I mentioned above, I would have created `Color` and `Product` as post types, adding a dropdown of all `colors` as a meta field for the `paintings` post type and a dropdown of all `products` to the `outpost` post type to create the relationships.
    1010
    1111> Name, title and description is enough if you're seeing WordPress only as blogging CMS, but I've done on top of it blogs, large companies sites, shops, two social apps, and two dedicated CRMs. I love flexibility and scalability of WP with CPT, but taxonomies in row with user management are last two things wasn't that flexible like the rest, it hurts sometimes...