Changes between Version 1 and Version 2 of Ticket #26946, comment 22
- Timestamp:
- 02/27/2014 08:12:19 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26946, comment 22
v1 v2 24 24 Regarding 2. above, here are the Top 10 reasons why IMO posts don't work well for Nav Menu Items, **in increasing order of importance** ''(Note: In general, I advocate people use posts rather than add tables, but experience has taught me that at least for Nav Menu Items, posts are not a good fit):'' 25 25 26 10. Posts have many fields that are simply not needed for Nav Menu Items, some being `to_ping`, `pinged`, `post_password`, `post_content`, `post_excerpt`, `post_date`, `guid`, and `post_mime`.26 10. Posts have many fields that are simply not needed for Nav Menu Items, some being `to_ping`, `pinged`, `post_password`, `post_content`, `post_excerpt`, `post_date`, `guid`, `post_mime` and others. 27 27 28 28 9. Nav Menu Items don't have comments. 29 29 30 8. Nav Menu Items use more post meta fields than they actually need to use fields in the `wp_posts` table in the the posttable: `classes`, `menu_item_parent`, `object`, `object_id`, `orphaned`, `target`, `type`, `url` and `xfn`. Together 10 and 8 make using posts a heavy solution for the use-case.30 8. Nav Menu Items use more post meta fields than fields they actually need to use in the `wp_posts` table: `classes`, `menu_item_parent`, `object`, `object_id`, `orphaned`, `target`, `type`, `url` and `xfn`. Together 10 and 8 make using posts a heavy solution for the use-case. 31 31 32 32 7. Saving and loading posts fires many hooks, most of which are completely irrelevant for Nav Menu Items.