Meerkat

Troubleshooting

#Run the health check first

1php artisan meerkat:health

It verifies the database connection, blueprint, required tables, columns and indexes, mirror path, and queue connection.

#SQLSTATE ... no such table: comments (or threads)

Meerkat's tables have not been created. Run php artisan meerkat:install if the migrations were not published before php artisan migrate.

1php artisan meerkat:install

meerkat:sync also requires the tables, so complete installation before restoring a filesystem mirror.

#GraphQL or revisions return 404

GraphQL and revisions require Statamic Pro and are disabled by default.

  • GraphQL: enable Meerkat GraphQL and Statamic's GraphQL endpoint. See GraphQL.
  • Revisions: enable meerkat.revisions.enabled. See Revisions.

#Comments fail to save, or meerkat:health reports the mirror path

The filesystem mirror writes a file for every comment. If Meerkat cannot write to its path (default content/comments), comments fail to save. Fix the directory permissions, or disable the mirror with MEERKAT_MIRROR_ENABLED=false. See Filesystem mirror.

#The Meerkat item is missing from the Control Panel nav

The navigation item requires view comments. The submit comments permission alone does not show it. See Permissions.

#New migrations after an update

Meerkat publishes its migrations into your application. After composer update brings in a new migration, re-run the installer to publish and apply it:

1php artisan meerkat:install

Was this page helpful?