When something goes wrong

The short answers to the questions that come up again and again. Debug is the page to have open while you read this. Paste it when you ask on the discussions board.

An ADIF file will not import

The file has to end in .adi. An .adif renamed by hand is still the wrong name until the extension is .adi.

Pick the station location the contacts belong to. With no location selected, Cloudlog has nowhere to put them.

If the file is large and the page comes back blank, or the browser gives up, the upload is bigger than PHP will accept. Debug shows the upload limit. The install notes say how to raise it. post_max_size has to be larger than upload_max_filesize.

A file full of contacts you already have will look like a failure if Import duplicate QSOs is off. That switch is on the import page, and it is described on the ADIF page. Leaving it off is usually what you want.

The message about the options table

Table 'cloudlog.options' doesn't exist means the database has not been brought up to date. Log in, or open any page, and Cloudlog applies the pending database changes. The update script does that request for you.

If the message is still there after a page load, the database user cannot create tables. That user needs to be able to change the Cloudlog database. The install notes cover the grants.

Developer Mode across the top

The red badge means this Cloudlog is running with the development environment switched on. Day to day it should say production. Whoever looks after the server sets CI_ENV. If the badge appeared after an update, that setting was left on development.

Restoring from a database dump

The copy you make from the callsign menu is a zip of your stations, logbooks, and contacts. That is the copy to use when you are moving your own log.

A .sql dump is the whole database, taken on the server. Putting one back is a job for the person who runs MariaDB or MySQL: load the dump into the Cloudlog database, put the Cloudlog files back beside it, and open the site once so the database version matches the files. Config files hold the database password. They need to match the server you restored onto.

If you have the zip and you do not have a dump, use the zip. It is the restore path the Backup page was built for.