Troubleshooting

The problems that come up most, and the order to check things in.

Start with System > Logs > Error log. Most of what follows is a shortcut to the same answer.

The site shows a blank page#

Almost always a PHP error with display disabled. Look at the error log first, then at your host's PHP error log. The usual causes are a missing extension after a PHP version change and a file that lost its permissions.

E-mails never arrive#

1. System > Logs > Email log: does the attempt appear at all?
2. If it does not, the message was never queued. Check that cron is running.
3. If it appears and failed, the reason is in the row: bad credentials, a refused sender, a blocked port.
4. If it appears and succeeded but nothing arrives, it is spam filtering. Use SMTP on your own domain with SPF and DKIM configured, not the PHP mail function.

Scheduled work never happens#

Digests, the license heartbeat and cleanup all ride on the scheduler. Check System > Logs > Task log. An empty log means the cron entry is missing or points at the wrong PHP binary. Some hosts have several.

The license will not activate#

• Invalid serial: check for a typo, and check that you copied a serial for the product you are installing.
• Domain in use: the license is active on another domain. Deactivate it there, or from your account here.
• Revoked: the license was refunded or charged back.
• Network error: the host cannot reach the license server. See License and activation.

An update fails#

The updater restores files and the database when a step fails after the backup, so you are back where you started. The run history records the step that broke. The usual causes:

• a directory that is not writable;
• not enough disk space for the backup;
• no database dump tool available on the host.

If the web request times out on a big package, run the update from a shell:

php artisan bondry:update --file=/path/to/package.zip

A module disappeared after an update#

It became incompatible and was disabled at boot. Modules shows the reason: the core version, the PHP version or another module it needs. Update the module, and if there is no update yet, the previous core version is still in your account.

A member cannot see something they should#

It is a group permission nine times out of ten. Check, in order:

1. the member's primary and secondary groups;
2. the permission matrix of those groups for that module;
3. the per-forum or per-category permissions;
4. any paywall rule, if Members Plus is installed.

Styles look broken after installing a theme#

Assets are published on install; if the publish failed, the CSS is missing. Reinstall the theme, and check that public/ is writable.

Still stuck#

Write to us from the account that owns the license, with the Bondry version, the PHP version, what you did and the exact error text. See Contact.