WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #52279, comment 2


Ignore:
Timestamp:
01/12/2021 02:02:42 AM (5 months ago)
Author:
stacksoft
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #52279, comment 2

    initial v1  
    1 Also, we do NOT want to add custom code to each deployment. We see this article https://make.wordpress.org/core/2013/10/25/the-definitive-guide-to-disabling-auto-updates-in-wordpress-3-7/ suggesting that we can add a filter:
    2 
    3 `add_filter( 'automatic_updates_is_vcs_checkout', 'update_languages_vcs', 10, 2 );`
    4 
    5 and return false, but that means we need to add custom code to each of our vanilla projects?
    6 
    7 I'm super confused on why you would want this extreme behaviour not overridable. This is absolutely awful for us. This seems like the exact case of having a variable in wp-config.php to disable this behaviour. It also looks like since it isn't overridable on 5.6, all past versions are not overridable either.
    8 
    9 We are now trying to find methods to trick WordPress on the OS level to disable this behaviour. We cannot use custom code for each project, it's not viable in the environment we are in :(
    10 
    11 Who thought this was a good idea?