Skip to content

Troubleshooting

CoverKit requires the PHP Imagick extension. Ask your host to enable it, or install php-imagick on the server. Without Imagick, generation fails.

Use PHP 8.1 or newer (see plugin header and installation).

Generation writes cache files under your WordPress content directory. Ensure PHP can write to wp-content/uploads and other writable content paths your host uses for CoverKit output.

  1. Confirm the template is published.
  2. In the template editor, enable the Open Graph image use case and save mappings. See Open Graph image.
  3. Check use case settings (post types, front page, archives) match the page you are viewing.
  4. View page source for og:image — the URL should point at a generated image on your site.
  5. Open that URL in a browser to confirm the image loads.

If the design changed but meta still points at old art, clear the template cache.

If CoverKit is correct but a social network still shows an old thumbnail, the platform is caching the preview—see Caching overview.

  • Save the template after changing use case assignments or layers.
  • Clear cache on the template (edit screen meta box or list bulk action).
  • Reload the preview or front-end image URL.

Edit a CoverKit template (coverkit post type), not a normal post, for template-only blocks. On posts and pages, use the CoverKit Canvas block. See Editor overview.

  • Save the template after changing use case assignments.
  • Check the browser network tab for failed calls to CoverKit REST routes (preview requires editor capabilities).
  • Rebuild plugin assets if you develop from source: npm run build in the plugin directory.

Global options live at Settings → CoverKit (image format and dimension presets). Use case settings are per template in the CoverKit sidebar.