WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #18227, comment 4


Ignore:
Timestamp:
07/28/11 19:45:31 (4 years ago)
Author:
MarcusPope
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18227, comment 4

    initial v1  
    11Replying to [comment:2 azaozz]: 
    22 
    3 My fix is purely to prevent the JS error that is thrown when editor or title support are removed from a post - a fix of that nature should definitely happen regardless of autosave's purpose. 
     3My fix is intended purely to prevent the JS error that is thrown when editor or title support are removed from a post - a fix of that nature should definitely happen regardless of autosave's purpose. 
    44 
    55However I also think preventing autosave entirely because those fields were not enabled or because they are empty seems like a poor assumption - especially so with the advent of custom post types.  Why shouldn't a custom post type be allowed to rely on the autosave functionality for custom meta properties it has implemented in a save_post action hook?