Changes between Initial Version and Version 1 of Ticket #26946, comment 22
- Timestamp:
- 02/27/2014 01:43:09 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26946, comment 22
initial v1 42 42 2. The `'transition_post_status'`, `'edit_post'`, `'post_updated'`, `"save_post_{$post_type}"`, `'save_post'`, `'wp_insert_post'` hooks ''(and many others)'' need to make sure that they filter out `'nav_menu_item'` posts which isn't always obvious to everyone. 43 43 44 1. `wp_unique_post_slug()`; [https://core.trac.wordpress.org/ticket/11863#comment:52 the ill-fated decision] to allow values for the `post_name` field in trash override the values of newly created posts makes Nav Menu Items and other programmatic usedof posts a real data integrity nightmare. I wasted a literal month's worth of coding trying to use the WordPress menus in a system where my code generated the menus, with constant data integrity issues until I finally ripped it out and put in my own menu system and all the issues went away.44 1. `wp_unique_post_slug()`; [https://core.trac.wordpress.org/ticket/11863#comment:52 the IMO ill-fated decision] to allow values for the `post_name` field in trash override the values of newly created posts makes Nav Menu Items and other programmatic uses of posts a real data integrity nightmare. I wasted a literal month's worth of coding trying to use the WordPress menus in a system where my code generated the menus, with constant data integrity issues until I finally ripped it out and put in my own menu system and all the issues went away. 45 45 46 46 P.S. Further, none of the WordPress admin UI for posts is used for menus which is a strong hint that maybe the two things really are different.