NewsLoopVersion 1.0.0 · offline copyGuides

Upgrading to a new version ​

This page is for moving an installed site from one NewsLoop version to a newer one. It covers what an update changes in your database and settings, what you do by hand, and how to go back if something goes wrong.

Your version is shown at the top of System in the admin. What changed in each version is in the Changelog.

Before every upgrade ​

  1. Read the notes for the new version in Notes for each version below and in the changelog. They list any step you must do yourself.
  2. Make a backup on the System page (Back up now, with the uploads ticked), and download it. A downloaded copy is safe even if the server fails.
  3. On a busy site, try it on a copy first, such as a copy at staging. in front of your domain, or on your computer.
  4. Pick a quiet time. Between uploading the new files and pressing Update the database, some pages may show errors.

How to upgrade ​

You upload the new version over your site, then finish it on the System page. You need no SSH.

  1. Make a backup and download it (see Before every upgrade).

  2. Download the new version from your CodeCanyon Downloads page, and prepare its newsloop-web folder (in Main_File) as in Preparing the files: composer install --no-dev, then the two npx pnpm@10 commands. You need the new vendor and public/build: the old ones don't match the new code.

  3. Upload the prepared files over your site. Keep these, and don't upload the new version's copy of them:

    • .env (your settings and app key);
    • storage (backups, logs, your translations in storage/app/lang);
    • public/uploads (your pictures and files).
  4. Open System in the admin. When the new files bring database changes, it says "The files are newer than the database". Press Update the database. It runs the database changes, publishes the themes' new pictures and styles, and clears the caches.

    With SSH you can run these instead, in the site folder:

    bash
    php artisan migrate --force
    php artisan newsloop:themes:publish --all
    php artisan optimize:clear

On a VPS, also see Updates and backups for the permissions and the queue worker.

What an upgrade changes ​

Your database ​

Your settings and configuration ​

Your design and files ​

The mobile app ​

After upgrading ​

Going back ​

Notes for each version ​

The steps you do yourself for each version. Database changes run when you press Update the database, so they are only listed when they need your attention.

Version Database .env and settings Steps by hand
1.0.0 First release. — None.

Each new version adds a row here and a section to the Changelog.

Troubleshooting ​