When I have all 3 plugins – Revolution Slider, Woo Commerce and Page Builder – installed, conflicts occur. When I searched your site for “conflicts”, I got many many pages of results. I am hoping you may be aware of conflicts with these plugins so that I don’t have to read through all the results.
Conflict with Revolution Slider & Woo Commerce
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Sbehnfeldt,
Can you please clarify on the issues you’re having? There are no major compatibility issues known for either plugins.
Can you try disabling all non-SiteOrigin plugins (leave WooCommerce and Revolution Slider active) and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Alex – Thank you for your reply. Since my original post, I have tracked down the problem. I will explain it to you, and hopefully you may be able to help me find a solution.
tl;dr: We have a slider with a content source of “posts”. Revolution Slider processes it as though it were of source of “WooCommerce.” Revolution takes the source post ID and, thinking it is a WooCommerce product ID, tries to get product info from the database. This causes WordPress to crash.
More detail:
RevSliderSlider::getSlidesForOutput() calls RevSliderSlider::isSlidesFromPosts() to determine whether the slider source type is of type “posts”. Unfortunately, isSlidesFromPosts() returns true if the source type is any of “posts”, “specific_posts”, or “woocommerce”. Since isSlidesFromPosts() returns true, getSlidesForOutput() calls RevSliderSlider::getSlidesFromPosts(). This method initializes each slide by calling RevSliderSlide::initByPostData(), which in turn calls RevSliderSlide::setLayersByPostData(), which in turn calls RevSliderSlide::set_post_data(). This is where the crash actually happens.
set_post_data() makes a call to RevSliderWooCommerce::isWooCommerceExists(), which returns true if the “Woocommerce” class exists. Since we are using WooCommerce, this check returns true. Since the check returns true, set_post_data() tries to construct a WC_Product object from the post ID of the slide, EVEN THOUGH THE SOURCE TYPE IS NOT WOOCOMMERCE. get_product() returns null, but set_post_data() doesn’t check for this eventuality and attempts to call various WC_Product methods on a null object.
I have temporarily fixed this (directly editing the Revolution Slider source code) by checking the return value of get_product() for null. This seems to correct the problem. But of course it is never a good idea to directly modify plugin code.
Moreover, it does seem highly incredible that nobody has encountered this problem before, considering that Woo and Revolution are two hugely-popular plugins with large user bases. This makes me wonder whether I am missing something terribly fundamental.
Thank you for any insight you can offer.
FYI:
Apache 2.2.15
PHP 5.4.45
WordPress 4.5.5
SmartMag 2.6.2
Bunyad Page Builder 1.3.7.6-mod
Slider Revolution 5.1.5
WooCommerce 2.6.13
–Kind regards,
Stephen
Hi Stephen,
Thank you for your extremely detailed post! I hate to ask but… are you running our page builder? I ask as our Page Builder is actually called SiteOrigin Page Builder, not Bunyad Page Builder (I’ve never actually heard of that page builder before). I just want to confirm we’re talking about the same plugin here.
If you’re not, I’m very sorry about the misunderstanding on our part!
You’re right. It’s a different page builder, but our copy has a link to SiteOrigin. I guess somebody here edited it manually to point to you? Who knows.
Sorry for the inconvenience.