You are not using the correct API key
It seems like you are using a wrong API key in the Makeswift client or API handler.
Check that the correct API key is passed to both the Makeswift client and API handler. If you’re using an environment variable for the Makeswift API key, make sure it’s set properly. Our installation guide explains how to set that up:
There are no available elements to edit or the page is not integrated with Makeswift
The page you are trying to edit is not editable in Makeswift. This can happen for a number of reasons:
To make your page editable in Makeswift, please refer to our Quickstart guide.
If you see this message while trying to install Makeswift for your existing site, please make sure you have completed all the necessary steps in the Installation guide:
The host manifest is unreachable
Makeswift uses a host manifest to fetch metadata about your site. This metadata is used by the builder to determine what URL to use to route pages, what version of the runtime is running in the host, and what features are available in the host. If the host manifest is unreachable, the pages in the builder will not load properly.
Here is a list of things to check to make sure the host manifest is reachable:
Makeswift can only fetch the host manifest if your Next.js app is running. Make sure your Next.js app is running.
If your Next.js app is running, check that the host URL including the host name and port are correct in the Makeswift host settings. Update the host URL if necessary.
Makeswift fetches the manifest from an API handler in your Next.js app. If you’re using an environment variable for the Makeswift API key, make sure it’s set properly. Our installation guide explains how to set that up:
Your page did not connect to the builder in time.
Editing a page in the Makeswift Visual Builder requires your page to establish a connection with the builder. This message means that your page did not initialize this connection in time.
v0.24 and laterIn v0.24 and later, the connection is automatically initiated by the
ReactRuntimeProvider. Make sure you have correctly rendered the
ReactRuntimeProvider and are passing a correct value for the previewMode (in
v0.24) or siteVersion (in v0.25+) prop. For more details, see our
installation guides:
v0.23 and earlierFor v0.23 and earlier, the connection is initiated by the DraftModeScript or
PreviewModeScript components for App Router and Pages Router, respectively.
This message indicates that these components are likely missing from your page.
App Router
Make sure you have added the DraftModeScript component to the <head> of your
page by rendering it in the root layout.
Pages Router
Make sure you have added the PreviewModeScript component to the <Head> of the
page by extending the custom document.