Home Forums Weaver Xtreme Theme Weaver Extreme issue with WP-CLI

  • This topic has 6 replies, 3 voices, and was last updated 2 years ago by User.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #74931
    WombatsSA
    Participant

    We have an outdated Plugin that is being replaced by a supported one and are hoping to use WP-CLI to do a mass import of the data.
    – Working with the new plugin’s author to do it.

    I installed WP-CLI and ran a test to see it was working, using “wp plugin list” and “wp core check update” as recommended by the plugin author.

    I saw:
    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) in /home/wombatss/public_html/wp-content/themes/weaver-xtreme/functions.php on line 370

    The plugin developer who is helping me checked out “functions.php on line 370” to see if he could help and sent me a revised version with the blue code below between the existing lines:

    // weaverx_admin_header_style
    //–

    if ( ! defined( ‘WP_CLI’ ) ) {
    add_action(‘widgets_init’, ‘weaverx_widgets_init_action’);
    }

    /**
    * Register our sidebars and widgetized areas.
    *
    * @since Weaver Xtreme 1.0
    */

     

    After uploading the modified functions.php (backed up the original) I ran the “wp plugin list” again and the memory error moved:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) in /home/wombatss/public_html/wp-content/themes/weaver-xtreme/functions.php on line 286

    So either his solution to the problem was not right or functions.php (or more plugin features) need more  changes to allow WP-CLI to work?

    Can anyone help with this please?

    Thanks,

    Merv
    ===========================

    ### Weaver System Info ###

    — WordPress Configuration —

    Site URL: https://wombatssa.org.au
    Home URL: https://wombatssa.org.au
    Multisite: No
    Version: 6.6.1
    Language: en_AU
    WP_DEBUG: Disabled
    WP Memory Limit: 128M
    Permalink: /%postname%/
    Show On Front: page
    Page On Front: Home (ID# 10)
    Page For Posts: (ID# 0)
    Current Theme: Weaver Xtreme (6.5.1)
    Post Types: post, page, attachment, revision, nav_menu_item, custom_css, customize_changeset, oembed_cache, user_request, wp_block, wp_template, wp_template_part, wp_global_styles, wp_navigation, wp_font_family, wp_font_face, envira, wpmem_product, responsive_accordion, product, product_variation, shop_order, shop_order_refund, shop_order_placehold, feedback, dedo_download, jp_mem_plan, patterns_ai_data, wpforms, wpforms-template, jp_pay_order, jp_pay_product

    — Weaver Xtreme Configuration —

    Weaver Xtreme Version: 6.5.1
    Theme Support Version: 6.5.1

    — Server Configuration —

    Operating System: Linux
    PHP Version: 8.2.20
    MySQL Version: 10.5.25
    jQuery Version: 3.7.1
    Server Software: Apache

    — PHP Configuration —

    Local Memory Limit: 256M
    Server Memory Limit: 128M
    Post Max Size: 8M
    Upload Max Filesize: 2M
    Time Limit: 30
    Max Input Vars: 1000
    Display Errors: N/A

    — WordPress Active Plugins —

    404 to 301 – Redirect, Log and Notify 404 Errors: 3.1.4
    BackWPup: 4.1.4
    Better Search Replace: 1.4.7
    Custom Error Pages: 1.2
    Delightful Downloads: 1.6.6
    Disable Gutenberg: 3.1.2
    Duplicate Page: 4.5.4
    Easy Accept Payments via PayPal: 5.1.0
    Easy Timeout Session: 1.1
    Envira Gallery Lite: 1.8.15
    Health Check & Troubleshooting: 1.7.1
    Jetpack: 13.7
    Login Logo Editor: 1.3.3
    Nav Menu Roles: 2.1.2
    Really Simple CAPTCHA: 2.3
    Responsive Accordion And Collapse: 2.4.9
    Site Kit by Google: 1.134.0
    User Login Log: 2.2.2
    Video.js – HTML5 Video Player for WordPress: 4.5.0
    Weaver Show Posts: 1.8.1
    Weaver Xtreme Theme Support: 6.5.1
    Widget Shortcode: 0.3.5
    WooCommerce: 9.2.3
    WooCommerce Square: 4.7.3
    Wordfence Security: 7.11.7
    WP-Members: 3.4.9.5
    WP-Members Download Protect: 1.9.8
    WP Admin Bar Removal: 2014.0707.0383
    wpDataTables – Tables & Table Charts: 3.4.2.22
    WP Edit: 4.0.4
    WPForms Lite: 1.9.0.4
    WP Mail SMTP: 4.1.1
    WP Super Cache: 1.12.4
    Yoast SEO: 23.3

    — WordPress Inactive Plugins —

    Akismet Anti-spam: Spam Protection: 5.3.3
    Hello Dolly: 1.7.2
    Ozh’ Admin Drop Down Menu: 3.7.1
    Redirection: 5.5.0

    ### End System Info ###

    #74932
    User
    Moderator

    @Weaver will need to comnent.

    Regards!

    #74933
    Weaver
    Keymaster

    I don’t have access to my dev environment at the moment, so can’t really answer at the moment. I don’t really have any idea what might be happening.

    But one thing to perhaps try. Plugins and widgets used are usually totally independent of the theme you are using.

    You might be able to try a different theme to see if you still get WP-CLI related errors and the switch back.

    But backup your database before trying that. I really don’t remember what WP-CLI is or does, and don’t know why it had special handling in Weaver’s code.

    #74934
    User
    Moderator

    @WombatsSA

    As I am sure you know, you will be able to test Weaver’s advice using another Theme on the “Health Check & Troubleshooting” which you have installed already.

    From memory the recommended WP vanilla theme to test on, is “TwentyTwelve” (2012), which is before blocks came on the scene.

    Regards!

    #74935
    WombatsSA
    Participant

    Thanks for the responses. 🙂

    Although now retired, I had been working on programming for 50+ years and Web stuff for 30+ years and actually kept away from WordPress.
    – Had my own team that created custom, non-WordPress Web solutions, so I don’t have deep knowledge of WordPress.
    I now volunteer for a Not-for-Profit that has a WordPress website.

    This problem has already taken way too much of my time and I was hoping to get an answer from the developer about the code issue with WP-CLI, which is a WordPress command-line tool we have been advised to use for the plugin data swap.

    Having to backup and restore the database increases my concern … no other changes are likely to be made to the system by adding and activating a new theme?

    For speed of swap – could I create a copy of the database via phpMyAdmin and switch between them by altering the database Name / PW login in wp-config.php? Sounds like it should work to me?

    I searched for “Vanilla WordPress theme” and “Harmless WordPress theme” but did not find anything with sufficient detail.

    I will ask the TwentyTwelve Theme Forum about the safety of using it as a “switch-test theme”.

    Thanks for your help.

    Merv

    #74936
    User
    Moderator

    Hi Merv,
    Sorry, by vanilla, I meant a new and unused WP Theme such as:

    Twenty Twelve


    Which has not been used on the site before.
    That (2012) theme can be used on the aforementioned “Health Check & Troubleshooting” plugin instead of the Xtreme Theme, to test for conflicts and compatibility issues between WP and themes and plugins.
    Please note that the Health Check plugin troubleshooting function does not impact or affect the live site in any way, and no chamges made there are transferred to the live site. It is all done in its own ‘sandbox’.
    As Weaver said, no plugins should be altering any Theme code, so testing with the 2012 theme ought to give some insights as to which plugin is misbehaving.
    Regards!

    #74937
    User
    Moderator

    Hi Merv,
    In the event that you find a plugin which is conflicting with the current theme version, there’s a plugin wich will allow you to roll back things to previous versions to get things working again.
    I find it very useful in such circumstances.

    WP Rollback – Rollback Plugins and Themes


    Regards!

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.