Log Files

Omnalingo writes its own log file separately from WordPress’s general error log. When something isn’t working as expected, the log is usually the fastest place to find out why.

Where to Find the Log

On a live (production) site, the log file is located at:

wp-content/omnalingo/logs/error.log

This is outside the plugin folder — look in wp-content/omnalingo/, not inside wp-content/plugins/omnalingo/.

You can read the log file with any text editor, an SFTP client, or via your hosting control panel’s file manager.

If you have SSH access, you can stream the log in real time while reproducing an issue:

tail -f wp-content/omnalingo/logs/error.log

If the Log File Doesn’t Exist

If wp-content/omnalingo/logs/error.log isn’t there and isn’t being created, the plugin couldn’t create the log directory. This usually means a file permissions issue on wp-content/omnalingo/.

When this happens, Omnalingo automatically falls back to writing log entries to the server’s PHP error log instead. To find those entries, search your PHP error log for lines starting with [Omnalingo]. The PHP error log location depends on your server configuration — commonly /var/log/php_errors.log or your web server’s vhost error log.

You can also confirm the fallback happened by searching your PHP error log for:

Omnalingo Logger: Could not create log directory

If you find that message, fix the directory permissions on wp-content/omnalingo/ (typically 755) and the log file will be created on the next request.

Log Entry Format

Each log entry looks like this:

[2025-06-15 14:32:01] [INFO] Settings updated
[2025-06-15 14:35:22] [ERROR] API request failed
 Array
(
    [message] => Connection timed out
    [url] => https://api.omnalingo.com/translate
)

Entries include a timestamp, a severity level, a message, and — when relevant — additional context shown as an array below the main message line.

Log Levels

Level	What it means
`DEBUG`	Detailed internal events — string registration, scan progress, lock handling. Useful for deep debugging.
`INFO`	Normal lifecycle events — settings saved, scan started, translation batch completed.
`WARNING`	Something unexpected happened but the plugin recovered — a fallback was used, a retry succeeded.
`ERROR`	Something failed — API call failed, database write failed, scan request couldn’t complete.

All four levels are written to the log file. When reporting an issue to support, ERROR and WARNING entries are the most useful to share.

Common Log Messages

Settings saved successfully:

[INFO] Settings updated

If you don’t see this after saving settings, the save likely failed — check for an ERROR entry around the same time.

API translation failed: Look for [ERROR] entries mentioning “API request failed” or “translate.” These indicate that Omnalingo couldn’t reach its translation servers. Common causes: no internet access from your server, a firewall blocking outbound HTTPS connections, or an expired API key.

Scan request issues: Look for [WARNING] or [ERROR] entries around the time you ran a scan. These can indicate that scan requests were blocked, timed out, or returned unexpected responses.

Log file creation failed:

Omnalingo Logger: Could not create log directory/file. Falling back to error_log.

This appears in your PHP error log (not in Omnalingo’s own log). See “If the Log File Doesn’t Exist” above.

When contacting Omnalingo support about an issue:

Open the log file.
Find the time range when the problem occurred.
Copy the relevant ERROR and WARNING entries from that time window.
Share those entries in your support request along with a description of what you were doing when the problem appeared.

Sharing the full log file is also fine if you can’t identify the relevant section.