<p>If you restore from a 3.0.36 database backup, then update to the latest Craft 3.1 release (currently <a href="https://github.com/craftcms/cms/blob/develop/CHANGELOG-v3.md#3122---2019-01-19" rel="nofollow noreferrer">3.1.2.2</a>, this shouldn't be an issue anymore.</p>

CC BY-SA 4.0
2019-02-07T19:23:59.947Z
Unfortunately I don't have a backup for the database at this point.  Any other options before I blow this up and start over?  Thanks!
fodney
CC BY-SA 4.0
2019-02-08T03:23:32.670Z
Yeah... nothing comes to mind without being able to restore the database, unfortunately.
Brad Bell
CC BY-SA 4.0
2019-01-20T00:19:16.433Z
2019-01-20T00:19:16.433Z
Brad Bell
<p>I just updated to 3.1 and I'm getting the php error:</p>

<p>PHP Notice – yii\base\ErrorException</p>

<p>Undefined index: settings</p>

<p>It probably has to do with the Cheat Sheet plugin.  I deleted that folder in the vendor directly but no luck.</p>

<p>I can send along the link showing the errors.</p>

<p>Thank you!</p>

CC BY-SA 4.0
2019-01-17T13:29:54.247Z
Anyone have any suggestions on this?
fodney
CC BY-SA 4.0
2021-02-08T08:21:17.843Z
Did you try to rename the original vendor folder to say vendor-old and do a composer install ?
MisterMike
<php><error-message><upgrades>
Getting PHP Error on upgrade from 3.0.36 to 3.1
# Getting PHP Error on upgrade from 3.0.36 to 3.1

(Asked by: username_0 on 2019-01-15)

I just updated to 3.1 and I'm getting the php error:

PHP Notice – yii\base\ErrorException

Undefined index: settings

It probably has to do with the Cheat Sheet plugin. I deleted that folder in the vendor directly but no luck.

I can send along the link showing the errors.

Thank you!

**Tags:** php, error-message, upgrades
> **Comments:**
> **username_0**: Anyone have any suggestions on this?  
> **username_1**: Did you try to rename the original vendor folder to say vendor-old and do a composer install ?  

---

## 1 answers

### Answer by username_2 on 2019-01-20. Score: 1

If you restore from a 3.0.36 database backup, then update to the latest Craft 3.1 release (currently [3.1.2.2](https://github.com/craftcms/cms/blob/develop/CHANGELOG-v3.md#3122---2019-01-19), this shouldn't be an issue anymore.

> **Comments:**
> **username_0**: Unfortunately I don't have a backup for the database at this point.  Any other options before I blow this up and start over?  Thanks!  
> **username_2**: Yeah... nothing comes to mind without being able to restore the database, unfortunately.  

---

