WordPress Automatic Update Help Forum Topic – BPS Must-Use Plugin

Home Forums BulletProof Security Pro WordPress Automatic Update Help Forum Topic – BPS Must-Use Plugin

  • This topic is empty.
Viewing 1 post (of 1 total)
  • Author
    Posts
  • #39266
    AITpro Admin
    Keymaster

    First off, I apologize for the BPS MU Tools plugin Description text, which is very hard to read.  WordPress does not allow line breaks in Plugin Description text and strips out certain HTML code characters such as line break HTML code.

    • Disable all Updates: On = All WordPress Automatic Updates: Core, Plugins, Themes and Translations will be disabled.
    This option uses this WordPress Automatic Update filter:  add_filter( 'automatic_updater_disabled', '__return_true' );
    When this option is set to On all WordPress Automatic Updates will be disabled on a website.
    When this option is set to Off it means that the option is not in use/enabled. In other words, the automatic_updater_disabled filter is not being applied/used on your website.
    Note: This option also removes the Automatic Updates column on the WordPress Plugins page and the enable auto-updates link for Themes.

    • Disable all Core Updates: On = All WordPress Core Automatic Updates: Development, Minor and Major versions are disabled.
    This option uses this WordPress Automatic Update filter:  add_filter( 'auto_update_core', '__return_false' );
    When this option is set to On all WordPress Core Automatic Updates will be disabled on a website.
    When this option is set to Off it means that the option is not in use/enabled. In other words, the auto_update_core filter is not being applied/used on your website.
    Note: WP Site Health will still report that “Background Updates are working”, but that is incorrect. I checked the WP Site Health code and it is not checking if this filter and value is being applied to a website.

    • Enable all Core Updates: On = All WordPress Core Automatic Updates: Development, Minor and Major versions are enabled.
    This option uses this WordPress Automatic Update filter:  add_filter( 'auto_update_core', '__return_true' );
    When this option is set to On all WordPress Core Automatic Updates will be enabled on a website.
    When this option is set to Off it means that the option is not in use/enabled. In other words, the auto_update_core filter is not being applied/used on your website.

    • Enable Development Updates: On = WordPress Core Automatic Updates are enabled for Development WP versions.
    This option uses this WordPress Automatic Update filter:  add_filter( 'allow_dev_auto_core_updates', '__return_true' );
    When this option is set to On WordPress Core Automatic Updates are enabled for Development versions of WP.
    When this option is set to Off it means that the option is not in use/enabled. In other words, the allow_dev_auto_core_updates filter is not being applied/used on your website.

    • Enable Minor Updates: On = WordPress Core Automatic Updates are enabled for Minor WP versions.
    This option uses this WordPress Automatic Update filter:  add_filter( 'allow_minor_auto_core_updates', '__return_true' );
    When this option is set to On WordPress Core Automatic Updates are enabled for Minor versions of WP.
    When this option is set to Off it means that the option is not in use/enabled. In other words, the allow_minor_auto_core_updates filter is not being applied/used on your website.
    Note: WordPress minor version releases enabled by default on most sites.

    • Enable Major Updates: On = WordPress Core Automatic Updates are enabled for Major WP versions.
    This option uses this WordPress Automatic Update filter:  add_filter( 'allow_major_auto_core_updates', '__return_true' );
    When this option is set to On WordPress Core Automatic Updates are enabled for Major versions of WP.
    When this option is set to Off it means that the option is not in use/enabled. In other words, the allow_major_auto_core_updates filter is not being applied/used on your website.

    Note: By default, only minor releases – such as for maintenance and security purposes – and translation file updates are enabled on most sites.

    Possible problems:

    If conflicting filters are enabled/Turned On then unintended results will occur.  Example:  If Disable all Updates: On is used with Enable all Core Updates: On the end result will be: All WordPress Automatic Updates: Core, Plugins, Themes and Translations will be disabled.

    Error Checking:

    BPS checks if you are currently using WP Automatic Update constants in your wp-config.php file when you enable/Turn On any of the BPS MU Tools WP Automatic Update options/filters.  The Dismiss Notice below will be displayed to alert someone if this scenario occurs. The reason for that is you would either want to use ONLY the BPS MU Tools WP Automatic Update options/filters or the WP Automatic Update constants in your wp-config.php file to handle WordPress Automatic Updates. If you have conflicting values for the BPS MU Tools WP Automatic Update options/filters and the WP Automatic Update constants in your wp-config.php then unintended results will occur

    BPS wp-config.php file WP Automatic Update constants detected
    You are using the BPS Pro MU Tools plugin option settings to handle WP Automatic Updates. BPS detected that you are also using one or both of these WP Automatic Update constants in your wp-config.php file: WP_AUTO_UPDATE_CORE and/or AUTOMATIC_UPDATER_DISABLED. Either comment out these constants in your wp-config.php file or delete these constants. If you choose to comment out these constants instead of deleting them then dismiss this Dismiss Notice after you have commented them out. When BPS Pro AutoRestore quarantines the wp-config.php file after you haved edited it, restore the wp-config.php file from BPS Pro Quarantine using the Restore File option.
    To Dismiss this Notice click the Dismiss Notice button below. To Reset Dismiss Notices click the Reset|Recheck Dismiss Notices button on the S-Monitor page.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.