Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter pumpkinbread

    (@pumpkinbread)

    Marking resolved.

    Thread Starter pumpkinbread

    (@pumpkinbread)

    no problem.

    Managed to comb through everything through ssh as root.

    Use find command to locate all 5.7.2 installs.
    Then use grep to find config files without the auto update flag.
    Then manually proceeded to insert the flag to the installs that don’t have it set.

    I am sure someone who knows bash can write a script that automates the whole process, but that’s beyond my knowledge.

    Hope others find this helpful. Can consider this matter resolved.

    Thank you!

    Thread Starter pumpkinbread

    (@pumpkinbread)

    It’s fine.

    My question was about delaying remote push by www.ads-software.com on this major update as this would affect a lot of installs (not just mine) that relies on the documentation.

    Regardless, I assumed the answer is a no, we have proceeded to change our settings hopefully before the automatic update gets pushed to more installs.

    Thread Starter pumpkinbread

    (@pumpkinbread)

    Ok now I understand. Yes, all the sites that are auto-updating today are from 5.7.X

    This starts to make sense now, given the documentation is not up to date.

    #1-
    I just want to confirm: this flag will still disable / prevent all automatic major updates?
    define( ‘WP_AUTO_UPDATE_CORE’, ‘minor’ );

    #2-
    Here is a crazy ask:
    Is it possible to delay further auto update push by 24 hours? We have relied on the documentation thinking that auto major updates would not happen. I do have a few hundred production installs where I would set auto update to minor release only to prevent sites crashing out of the blue (even if it is a small percentage, it is not ideal). This time would allow me (and potentially others) to avert disaster by putting the flag in and disabling an automatic major update.

    I don’t think I am the only person managing a few hundred installs who may be have the same issue (?)

    Thread Starter pumpkinbread

    (@pumpkinbread)

    Hi, thank you for quick response.

    #1- webhost – it is not a managed service. We have a few hundred wordpress installs on the same vendor and has not happened before / consistently across all our sites, so I would eliminate this as a possibility

    #2- plugins – yes this is a likely candidate. I will look forward to see if there is a common plugin among the sites that auto-updated.

    Right now, 5 sites auto-updated. Give or take 2% of sample size.

    We are also racing against this by adding the auto update minor code to all installs before it hits more sites, so may not be able to get the best data.

    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)