Like every other WordPress theme, Jupiter X may have conflicts with some plugins. Conflict here means at least one of the features of the theme doesn't work as expected due using a plugin. In this article, we will go through the famous plugin conflicts with Jupiter X and provide workarounds to resolve it. This article will check the possible conflicts and issues with the Bundled plugins of Jupiter X. Other popular plugins will gradually add to the list.
Sometimes logical conflicts happens because same features are available in both the theme and plugin. In this case, it's only the matter of setting the proper priority between the theme and plugin to resolve the issue.
- Fonts won't update on the website using Customizer settings
As an example, there is a conflict when you set up the Elementor Default fonts and also set the Default fonts using the Jupiter X Customizer. In this scenario, the Customizer fonts will not apply since the Elementor has a higher priority. To resolve this issue, just follow the steps provided in this article:
- Blog default page is not showing what you designed with Elementor or page editor
By default, WordPress overrides the default archive pages such as blog categories, tags, author posts and calendar archives. But more than that, sometimes you want to create a custom blog page design. Well, if you create a page and then assign it to be your Default Blog page in WordPress -> Settings -> Reading, it will not show any of your designed layout and only shows the default WordPress archive page. In case you had such issue, simply unassign the blog page in WordPress -> Settings -> Reading. You can still add that page in your menu.
Before everything, You don't need to buy Elementor Pro when you are using Jupiter X. However, Elementor pro is adding some advanced features such as the archive templates which is very useful indeed, but it's not mandatory to buy the Pro version of Elementor to work with Jupiter X. Here is more information about it.
Using Elementor Pro, some logical problems appear after you use the Display Conditions.
- Display Conditions
It's one of the features of Elementor Pro that gives you ability to set block or page templates to your website. You can choose where to show a block based on different conditions. Here you can find more information about it.
It's indeed useful for advanced website design, but Jupiter X has also a similar feature that has conflict with the Header and Footer templates when you set a display condition to the Header and Footer templates in Elementor Pro. The issue is, Elementor Pro overrides Jupiter X settings as soon as you set the Header or Footer templates to your website using the Display Conditions. Also, when you assign WooCommerce archive or single templates using the display conditions, you can not use the Shop Customizer settings anymore. It's a logical problem and in order to resolve it, you should make sure the display conditions are not set in any of the Header, Footer or WooCommerce templates.
You can check how to work with Custom Header and footers in Jupiter X here:
There is no reported conflict with Raven so far, except for a very specific situation after deactivating Elementor Pro and that is causing the header and footer to be invisible. The situation is explained as below:
- By default, the standard version of Elementor doesn’t have Header and Footer templates option.
- We add our own header and footer option with the same post type name as Elementor Pro using the Raven plugin. This is for users who don’t want to use Elementor Pro.
- In case you use Elementor Pro, the Header and footer records you created with the Raven plugin will be still available on the database, and you can still select them through the pages that has those header and footer templates selected (from the top bar of the front end while you are logged in to your website). However, you can not see them in the Elementor templates anymore.
- When you deactivate Elementor Pro and enable Raven, you can see the Raven header and footer templates in the Elementor templates section on your backend.
- In case you have used any Elementor Pro elements inside your “Raven” header and footers, as soon as you deactivate the Elementor Pro and use the standard version, you will no longer see those elements. Now if that was the only element you used, your header or footer will look empty.
So, to avoid that, It's recommended to either only use the Raven plugin and its elements and other plugins that is bundled to the theme, or recreate your header (if you want to use Elementor Pro) and assign it again in the customizer. This way your issue will be fixed.
One of the biggest concerns among the website designers is the performance and the first solution come to every mind is to use the caching plugins. At the moment, we have tested and made sure that the Jupiter X is fully compatible with WP ROCKET and Autoptimize with all the options activated. Other caching plugins are not tested yet, so they might have some possible conflicts.
If you wish to create a customized WooCommerce shop you can do it gently using Jet WooBuilder plugin. This plugin adds features to WooCommerce and let you create and choose templates for your archive pages, lists, single pages (individually and globally), custom shop page and etc. But, when it comes to show a list of products, there is a logical conflict with the Jupiter X shop customizer: Number of columns in a row.
You have created a template for your archive pages, designed a layout that has only one product in a row, configured it in the WooCommerce setting to show that template you have created, and now when you visit the page, the list is showing in a grid instead of a list. The issue is with default Shop Customizer grid system. To resolve this issue you can either set the number of columns in the Customizer -> Shop -> List to 1 (not recommended) or force your template to override the default WooCommerce settings and show the products in one column per row:
You can find more information about it in the Jet WooBuilder documentation here.
The only known issue with the Jet Plugins is that the as soon as Jet Elements, Jet Tricks and other Jet plugins are active along side with Raven and Elementor, it doesn't stop the spinner on the Elementor editor loading. So it won't be usable if you face this issue. To fix this problem, simple add this to your .htaccess file or ask your web host support to do it for you:
Also, Make sure you already have proper server resources as mentioned in this article.