WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #24138, comment 2


Ignore:
Timestamp:
04/20/13 01:26:35 (12 months ago)
Author:
krembo99
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24138, comment 2

    v2 v3  
    1 I know they could be defined anywhere , but since this is a multisite , regardless of the actual location where they are defined ,those constants will affect ALL blogs ( unless specifically defined or treated otherwise ).. I am also not sure how does a defined constant will act upon conflicts where the same constant is sharing a name but different in value. which will take priority ? (or the constant will just keep on "switching" and "bouncing" from one value to the other ) . Also, constants that are cron - dependent ( like trash or auto-save ) would be entering a bit of a conflict ( as to my understanding ) 
     1I know they could be defined anywhere , but since this is a multisite , regardless of the actual location where they are defined ,those constants will affect ALL blogs ( unless specifically defined or treated otherwise ).. I am also not sure how does a defined constant will act upon conflicts where the same constant is sharing a name but different in value. which will take priority ? (or the constant will just keep on "switching" and "bouncing" from one value to the other ) . Also, constants that are cron - dependent ( like trash or auto-save ) would be entering a bit of a conflict ( as to my understanding at least until the Heartbeat API [https://core.trac.wordpress.org/ticket/23216] will be fully implemented )