Updating to a new version

An update is two steps: put the new files over the old ones, then open db_update.php once. Your own things are never in the package - config.php, installed.lock, the files in uploads/ and your settings in the database - so nothing of yours is overwritten.

Is there a new version?

Admin → Settings → Updates shows This version: the Script version, the version of the Database, when the site Last looked, and the Newest known version. Look for a newer version asks the License Center. When one is out, the tab says so (Version ... is out. Take a backup, replace the files, then open db_update.php.) and the bell in the admin panel shows it too.

Leave Update address under Where to look empty: it then asks your licence centre (its changelog of AIO Video), which is what you want. Look once a day by itself (on by default) lets the cron job Update check ask every day, so the panel knows about a new version without anybody pressing the button.

After the files of an update are in place, db_update.php also writes the Speed & security cache block back into .htaccess when browser caching is on (the update's own .htaccess does not have it).

Download the new ZIP from your account on license.faruk.bd.

1. Make a backup

AIO Video has no backup button of its own; use your hosting panel:

• The files: cPanel File Manager, select the site's folder, Compress, and download the archive. The uploads/ folder can be very large; the update never writes into it, so you may leave it out.
• The database: phpMyAdmin → Export, or cPanel Backup.

Keep both until the new version has run for a few days.

2. Close the site (optional)

On a busy site, switch on Admin → Settings → Content → Maintenance → Close the site while you work. Visitors see a short "back shortly" page; you, signing in, db_update.php and the cron line keep working.

3. Upload the new files

Upload the ZIP to the folder of the site and Extract it there, letting it overwrite the existing files. The package holds the whole script: the core, every plugin, both themes, .htaccess and install.php. It never holds config.php, installed.lock, your uploads or the cache/ folder.

4. Update the database

Open this address while signed in as an administrator:

https://your-site/db_update.php

The Database update page lists each change it made (... change(s) applied.), or says Everything was already up to date. Back to the admin panel takes you home.

With a shell you can run it there instead; it prints one line per change:

php db_update.php

db_update.php is safe to open as often as you like. Every change is written down when it is done and never runs twice. If one fails, the page shows its name and the reason, and the changes after it wait. Put right what it names - often a database user that is not allowed to change tables - and open the address again; it carries on from where it stopped.

Until it has run, Admin → System status shows the two versions apart (for example 1.14.0 (database at 1.13.0)), and Settings → Updates shows a different Script and Database.

5. Finish off

1. Delete install.php again. It came with the package. While installed.lock exists it only sends visitors to the home page, but it does not belong on a live site.
2. .htaccess was replaced. If Let browsers keep pictures, styles and scripts is on under Admin → Settings → Speed & security, press Save on that tab once: that writes its block back into the new .htaccess. Add again any lines you had put there yourself.
3. Clear the cache with the broom in the panel's top bar. Styles and scripts carry their version in their address, so browsers fetch the new ones by themselves.
4. Look around: Admin → System status, the front page, a watch page.
5. Open the site again if you closed it in step 2.

Plugins and themes

Plugins and themes are part of the package, so they are updated with it.

• A plugin that is switched on brings its own tables up to date the next time it runs.
• A plugin that is new in this version arrives switched off: turn it on at Admin → Plugins.
• Switching a plugin off keeps its data. Switching it on again runs its own set-up once more, which is a good first step when a plugin page looks wrong after an update.
• The two theme folders, themes/default and themes/youtube, are replaced. Theme settings are kept in the database and survive, but changes made inside those folders' files do not. If you want your own version of a theme, copy its folder under a new name and change the copy; for small style changes use Admin → Settings → Your code.

What's new

The notes of the new version are added to the public What's new page (/whats-new) the first time it, or Admin → What's new, is opened after the update. There you can edit an entry, Hide it or Delete it; a deleted entry never comes back.

If something goes wrong

• A white page or errors after the upload. The upload may have stopped part way. Upload and extract the ZIP again, then open db_update.php.
• Every page sends you to install.php. installed.lock is missing. Put it back in the site's folder - an empty file with that name is enough - and never delete it.
• Going back. Restore the file backup and the database backup together. Old files on a database that db_update.php has already changed are not a safe mix.
• Something looks old. Use the broom, then reload the page.