WCFM and Post Expirator conflict

  • Resolved denrossww

    (@denrossww)


    3 years, 4 months ago

    I have upgraded my staging website from WordPress version 5.2.11 to 5.7.2 and from WCFM (WooCommerce for Marketplace) 3.4.0 to 3.4.9. The result is that when a Vendor tries to edit a product, the screen is displayed like this:-

    https://tinyurl.com/yfyxp9uc

    It is all squashed in to a narrow column. I have narrowed it down to the Post Expirator plugin, as this is the fatal error that is displayed:-

    How to expire:
 Fatal error: Uncaught Error: Call to undefined function _postExpiratorExpireType()
in /home/wwdevie/dev.ww.ie/wp-content/plugins/wc-frontend-manager/core/class-wcfm-integrations.php on line 1484

Call stack:

WCFM_Integrations::wcfm_woo_product_post_expirator_product_manage_views()
wp-includes/class-wp-hook.php:292
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:316
WP_Hook::do_action()
wp-includes/plugin.php:484
do_action()
wp-content/plugins/wc-frontend-manager/views/products-manager/wcfm-view-products-manage.php:868
include()
wp-content/plugins/wc-frontend-manager/core/class-wcfm-template.php:38
WCFM_Template::get_template()
wp-content/plugins/wc-frontend-manager/core/class-wcfm-library.php:940
WCFM_Library::load_views()
wp-content/plugins/wc-frontend-manager/includes/shortcodes/class-wcfm-shortcode-wc-frontend-manager.php:42
WCFM_Frontend_Manager_Shortcode::output()
wp-content/plugins/wc-frontend-manager/core/class-wcfm-shortcode.php:114
WCFM_Shortcode::shortcode_wrapper()
wp-content/plugins/wc-frontend-manager/core/class-wcfm-shortcode.php:46
WCFM_Shortcode::wc_frontend_manager()
wp-includes/shortcodes.php:343
do_shortcode_tag()
preg_replace_callback()
wp-includes/shortcodes.php:218
do_shortcode()
wp-includes/class-wp-hook.php:292
WP_Hook::apply_filters()
wp-includes/plugin.php:212
apply_filters()
wp-includes/post-template.php:253
the_content()
wp-content/plugins/wc-frontend-manager/templates/classic/wcfm-content.php:32
include()
wp-includes/template-loader.php:106
require_once()
wp-blog-header.php:19
require()
index.php:17

    I have reported this to the WCFM (wclovers.com) developers as well as yourselves for a resolution please as both plugins are essential to the operation of our website.

    Kind regards
    Zoe Sterling

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter denrossww

    (@denrossww)

    Further update: WCFM have referred me back to the developers of Post Expirator. Please could anyone advise? Thanks in advance.

    Plugin Author Steve Burge

    (@stevejburge)

    Hi @denrossww. Is this appearing on the frontend of your site? Can you disable Post Expirator on this post type?

    Thread Starter denrossww

    (@denrossww)

    Hi Steve

    Yes, technically it is on the front end. WCFM is a vendor platform for WordPress/WooCommerce. Each of our vendors have their own unique products which are available until 5 minutes before their class starts (they sell online classes as products in conjunction with zoom).

    The WCFM gives a frontend back office view so that Vendors can log in to WordPress and view their products and edit them themselves using the marketplace interface without being allowed to see the admin toolbar.

    So they log in and click on a product using WCFM interface to edit the product, but because the latest code of Post Expirator is conflicting with the code for WCFM (www.wclovers.com) it causes a php error and distorts the view.

    I have reverted back to Post Expirator version 2.4.1 as it works OK with WCFM’s latest version.

    So I cannot disable Post Expirator for Products, because the product must expire 5 minutes before the zoom class begins because they must not be able to accept sales after the class has started and it must disappear from the website so it can’t be purchased. It is the only reason we use the plugin.

    Many thanks.
    Zoe

    Plugin Author Steve Burge

    (@stevejburge)

    Hi @denrossww

    Thanks for the detailed report. Sorry, we can’t guarantee a solution for this in a specific timeframe. It’s an unusual integration issue with another plugin that has a custom layout. So 2.4.1 may be your best option for now.

    But I will open an issue for our team to look at and we’ll post back here when it’s fixed.

    Thread Starter denrossww

    (@denrossww)

    Many thanks.

    WCFM seem to know of the issue, so others may have reported it WCFM as well.

    We will stick with Post Expirator 2.4.1 for the time being.

    We import approx 150 products weekly using a custom import file. This also has the Post Expiry Date & Time using a custom php on the import file to ensure the products are set to private at the specific date/time. So maybe best to stick with what works for this reason too!

    Thanks again.

    Plugin Author Steve Burge

    (@stevejburge)

    @denrossww thanks for reporting this. It will be fixed in our next release.

    Thread Starter denrossww

    (@denrossww)

    That is great news. Thank you

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WCFM and Post Expirator conflict’ is closed to new replies.

Tags