Forum Replies Created

Viewing 15 replies - 1 through 15 (of 46 total)
  • Newt Labs

    (@newtlabs)

    We’re also seeing the following fatal error:

    Fatal error: Uncaught Error: Call to undefined function rcp_is_rcp_admin_page() in /wp-content/plugins/restrict-content/restrictcontent.php:1000 Stack trace: #0 /wp-includes/class-wp-hook.php(324): {closure}() #1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /wp-includes/plugin.php(517): WP_Hook->do_action() #3 /wp-admin/admin-header.php(303): do_action() #4 /wp-admin/users.php(604): require_once(‘…’) #5 {main} thrown in /wp-content/plugins/restrict-content/restrictcontent.php on line 1000

    This is because of your sale banner you’ve tried to implement to do with this:

    // Stop if isn’t a RCP page.
    if ( ! rcp_is_rcp_admin_page() ) {
    return;
    }

    To temporarily fix this before an update is released I have commented out the entire “Stellar Sale Banner” code.

    Thread Starter Newt Labs

    (@newtlabs)

    I have contacted Yoast to see if there’s anything they can do. In the meantime please can you confirm why the previous version of your plugin works fine but this version does not?

    Thread Starter Newt Labs

    (@newtlabs)

    Hi,

    It seems to be a conflict between your plugin and Yoast SEO Premium:

    I get the following error when activating the “WooCommerce emerchantpay Payment Gateway Client” plugin:

    Fatal error: Uncaught Error: Call to undefined function Automattic\Jetpack\wp_rand() in /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php:161 Stack trace: #0 /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php(99): Automattic\Jetpack\A8c_Mc_Stats->build_stats_url() #1 /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php(124): Automattic\Jetpack\A8c_Mc_Stats->get_stats_urls() #2 /wp-content/plugins/woocommerce/includes/class-woocommerce.php(414): Automattic\Jetpack\A8c_Mc_Stats->do_server_side_stats() #3 [internal function]: WooCommerce->log_errors() #4 {main} thrown in /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php on line 161

    When “Yoast SEO Premium” is deactivated the error doesn’t show. However If I deactivate “Yoast SEO Premium”, activate “WooCommerce emerchantpay Payment Gateway Client”, then try to reactivate “Yoast SEO Premium” I get the following:

    Plugin could not be activated because it triggered a fatal error. Fatal error: Uncaught Error: Call to undefined method Composer\Autoload\ClassLoader::setClassMapAuthoritative() in /wp-content/plugins/wordpress-seo-premium/vendor/composer/autoload_real.php:43 Stack trace: #0 /wp-content/plugins/wordpress-seo-premium/vendor/autoload.php(7): ComposerAutoloaderInit42a00a4ee82636814e937c49e791ee2d::getLoader() #1 /wp-content/plugins/wordpress-seo-premium/wp-seo-premium.php(67): require(‘…’) #2 /wp-admin/includes/plugin.php(2387): include_once(‘…’) #3 /wp-admin/plugins.php(194): plugin_sandbox_scrape() #4 {main} thrown in /wp-content/plugins/wordpress-seo-premium/vendor/composer/autoload_real.php on line 43

    If there’s anything you can do including pointing me in the right direction please let me know, in the meantime I will contact Yoast.

    Thread Starter Newt Labs

    (@newtlabs)

    [video_lightbox_youtube video_id=”u4D-wjmeXwE&rel=0″ height=”auto” width=”100%” anchor=”/wp-content/uploads/2020/07/anchor_image.png”]

    Thread Starter Newt Labs

    (@newtlabs)

    Hi,

    nothing on the domain was changed, the only other thing that changed since the issue appeared was that we updated the WP version from 6.5.5 – 6.6.

    We are not using your plugin on this website so you can close this ticket but I thought it would be worth sharing in case there is a bug.. As mentioned the issue is resolved when deactivating the WP Code plugin and the site works fine when adding the same scripts to the head via the theme.

    Thread Starter Newt Labs

    (@newtlabs)

    these scripts added via the head of the theme template work fine and do not add anything to the url. It is only when adding them via your plugin there is an issue, they were working fine before on your plugin for many years but crashed the site after updating to the latest version of your plugin.

    I’m also seeing a fatal error when updating:

    Fatal error: Uncaught Error: Call to undefined function rcp_is_rcp_admin_page() in /wp-content/plugins/restrict-content/restrictcontent.php:1000 Stack trace: #0 /wp-includes/class-wp-hook.php(324): {closure}() #1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /wp-includes/plugin.php(517): WP_Hook->do_action() #3 /wp-admin/admin-header.php(303): do_action() #4 /wp-admin/admin.php(239): require_once(‘…’) #5 {main} thrown in /wp-content/plugins/restrict-content/restrictcontent.php on line 1000

    Thread Starter Newt Labs

    (@newtlabs)

    that seems to work, thanks.

    Thread Starter Newt Labs

    (@newtlabs)

    Hi, after changing invoice_number to number and invoice_date to date the pdfs stopped working and returned a fatal error:

    Fatal error: Too few arguments to function WPO\WC\PDF_Invoices\Documents\Order_Document::number(), 0 passed in /themes/ico/woocommerce/pdf/iCO/invoice.php on line 119 and exactly 1 expected.

    This is how the code is being used in the custom template:

                <?php if ( isset($this->settings['display_number']) ) { ?>
    
                <tr class="invoice-number">
    
                    <th><?php echo $this->get_number_title(); ?></th>
    
                    <td><?php $this->invoice_number(); ?></td>
    
                </tr>
    
                <?php } ?>
    
                <?php if ( isset($this->settings['display_date']) ) { ?>
    
                <tr class="invoice-date">
    
                    <th><?php echo $this->get_date_title(); ?></th>
    
                    <td><?php $this->invoice_date(); ?></td>
    
                </tr>
    
                <?php } ?>

    Please can you confirm what needs changing so we are not using deprecations?

    Thread Starter Newt Labs

    (@newtlabs)

    good point, cheers.

    @barryhughes-1 I did post a solution in the “v1.0.2 Critical Error” thread which should point you in the right direction.

    Highlighted Changes to fix this issue while waiting for update to be released.

    In maybe_add_hpos_incompatibility_admin_notice:

    1. Instance Creation:phpCopy code$instance = new self(); // Create an instance of the class
    2. Calling Non-static Method:phpCopy codeif( ! $instance->hpos_is_enabled() || self::user_has_dismissed_admin_notice( 'legacy_rest_api_is_incompatible_with_hpos' ) ) {

    In maybe_remove_hpos_incompatibility_admin_notice:

    1. Instance Creation:phpCopy code$instance = new self(); // Create an instance of the class
    2. Calling Non-static Method:phpCopy codeif ( WC_Admin_Notices::has_notice( 'legacy_rest_api_is_incompatible_with_hpos' ) && ! $instance->hpos_is_enabled() ) {

    These highlighted changes will resolve the error by correctly calling the non-static hpos_is_enabled method on an instance of the WC_Legacy_REST_API_Plugin class.

    The issue arises because the hpos_is_enabled method is non-static, but it is being called statically within the maybe_add_hpos_incompatibility_admin_notice and maybe_remove_hpos_incompatibility_admin_notice methods. To fix this, we need to create an instance of the WC_Legacy_REST_API_Plugin class before calling the non-static hpos_is_enabled method.

    Here’s how you can modify the maybe_add_hpos_incompatibility_admin_notice and maybe_remove_hpos_incompatibility_admin_notice methods to address this issue:

    1. Update maybe_add_hpos_incompatibility_admin_notice Method:

      REPLACE THIS:

      private static function maybe_add_hpos_incompatibility_admin_notice() { if( ! self::hpos_is_enabled() || self::user_has_dismissed_admin_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ) ) { return false; } if ( ! WC_Admin_Notices::has_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ) ) { $features_page_url = admin_url( ‘admin.php?page=wc-settings&tab=advanced&section=features’ ); WC_Admin_Notices::add_custom_notice( ‘legacy_rest_api_is_incompatible_with_hpos’, sprintf( wpautop( __( ‘? <b>The Legacy REST API plugin and HPOS are both active on this site.</b><br/><br/>Please be aware that the WooCommerce Legacy REST API is <b>not</b> compatible with HPOS. <a target=”_blank” href=”%s”>Manage features</a>’, ‘woocommerce-legacy-rest-api’ ) > $features_page_url ) ); return true; } return false; }

      WITH THIS:

      private static function maybe_add_hpos_incompatibility_admin_notice() { $instance = new self(); // Create an instance of the class if( ! $instance->hpos_is_enabled() || self::user_has_dismissed_admin_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ) ) { return false; } if ( ! WC_Admin_Notices::has_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ) ) { $features_page_url = admin_url( ‘admin.php?page=wc-settings&tab=advanced&section=features’ ); WC_Admin_Notices::add_custom_notice( ‘legacy_rest_api_is_incompatible_with_hpos’, sprintf( wpautop( __( ‘? <b>The Legacy REST API plugin and HPOS are both active on this site.</b><br/><br/>Please be aware that the WooCommerce Legacy REST API is <b>not</b> compatible with HPOS. <a target=”_blank” href=”%s”>Manage features</a>’, ‘woocommerce-legacy-rest-api’ ) ), $features_page_url ) ); return true; } return false; }

    2. Update maybe_remove_hpos_incompatibility_admin_notice Method:

      REPLACE THIS:

      private static function maybe_remove_hpos_incompatibility_admin_notice() { if ( WC_Admin_Notices::has_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ) && ! self::hpos_is_enabled() ) { self::remove_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ); } }

      WITH THIS:

      private static function maybe_remove_hpos_incompatibility_admin_notice() { $instance = new self(); // Create an instance of the class if ( WC_Admin_Notices::has_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ) && ! $instance->hpos_is_enabled() ) { self::remove_notice( ‘legacy_rest_api_is_incompatible_with_hpos’ ); } }
    Thread Starter Newt Labs

    (@newtlabs)

    Hi, here's the log I hope it helps. By the way we increased the execution time to 120s this morning.
    
    WooCommerce Version: 8.2.1 - You are using the latest version of WooCommerce.
    
    Product Types: ? Simple Product [simple]
    
    ? Grouped Product [grouped]
    
    ? External/Affiliate Product [external]
    
    ? Variable Product [variable]
    
    Total Products: WP Query: 508
    WC Product Query: 508
    Both Query: 508 Product Total by Types. ? Simple Product: 43 ? Variable Product: 465 ? Product Variations: 1494 Product Per Batch: 200 Product Query Type: WC_Product_Query Default Customer Location: Default Customer Location
    Geolocate Store Address
    The Granary Loft
    Radstock
    GB
    BA3 4QF : Multi Language Site: Google Language Translator is not compatible for multi-language feed. You can not make feed for each language. Supported multi-language plugins are WPML & Polylang. Multi Currency Site: Below Multi Currency Plugins are compatible with Woo Feed Pro. ? Currency Switcher WooCommerce by Aelia
    ? WooCommerce Currency Switcher by Realmag777
    ? WooCommerce Multilingual
    ? Polylang WP DEBUG Status: WP_DEBUG is false. If you having any issue with the plugin then set WP_DEBUG to true so that you can find the issue from logs. You can learn more about debugging in WordPress from here. WP CRON: WordPress cron is disabled. The Auto Feed Update will not run if WordPress cron is Disabled. Upload Directory: Ok - Writable. Cache Plugin Installed: No. WordPress Multi Site: No : Server Info Home Url: *** Site Url: *** Version: 8.2.1 Log Directory: /wp-content/uploads/wc-logs/ Log Directory Writable: Yes WP Version: 6.3.2 WP Multisite: No WP Memory Limit: 512 MB WP Debug Mode: No WP Cron: No Language: en_GB External Object Cache: Yes Server Info: nginx/1.24.0 Php Version: 8.1.25 Php Post Max Size: 64 MB Php Max Execution Time: 120 Php Max Input Vars: 2.93 KB Curl Version: 7.81.0, OpenSSL/3.0.2 Suhosin Installed: No Max Upload Size: 64 MB Mysql Version: 8.0.35 Mysql Version String: 8.0.35-0ubuntu0.22.04.1 Default Timezone: UTC Fsockopen Or Curl Enabled: Yes Soapclient Enabled: Yes Domdocument Enabled: Yes Gzip Enabled: Yes Mbstring Enabled: Yes Remote Post Successful: Yes Remote Post Response: 200 Remote Get Successful: Yes Remote Get Response: 200 : Installed Theme Virtue - Premium Child: 4.10.8.1673345265 (Latest:0) : Installed Plugins ManageWP - Worker (GoDaddy): 4.9.17 Akismet Anti-spam: Spam Protection (Automattic - Anti-spam Team): 5.3 WP Offload Media (Delicious Brains): 3.2.5 Autoptimize (Frank Goossens (futtta)): 3.1.9 Beautiful and responsive cookie consent (Beautiful Cookie Banner): 3.0.0 Bulletin Announcements (Bulletin): 3.8.5 Cart Upsell for WooCommerce (SKROTRON): 1.0.8 Classic Widgets (WordPress Contributors): 0.3 Contact Form 7 (Takayuki Miyoshi): 5.8.2 Customer Reviews for WooCommerce PRO (CusRev): 1.4.1 Customer Reviews for WooCommerce (CusRev): 5.37.1 Doofinder WP & WooCommerce Search (Doofinder): 2.0.32 EAN for WooCommerce (WPFactory): 4.8.2 Facebook for WooCommerce (Facebook): 3.1.2 Flexible Shipping PRO (Octolize): 2.16.6 Flexible Shipping (Octolize): 4.23.0 Google Authenticator (Ivan Kruchkoff): 0.54 Google Language Translator (Translate AI Multilingual Solutions): 6.0.19 WPCode Lite (WPCode): 2.1.4.1 Limit log in attempts reloaded (Limit log in attempts reloaded): 2.25.26 Logo Showcase Ultimate Pro (wpWax): 1.6.3 My Custom Functions (Space X-Chimp): 4.51 Page-list (webvitaly): 5.6 Popup Builder (Looking Forward Software Incorporated.): 4.2.0 ActiveCampaign Postmark (Official) (Andrew Yates & Matt Gibbs): 1.20.0 Page Builder by SiteOrigin (SiteOrigin): 2.27.0 SiteOrigin Widgets Bundle (SiteOrigin): 1.56.0 WP FAQ (WP OnlineSupport, Essential Plugin): 3.8 SpinupWP (SpinupWP): 1.5.1 Sucuri Security - Auditing, Malware Scanner and Hardening (Sucuri Inc.): 1.8.39 Visual Portfolio, Posts & Image Gallery (Visual Portfolio Team): 3.1.3 CTX Feed (WebAppick): 6.2.4 (Latest:6.2.5) Conditional Discounts for WooCommerce - A simple yet complete woocommerce dynamic pricing plugin (ORION): 2.31.5 WooCommerce Cart Abandonment Recovery (CartFlows Inc): 1.2.25 Woo Product Dropdown Widget (Razorfrog Web Design): 1.1.3 Product Feed PRO for WooCommerce (AdTribes.io): 13.0.7 Woo Stickers by Webline (Weblineindia): 1.1.6 WooCommerce Customer/Order/Coupon Export (SkyVerge): 5.5.0 WooCommerce EU/UK VAT Compliance (Premium) (David Anderson): 1.29.7 WooCommerce Stripe Gateway (WooCommerce): 7.6.2 WooCommerce Google Analytics Integration (WooCommerce): 1.8.9 WooCommerce Grid / List toggle (jameskoster): 1.2.1 CURCY - WooCommerce Multi Currency Premium (VillaTheme): 2.3.1 WooCommerce Nested Category Layout (SkyVerge): 1.19.0 WooCommerce PayPal Payments (WooCommerce): 2.4.0 PDF Invoices & Packing Slips for WooCommerce (WP Overnight): 3.7.1 WooCommerce PDF Invoices & Packing Slips Premium Templates (Ewout Fernhout): 2.12.0 Brevo - WooCommerce Email Marketing (Brevo): 4.0.3 WooCommerce Shipment Tracking (WooCommerce): 2.4.1 WooCommerce (Automattic): 8.2.1 Yoast SEO Premium (Team Yoast): 21.5 Yoast SEO (Team Yoast): 21.5 WP Crontrol (John Blackbourn & contributors): 1.16.0 WP Migrate (WP Engine): 2.6.10 Smush Pro (WPMU DEV): 3.14.2 WP101 Video Tutorial Plugin (WP101?): 5.3.1 Feed Files
    /wp-content/uploads/woo-feed/google/xml/ap-feed.xml Fatal Errors
    2023-11-07T08:31:05+00:00 CRITICAL Maximum execution time of 30 seconds exceeded in /wp-includes/Requests/src/Transport/Curl.php on line 510

    It seems ok now, cheers.

Viewing 15 replies - 1 through 15 (of 46 total)