The Integrations tab lists the integrations available for the theme you are running. Open a different jkdevstudio theme and the list is different. That is intended, and this page explains the rule behind it.
#Each integration names its themes
Every integration carries its own list of products it supports. Your theme shows only the ones that work with it.
So the case people ask about, seeing integration A in one of our themes and not in another, is the system working. The other theme has B instead.
The reason is fit. An integration built around a magazine layout has nowhere to render in a portfolio theme, and shipping it there would create a setting that does nothing.
#Translation is the default
The one integration category present in every one of our themes is translation, through two integrations: WPML and Polylang. Everything else is opt-in.
The reason is narrow: those two integrations are what allow our own admin strings to be translated on a multilingual site. That covers the theme panel, Theme Options and everything else we render into the dashboard. Both plugins read the text domains our products register, which is how a Ukrainian or German administrator sees our settings screens in their language.
This is about translating the interface, and it does nothing for your front end.
Nothing here translates a post, a page or a menu label your visitors read. Translating the front end is a separate job done by the translation plugin itself, and the visible part of it in the theme is the language switcher, which is its own integration per provider, such as the WPML language switcher.
#How the list is ordered
Self-contained integrations come first, then the ones that sit on top of a third-party plugin.
That order is more useful than alphabetical, because the first thing you want to know about an integration is whether using it means installing something else as well.
#What each integration page tells you
The format is the same throughout, so you can skim it:
- what it adds
- where it is switched on
- what it requires
If an integration needs a third-party plugin, that is stated on its row and on its page.
#Common questions
Why do WPML and Polylang appear even though my site is in one language?
They are the interface translation layer, so they are listed for every theme. On a single-language site you leave them off.
Can I request an integration for my theme?
Yes, as a feature request and not a support ticket, because it is a roadmap question. Feature requests come with a direct license; on a Regular key you can still vote on published roadmap entries.
Will the list grow?
It does over time, and new integrations appear in the tab on their own with nothing to reinstall.
I use a service you do not have an integration for
Its own plugin usually works. What you lose is the theme-level styling and placement that an integration provides.
Does an integration work on the free edition?
The registry and the screen are visible on a free edition, but the catalog they install from comes with the Pro plugin and an active license. The list is browsable; the install is not.
I expected an integration and it is not listed
First check that the theme and the Pro plugin are both up to date, since the list is served against the current pair. If it is still absent, it is not supported for this theme, and a feature request is the right channel.
#Still stuck
Open a support ticket and say what you tried and where it stopped. Your product, your domain, a screenshot and the exact message you saw are usually enough to settle it in one reply.
Last updated
