current_version; $fetch_ok = $updates->result === 0; // Commits sitting between this working tree and the remote branch. Fields are separated // by \x1f rather than having git build the table markup, because a commit subject comes // from outside this install and used to reach the page as unescaped HTML. $pending_commits = []; $git_log = shell_exec("git log HEAD..$remote_ref --pretty=format:'%h%x1f%ar%x1f%s'"); foreach (explode("\n", trim((string) $git_log)) as $commit_line) { if ($commit_line === '') { continue; } $commit_fields = explode("\x1f", $commit_line, 3); if (count($commit_fields) === 3) { $pending_commits[] = $commit_fields; } } // version_compare, not > - "2.6.10" is less than "2.6.9" as a plain string comparison, so // the plain comparison silently stops offering database updates once a minor reaches 10. $db_update_available = version_compare(LATEST_DATABASE_VERSION, CURRENT_DATABASE_VERSION, '>'); $app_update_available = !empty($pending_commits); ?>

Update

Cannot reach the Git remote
ITFlow updates itself with Git, so nothing below is current until this is fixed. output)) { ?> 
output)) ?>
Check that Git is installed, that the remote is reachable from this server, and that the web server user can write to the ITFlow directory. The forum can help - include your PHP error log and the output above.
Release
Branch
Not the release branch
Database
→
Commit

You are up to date

Everything is going to be alright.

Do not update without a backup
A VM snapshot is the safest option - other methods are covered in the docs. Read the changelog first: some releases need manual steps, and this page will not do them for you.

Both are pending. Update the application files first - they bring the database migrations that the second step then applies.

Application files

commit behind .

Update App Force Update

Update App runs git pull. Force Update discards every local change and resets the files to - use it only when a normal update will not apply.

Database

Schema is at and this code expects . Parts of the app will error until this is applied.

Update Database

A large instance can take a minute or more. If it fails part way it stops without advancing the recorded version, so it is safe to run again after fixing the cause.

Pending commits
Commit When Description