> For the complete documentation index, see [llms.txt](https://nearchip.gitbook.io/qwiktest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nearchip.gitbook.io/qwiktest/installation/update-from-previous-versions.md).

# Update from Previous Versions

Follow the below steps carefully to update the QwikTest script. 

1. Take a backup of the previous installation
2. Clean the previous installation
3. Upload and extract the new update file from CodeCanyon
4. Check directory permissions.
5. Check and Fix updates in the Maintenance Settings.

{% hint style="danger" %}
**IMPORTANT NOTE**. You can't update the app from one version to another by skipping the intermediate versions. You have to update one by one sequentially. For Eg. Your app's current version is 1.3.0, and the latest version is 1.5.0. You must upgrade the app to 1.4.0 first, and then you have to update to 1.5.0.
{% endhint %}

### Detailed Update Process

#### Step 1

First things first, back up your files and database of the previous QwikTest installation on your server.

{% hint style="danger" %}
**KINDLY DON'T IGNORE**. Be make sure to back up your files and database before updating the application. So that if anything goes wrong, you won't lose your data.
{% endhint %}

#### Step 2

Goto the QwikTest previous installation directory in the server and delete all the files and folders **EXCEPT** the **`/storage`** folder and the "**`.env file`**". 

{% hint style="danger" %}
Perform this step only after you take the backup of previous files and database. If you delete the /storage folder or the .env file by mistake, upload them from the backup.
{% endhint %}

#### Step 3

Download the zip file from CodeCanyon and extract it on your local system (PC)

1. Goto the "`Upgrade to 1.x.x from 1.x.x`" folder.
2. You will find a zip file named "`upload_this.zip`".
3. Upload this zip file to your server into the previous QwikTest installation directory.
4. Extract the zip file in the same directory.

#### Step 4

Make sure you have 775 permission to the following directories.

* storage/framework
* storage/logs
* bootstrap/cache

#### Step 5

Clear the Browser Cache and Open Browser.

{% hint style="warning" %}
Most browsers cache the CSS and JS files, so **DON'T FORGET** to clear the browser cache. Otherwise, updated functionality may not be visible, or you may face a broken layout/white blank screen.
{% endhint %}

#### Step 6

Now, we need to run migrations. Visit (**<https://yourdomain.com/migrate>**) and click the run migrations button.

![App Migration Page](/files/WnyoH84mUATsBlK68EhG)

Once the migration is successful, proceed to the login and fix updates.

![Migration Successful Page](/files/zn5imEFhn7nlj8Fwx79o)

#### Final Step

{% hint style="warning" %}
After updating the application with the latest files, we must fix some settings. You can do that by performing the below steps.
{% endhint %}

1. Login to the admin account and select `Settings > Maintenance Settings` from the sidebar menu.
2. Then, click on the **Check and Fix Updates** button and confirm the password.
3. That's it! Your application is now updated to the latest version.

![](/files/-MgVcRWCGs55PfB1DZYO)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nearchip.gitbook.io/qwiktest/installation/update-from-previous-versions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.