• Resolved designstugan

    (@designstugan)


    Hi

    I’ve been using EUM for a while now and I like it very much BUT for some of my sites it still do the WP core updates even though I’ve set it at ‘Manually Update’ and unchecked ‘Allow development…’. In the log from this morning it says Core update ‘Failure’ but it has still updated the core to 6.0 – which I wanted to avoid.

    How can I avoid that this doesn’t happen?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hi @designstugan

    It could be a plugin conflict issue, to me it seems like you have other active plugins preventing EUM from disallowing automatic core updates. I’m not sure what plugin they could be, but as far as I know JetPack also has their own “automatic core updates” setting, which in some cases when it’s enabled then anything you set to the EUM’ WordPress core updates setting won’t have any effects at all.

    Thanks
    Anthon

    Thread Starter designstugan

    (@designstugan)

    Thank you Anton!
    I don’t have Jetpack installed on any of these sites; one is a regular simple/small with regular WP theme, one is a multi site with Divi theme and the third one is a regular site with Divi and a child theme.
    I probably need to compare these sites even more deeply to see what they might have in common since I have 20 something other sites with Divi and EUM where this doesn’t happens.

    Any more suggestions on how I’ll be able to find what causes this?

    Hi @designstugan

    Sorry for the delay.

    Are these websites hosted on a managed WP hosting? In the log entry where you find the Failure status of the Core update, what does it say in its show notes when you click it?. Also, could you please post your site information here, just one of the sites. To get the site info you could fetch it from the WP site health tools (/wp-admin/site-health.php?tab=debug), click the Copy site info to clipboard button and paste here.

    Thanks
    Anthon

    Thread Starter designstugan

    (@designstugan)

    Hi Anthon, one of the sites that has this problem is inspiratorerna.se (the one with a regular WP theme – Twenty-sixteen).
    No these websites are not om Managed WP hosting, just an ordinary account/set up ( or what ever it is called šŸ™‚ ).

    In the log entry for the Failure status it is empty in the Notes column. I only have a ‘note’ in the Stack Trace column.

    Here is the info from the WP Health check tool:

    
    ### wp-core ###
    
    version: 6.0
    site_language: sv_SE
    user_language: sv_SE
    timezone: +00:00
    permalink: /%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 1
    default_comment_status: open
    environment_type: production
    user_count: -1
    dotorg_communication: true
    
    ### wp-paths-sizes ###
    
    wordpress_path: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html
    wordpress_size: 57,45 MB (60239771 bytes)
    uploads_path: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html/wp-content/uploads
    uploads_size: 158,27 MB (165952974 bytes)
    themes_path: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html/wp-content/themes
    themes_size: 898,37 KB (919929 bytes)
    plugins_path: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html/wp-content/plugins
    plugins_size: 44,18 MB (46325505 bytes)
    database_size: 14,23 MB (14925824 bytes)
    total_size: 275,01 MB (288364003 bytes)
    
    ### wp-active-theme ###
    
    name: Twenty Sixteen (twentysixteen)
    version: 2.6 (latest version: 2.7)
    author: WordPress-teamet
    author_website: https://sv.ww.wp.xz.cn/
    parent_theme: none
    theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, title-tag, custom-logo, post-thumbnails, menus, html5, post-formats, editor-style, editor-styles, wp-block-styles, responsive-embeds, editor-color-palette, customize-selective-refresh-widgets, custom-line-height, custom-background, custom-header, widgets
    theme_path: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html/wp-content/themes/twentysixteen
    auto_update: Inaktiverat
    
    ### wp-mu-plugins (1) ###
    
    ManageWP - Worker Loader: author: GoDaddy, version: (undefined)
    
    ### wp-plugins-active (10) ###
    
    Easy Updates Manager: version: 9.0.12, author: Easy Updates Manager Team, Automatiska uppdateringar inaktiverade
    Loopia WordPress Plugin: version: 0.1, author: Loopia AB, Automatiska uppdateringar inaktiverade
    ManageWP - Worker: version: 4.9.13, author: GoDaddy, Automatiska uppdateringar inaktiverade
    Really Simple SSL: version: 5.3.1, author: Really Simple Plugins (latest version: 5.3.2), Automatiska uppdateringar inaktiverade
    Remove Footer Credit: version: 1.0.13, author: WPChill, Automatiska uppdateringar inaktiverade
    Social Slider Feed: version: 2.0.3, author: creativemotion, Automatiska uppdateringar inaktiverade
    Wordfence Security: version: 7.5.10, author: Wordfence, Automatiska uppdateringar inaktiverade
    WP Activity Log: version: 4.4.1, author: WP White Security, Automatiska uppdateringar inaktiverade
    WP Last Modified Info: version: 1.7.7, author: Sayan Datta (latest version: 1.8.3), Automatiska uppdateringar inaktiverade
    WP Maintenance Mode & Coming Soon: version: 2.4.4, author: Themeisle, Automatiska uppdateringar inaktiverade
    
    ### wp-plugins-inactive (2) ###
    
    Akismet Anti-Spam: version: 4.2.2, author: Automattic (latest version: 4.2.4), Automatiska uppdateringar inaktiverade
    Broken Link Checker: version: 1.11.16, author: WPMU DEV, Automatiska uppdateringar inaktiverade
    
    ### wp-media ###
    
    image_editor: WP_Image_Editor_Imagick
    imagick_module_version: 1692
    imagemagick_version: ImageMagick 6.9.12-34 Q16 amd64 2021-12-22 https://imagemagick.org
    imagick_version: 3.5.1
    file_uploads: File uploads is turned off
    post_max_size: 200M
    upload_max_filesize: 200M
    max_effective_size: 200 MB
    max_file_uploads: 50
    imagick_limits: 
    	imagick::RESOURCETYPE_AREA: 128 GB
    	imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
    	imagick::RESOURCETYPE_FILE: 1412538
    	imagick::RESOURCETYPE_MAP: 128 GB
    	imagick::RESOURCETYPE_MEMORY: 64 GB
    	imagick::RESOURCETYPE_THREAD: 1
    imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X3F, XBM, XC, XCF, XPM, XPS, XV, YCbCr, YCbCrA, YUV
    gd_version: 2.3.1
    gd_formats: GIF, JPEG, PNG, WebP, BMP
    ghostscript_version: not available
    
    ### wp-server ###
    
    server_architecture: FreeBSD 12.2-RELEASE-p12 amd64
    httpd_software: Apache/2.4.52 (FreeBSD) mpm-itk/2.4.7-04 PHP/7.4.27
    php_version: 7.4.27 64bit
    php_sapi: apache2handler
    max_input_variables: 5000
    time_limit: 180
    memory_limit: 256M
    max_input_time: -1
    upload_max_filesize: 200M
    php_post_max_size: 200M
    curl_version: 7.80.0 OpenSSL/1.1.1h
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true
    htaccess_extra_rules: true
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 10.3.35-MariaDB-log
    client_version: mysqlnd 7.4.27
    max_allowed_packet: 10485760
    max_connections: 1400
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html/wp-content
    WP_PLUGIN_DIR: /www/webvol23/zu/xnvnwmqifqhjt93/inspiratorerna.se/public_html/wp-content/plugins
    WP_MEMORY_LIMIT: 40M
    WP_MAX_MEMORY_LIMIT: 256M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: false
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_ENVIRONMENT_TYPE: Odefinierat
    DB_CHARSET: utf8
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    mu-plugins: writable
    
    

    Hope this was what you asked for. šŸ™‚

    Thank you!
    Kattis

    Hi,

    Yes, that’s what I was asking for. Also, in the log entry for the Failure status, could you please take a look at the Action column to see what’s written there, is it Manual or Automatic? There might be a manual update operation (not automatic) was performed by another admin user directly from within the website (via WP’s Updates screen) or via 3rd party dashboard that can manage many websites in one place (i.e. ManageWP — you have the plugin in your website inspiratorerna.se).

    Thanks
    Anthon

    Thread Starter designstugan

    (@designstugan)

    Hi Anthon, I am the one administrating the site alone for my client. Meaning, I’m the one using ManageWP, so there is no other admin on the site and the updates in MWP is set to manually.

    This is how the row reads in the log:
    User: None
    Name: WordPress 6.0
    Type: Core
    From: 6.0
    To: 6.0
    Action: Automatic
    Status: Failure
    Date: 2022-05-25 07:05:49
    Notes:
    Stack Trace: Show Trace

    And this is what the rows read for the previous ‘core update’:
    User: None
    Name: WordPress 5.9.3
    Type: Core
    From: 5.9.3
    To: 5.9.3
    Action: Automatic
    Status: Failure
    Date: 2022-04-06 04:05:03
    Notes:
    Stack Trace: Show Trace

    All Core entries in the log looks the same except that the earlier ones is empty in the ‘Stack Trace’ columns as well.

    Thank you!
    Kattis

    • This reply was modified 3 years, 11 months ago by designstugan.

    Hi Kattis,

    EUM had several log bugs in its previous version (9.0.12), and it looks like the log entries you provided were affected with one of the bugs. I recommend you update EUM to its current version (9.0.13), which has been released on June 7th. EUM has a better log mechanism in that new version, also there’s a tweak concerning the core updates, it deals with how EUM prevents other plugins from overriding the Manually core updates setting.

    Thanks
    Anthon

    Thread Starter designstugan

    (@designstugan)

    Thanks Anthon, I’ll do the update and see what happen after that then.

    Can we please keep this thread ‘open’ for a while if I still run into problems.

    Best,
    Kattis

    Hi Kattis,

    Sure, no problem. I will keep an eye on this topic.

    Thanks
    Anthon

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

The topic ‘Manually updates don’t work properly’ is closed to new replies.