Logs

Track what is going on with the built in logs.

Communicating Logs

When you are asking for support, Algolia recommends that you include logs if your issue is related to indexing problems or if your question is quota related.

This way, they can get a better sense of what is happening in your website.

PHP logs - With an extension

If you are not technical or find it easier to use a plugin to access the PHP error logs, you can use: https://wordpress.org/plugins/error-log-monitor/

Once installed, you will be able to see your PHP error logs in a widget on the WordPress dashboard screen.

PHP logs - Manual

Most of the job done by this plugin is done asynchronously, which makes debugging a bit harder. For that reason the plugin includes custom logs as is explained in the previous sections of this page.

When you are unable to debug your issues with the provided logs, it probably means you have PHP exceptions that are being raised behind the scenes.

---

For performances reasons, logging will only occur if WP_DEBUG is defined to true.

---

To access your PHP logs you should:

1. Turn WordPress debug mode on:

   Simply add the following lines to your wp-config.php:

   <?php
   // [...]
   define( 'WP_DEBUG', true );
   define( 'WP_DEBUG_LOG', true );
   // [...]
   

2. Re-try the operations you expect to go wrong, like hitting the Process queue button on the Indexing page of the plugin.

3. Check what has been logged in the wp-content/debug.log file.

---

If none of that helped, please head to the frequently asked questions to get help.

---