WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #11286, comment 41


Ignore:
Timestamp:
11/26/2012 10:20:40 PM (9 years ago)
Author:
bpetty
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11286, comment 41

    initial v1  
    88Besides that though, we could be returning a much more useful variety of error codes to the frontend to distinguish the types of errors (besides just 403 used for all of them) so it knows better how to handle the response besides showing the visitor a localized message, and frontend code having no idea why it failed.
    99
    10 Anyway, if this is changed too quickly here, plugins and themes will need to be fixed to handle this as is (it breaks backwards compat), and we don't want to do that twice. So I really believe this should wait off until the core team has some time to start looking at some of the long overdue comment system improvements that have been briefly touched on in a number of open tickets related to comments (maybe 3.6, but maybe not even until 3.7) - most of those tickets have already been mentioned here.
     10Anyway, if this is changed too quickly here, plugins and themes will need to be fixed to handle this (it breaks backwards compat), and we don't want to do that twice. So I really believe this should wait off until the core team has some time to start looking at some of the long overdue comment system improvements that have been briefly touched on in a number of open tickets related to comments (maybe 3.6, but maybe not even until 3.7) - most of those tickets have already been mentioned here.
    1111
    1212For that matter, this patch as it stands could do a better job at maintaining backwards compatibility itself.