Potential conflicts to watch for:

Below are a list of plugin suites to look out for during the installation of Trellis. These will point to keywords and settings to look out for, but won't name specific plugins. This is meant to help identify potential conflicts on a wide scale.

Optimization/Minification - Any plugin that performs any type of optimization or minification to HTML, CSS, or Javascript should at the very least have those settings disabled. At best the work done here is a duplication of effort with the built-in optimizations of Trellis, and can frequently result in conflicts.


Image Plugins - If you're using Trellis Images then you're already generating .webp images for your site. If there are two plugins performing this action, conflicts can arise. Disable .webp generation in your other image optimization plugins.


Lazy Load - Lazy loading of images has been part of WordPress core since version 5.5. Additional lazy loading plugins should not be required with Trellis.


Rest API - Rest API is used by not only Trellis, but our Create plug-in as well. There are several plugins out there that disable Rest API, so this is something to look for during installation. This setting is typically found in other optimization/minification plugins, but definitely something to keep an eye out for in standalone plugins as well.


Known conflicts within plug-ins:

Below are a list of plugins that have direct conflicts with Trellis and should be deactivated or settings changed during the Trellis installation process.


WP Rocket/Autoptimize/SG Optimizer/WP Optimize

These plug-ins provide minification and other optimizations that are unnecessary with Trellis. Trellis essentially solves the same problems, and if these tasks are duplicated it can result in broken functionality or layout issues on the site. If you are still considering using these plugins, we recommend disabling any "Optimization" style features ( this includes any HTML/CSS/JS Optimization)


WP Fastest Cache/W3 Total Cache

These plug-ins provide a lot of options for minification that can cause conflicts with Trellis. The caching features of these plug-ins should be ok to run with Trellis, but the minification settings should be disabled.


A3 Lazy Load

WordPress and Trellis will handle lazy loading of images and iframes, so any additional lazy loading is unnecessary and can create conflicts. This plugin should be deactivated when using Trellis.

Divi Builder/Thrive Architect/Beaver Builder/Elementor/WPBakery

Pagebuilders are not something that Trellis has built in compatibility with. Some can work, but they have a negative impact on performance which defeats the purpose of using Trellis to begin with.

If you feel that these page builder tools are necessary for the success of your business, Trellis might not be the best fit for you. If you're trying to get away from heavy pagebuilder tools, we recommended using the WordPress block editor (Gutenberg) with Trellis instead.



Jetpack

Jetpack is mostly fine to use with Trellis. However, optimizations in the Performance tab are redundant and can conflict with some Trellis built-in optimizations. We recommend disabling all Performance settings in Jetpack, as well as Jetpack's Comments Module, as this can cause a conflict when using Trellis.



Shortpixel/Smush/Imagify

If you're using Trellis Images you'll will want to disable the .webp generation setting found in many image optimization plug-ins like Shortpixel.

If you prefer Shortpixel, or some other image optimization plug-ins, to serve next-gen images, then Trellis Images will be redundant.

For more tips on optimizing your plug-in suite for Trellis, read this post on our blog.

Did this answer your question?