• Azey

    (@akumarjain)


    Updating the plugin to 1.9.3 caused a site to show fatal errors. Here is the error message:

    PHP Fatal error:  Cannot redeclare modify_specific_module() (previously declared in /srv/htdocs/wp-content/plugins/filter-everything/src/wpc-third-party.php:1044) in /srv/htdocs/wp-content/plugins/filter-everything/src/wpc-third-party.php on line 1044

    I had to roll back the plugin to 1.9.2.2 to recover the site from fatal error.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support fesupportteam

    (@fesupportteam)

    Hi @akumarjain

    Can you please provide the following information: the plugins currently in use, the active theme, and the PHP version? This will help us understand the current environment and recreate this type of issue on our end.

    Best regards,
    Victor

    Thread Starter Azey

    (@akumarjain)

    Hi Victor! Here is the list of active plugins:

    +---------------------------------------------+----------+
    | name | version |
    +---------------------------------------------+----------+
    | advanced-custom-fields | 6.8.5 |
    | woocommerce-advanced-free-shipping | 1.1.7.1 |
    | advanced-woo-search | 3.67 |
    | akismet | 5.7 |
    | all-in-one-wp-migration | 7.106 |
    | all-in-one-wp-migration-unlimited-extension | 2.51 |
    | automatewoo | 6.7.0 |
    | blaze-ads | 0.9.0 |
    | change-wc-price-title | 2.9 |
    | chaport | 1.1.9 |
    | dg-divi-carousel | 2.0.26 |
    | divi-pixel | 2.52.0 |
    | dg-product-carousel | 2.0.2 |
    | excel-like-product-manager | 2.1.86 |
    | filter-everything | 1.9.2.2 |
    | fluentform | 6.2.6 |
    | fluentformpro | 5.0.7 |
    | woocommerce-google-analytics-integration | 2.3.0 |
    | google-listings-and-ads | 3.7.3 |
    | gtranslate | 3.1.1 |
    | health-check | 1.7.1 |
    | jetpack | 16.1-a.1 |
    | mailpoet | 5.34.0 |
    | mailpoet-premium | 5.34.0 |
    | facebook-for-woocommerce | 3.7.4 |
    | pinterest-for-woocommerce | 1.4.27 |
    | sassy-social-share | 3.3.79 |
    | simple-history | 5.29.0 |
    | tiktok-for-woocommerce | 1.3.7 |
    | pojo-accessibility | 4.1.3 |
    | weight-based-shipping-for-woocommerce | 6.16.0 |
    | woocommerce | 10.9.4 |
    | woocommerce-back-in-stock-notifications | 3.3.4 |
    | woocommerce-gift-cards | 2.7.4 |
    | woocommerce-min-max-quantities | 5.2.9 |
    | woocommerce-product-addons | 8.3.1 |
    | woocommerce-product-bundles | 8.5.9 |
    | woocommerce-product-recommendations | 4.3.4 |
    | woocommerce-shipment-tracking | 2.7.4 |
    | woocommerce-shipping | 2.3.10 |
    | woocommerce-side-cart-premium | 1.2 |
    | woocommerce-services | 3.6.7 |
    | woocommerce-tm-extra-product-options | 5.1 |
    | woocommerce-payments | 10.9.0 |
    | google-sitemap-generator | 4.1.24 |
    | yith-woocommerce-wishlist | 4.16.0 |
    +---------------------------------------------+----------+

    The active theme is Divi. The PHP version is 8.3.32 and the Core version is 7.0.1.

    Hi everyone, I can’t offer much more insight here, but I can confirm the issue. I also use the Divi Builder; here are my plugins:

    • Advanced Custom Fields
    • Compliance by Hu-manity.co
    • Divi Blog Extras
    • Divi Plus
    • Filter Everything PRO
    • Imagify
    • Maintenance
    • Shortcodes Ultimate
    • UpdraftPlus
    • Wordfence
    • WP Rocket
    • WPS Hide Login
    • Yoast Duplicate Post
    • Yoast SEO
    Plugin Support fesupportteam

    (@fesupportteam)

    Hi @akumarjain @mabentrup

    Please go to our official site support page: https://filtereverything.pro/support/. You will find the support chat at the bottom right side of the page. Please describe the issue you are experiencing there.

    Best regards,
    Victor

    Thread Starter Azey

    (@akumarjain)

    @fesupportteam, I reported the issue on behalf of a customer. I’ll ask them to go to the Pro Support page and report the issue there.

    I also purchased the plugin for a client. However, I don’t understand why I have to create a ticket in a separate forum when this support forum already exists.

    Couldn’t you, @fesupportteam , just forward the bug to your team?

    Plugin Support fesupportteam

    (@fesupportteam)

    Hi @mabentrup

    The issue has been forwarded to the development team, and they are attempting to recreate it in order to provide a proper fix. However, they are still in the process of reproducing the issue and have not been able to achieve the same result yet.

    This step is required to ensure that the fix works properly, rather than releasing a quick patch that could potentially cause additional issues in the future.

    Best regards,
    Victor

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

You must be logged in to reply to this topic.