[wp-trac] [WordPress Trac] #37339: Need to invalidate opcode cache after writing configuration

[WordPress Trac]

#37339: Need to invalidate opcode cache after writing configuration
-------------------------------------+------------------------------
 Reporter:  remicollet               |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Upgrade/Install          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+------------------------------

Comment (by mikeschroder):

 @remicollet First, I want to apologize that it's taken as long as it has
 to have progress on this ticket. Thanks for the ticket and your patch!

 I took a look at this today, and want to check in to make sure I
 understand the problem.

 It looks like in `setup-config.php`, writing to `wp-config.php` won't
 happen if `wp-config.php` already exists, due to
 [https://github.com/WordPress/wordpress-develop/blob/master/src/wp-admin
 /setup-config.php#L59 this check on line 59].

 Since it doesn't write unless it's creating a new file, I believe that
 means that there wouldn't be any previous settings to invalidate during
 the setup process.

 Could you please walk me through when the changes to `wp-config.php`
 happened, and using what method?

 Thanks so much!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37339#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform