[wp-trac] [WordPress Trac] #29688: Stop editing line in default config not explicit enough

[WordPress Trac]

#29688: Stop editing line  in default config not explicit enough
-------------------------+-----------------------------
 Reporter:  kirrus       |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:  trunk
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 In my experience, new system administrators tend to append to config
 files, unless said config files have explicit "Don't edit below this line"
 instruction lines.

 The language of the "/* That's all, stop editing! Happy blogging. */"
 comment doesn't indicate that the functions defined below it are order-
 critical, in my experience they tend to assume a config file won't have
 any functional logic in -- most software packages do not put critical
 logic in config files.

 WordPress actually runs the main codebase setup from within the config
 file, so if defines are put below the wp-settings.php require, they are
 not used by WordPress at all, effectively discarded. This tends to cause a
 few hours of head scratching, as to why /wp-admin/ is redirecting to the
 old domain, when SITEURL define is appended in the config, for example.

 Would it be possible to put another comment below the stop editing line,
 along the lines of
 /* Nothing should be defined below this line */

 Or anything in plainer language, that makes explicit that Bad Things Will
 Happen if you put things below the settings require?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29688>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform