Changes between Version 2 and Version 3 of Ticket #17447, comment 47
- Timestamp:
- 09/17/2015 02:42:44 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17447, comment 47
v2 v3 4 4 > Professional programmers offer solutions to clients. Clients don't dictate specific modifications to `register_post_type()`. 5 5 6 Of course not. But sometimes the best and most performant way to offer a specific solution wouldbe through this hook acting on builtins.6 Of course not. But sometimes the best and most performant way to offer a specific solution might be through this hook acting on builtins. 7 7 8 8 > What other things to do you want to change, specifically? … … 12 12 A big reason to do this is to change values before the values trigger code to be run whose results have to be reverted. The code that ends up getting called that needs to be reverted at time includes calls to `add_rewrite_rule()`, `add_permastruct()` and `register_taxonomy_for_object_type()`. Unraveling those functions after the fact, especially the first two, is a PITA and introduces potential bugs if you don't get it correct. 13 13 14 Also, for example, being able to add a property ''(i.e. `'x_newclarity'` named with `'x'` for extension and the rest after mycompany name)'' to the post type array that would get passed around with the return value of `get_post_type_object()` so we can be sure it is always there. This would allow a developer to add, for example, metadata about generating reports for a post type or metadata for columns in the admin or metadata for customized export.14 Also, for example, being able to add a property ''(i.e. `'x_newclarity'` named with `'x'` for extension and the rest after our company name)'' to the post type array that would get passed around with the return value of `get_post_type_object()` so we can be sure it is always there. This would allow a developer to add, for example, metadata about generating reports for a post type or metadata for columns in the admin or metadata for customized export. 15 15 16 16 > If your use cases are vague, then they aren't an emergency.