Potential conflicts to watch for:
Below is 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.
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 plugins out there that disable Rest API, so this is something to look for during installation.
Known conflicts within plug-ins:
Below is a list of plugins that have direct conflicts with Trellis and should be deactivated or settings changed during the Trellis installation process.
Trellis is currently unsupported on sites and site servers running PHP 8.
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/Siteground
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.
Sites hosted by Lyrical Host are currently incompatible with Trellis's Critical CSS feature. We're currently working with Lyrical Host to resolve this incompatibility.
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.
Trellis includes built-in Comment functionality on posts and pages. Plugins like WPDiscuz, Jetpack’s Comments Module, Tasty Recipe Ratings, and other comment-related plugins are not compatible with Trellis.
However, Trellis’s built-in comment functionality can be disabled if absolutely necessary. This is in Trellis’s Settings under Layout.
iThemes Security, WordFence, Titan Anti-Spam
Security plugins can block Critical CSS functionality from working. Be sure to set your Firewall settings to "Learning Mode" for WordFence and Titan Anti-Spam. For iThemes Security be sure that the Rest API setting is Set to Default Access.
Cloudflare’s Bot Fight Mode/Super Bot Fight Mode
This feature will stop Trellis from being able to generate Critical CSS. If you need assistance disabling this feature, we recommend reaching out directly to Cloudflare.
If you're using Trellis Images you 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.