<p>I've run into this issue myself with Craft version: 2.6.2962.</p>

<p>The line in question is expecting a column from the database called "releaseDate".
In my case, that column no longer exists. It might have gotten dropped or lost with one of the updates, I am not sure.</p>

<p>A short-term solution would be to edit that line of code and pass in some different value.</p>

<p>In my case, I changed the line to:</p>

<pre><code>$row['releaseDate'] = DateTime::createFromString($row['dateUpdated'], null, false);
</code></pre>

<p>And to clarify, looking at the changelog, it seems they are in the process of tweaking the craft()->releaseDate() function call.</p>

<p>Update 03/06/2017:
It appears that my code-base was outdated with the version in my database. I updated to the latest version of craft and that line that I edited above is now gone.</p>

<p>My question to you: Is your craft version up to date?</p>

CC BY-SA 3.0
2017-03-07T12:28:04.137Z
Thanks for the help sturakov. I updated to the latest 2.6.2966 and this began happening, although my live site works perfectly and doesn't show this error. This only seems to happen on my local .dev version.

I also can't find the:

`$row['releaseDate'] = DateTime::createFromString($row['releaseDate'], null, false);` 

from line 500.
larnera1
CC BY-SA 3.0
2017-03-07T22:46:53.303Z
Just to verify, you're saying you updated to the latest version and the error is still happening? And no problem, happy to help.
sturakov
CC BY-SA 3.0
2017-03-08T12:02:33.610Z
Yep, I've updated, but my local version is getting this error. The live site is working fine. Quite strange, not sure what to do?
larnera1
CC BY-SA 3.0
2017-03-08T16:42:50.263Z
Yeah, definitely strange. Are you getting the same error message even though the line is missing from that file? If so, that makes me think there's some sort of caching going on. I'm not sure what you're development environment is like, but if you give me some details, we might be able to narrow it down.
sturakov
CC BY-SA 3.0
2017-03-09T10:40:05.147Z
Yep, I'm getting to the same error message. I've tried to find that line in Sublime, but doesn't seem to exist. I'm running Mamp Pro 3.5.2, PHP 7.0.8 and Craft 2.6.2966 according to `info.php` in the `app` folder.
larnera1
CC BY-SA 3.0
2017-03-09T22:13:02.997Z
That is really, really strange. I wonder if it's being cached somehow? Have you tried restarting the system / web-server?
sturakov
CC BY-SA 3.0
2017-03-10T10:46:47.380Z
I have, but it doesn't seem to work. I'm committing to GitHub and the local dev version is working on other computers. I've tried deleting my files and re-cloning my repository again, but it seems to be stuck with this issue. When I initially installed the `2.6.2966` update it didn't recognize the changes on the local version, but when I pushed the changes the live version updated. My local one seems to be stuck and I can't work on the site.
larnera1
CC BY-SA 3.0
2017-03-11T00:32:08.363Z
Well that really sucks.
Does your local MAMP install rely on having your files in the web-server path?
For example, if you develop say locally, on your main machine (assuming OS X), do you then have to upload them to the web-server directory?
sturakov
CC BY-SA 3.0
2017-03-14T08:58:48.907Z
Not sure I quite understand, how do you mean sorry? My local site gets pushed to GitHub and then deployed to the live environment via DeployBot. Not sure that helps? Thanks again for helping out.
larnera1
CC BY-SA 3.0
2017-03-14T21:59:41.593Z
All good. Maybe we'll figure it out some day haha :).

Your deployment makes sense...
How do you use MAMP?
Like, do you edit your files, hit save, and then the changes show up when visiting a URL from your browser?
Or do you have to upload your changed file to a local web-server directory?
sturakov
CC BY-SA 3.0
2017-03-17T09:30:32.917Z
That's how I do it, yes. I've updated my .dev with the production database file as well.
larnera1
CC BY-SA 3.0
2017-03-17T20:27:43.813Z
I'm not sure what could be the problem at this point. If you want, I could attempt to help you through like a GoTo meeting or something, so I can see what you're seeing. Might be able to debug and figure out the problem that way.
sturakov
CC BY-SA 3.0
2017-03-27T13:43:07.260Z
Hello sturakov, thanks again for all the help. Turns out I'd pointed my .dev in Mamp to an older version of the files. Really sorry to have wasted your time, thanks for your patience. All working now, very embarrassing!
larnera1
CC BY-SA 3.0
2017-03-28T04:28:31.970Z
Hahaha, that's awesome! Glad you figured out what the issue was! And no worries, glad we finally got some closure. Wish you well in the future!
sturakov
CC BY-SA 3.0
2017-03-06T22:00:28.657Z
2017-03-06T22:16:17.797Z
2017-03-06T22:16:17.797Z
sturakov
<ol>
<li>Backup your DB.</li>
<li>I updated the CMS on my live site to the newest version. </li>
<li>download the newest version of Craft and replace <code>craft/app</code> with the new <code>craft/app</code></li>
</ol>

CC BY-SA 3.0
2018-02-02T22:59:50.077Z
2018-02-12T15:48:42.797Z
2018-02-12T15:48:42.797Z
Jeff Irwin
<p>I'm getting this error: </p>

<pre><code>Undefined index: releaseDate in craft/app/etc/behaviors/AppBehavior.php(500)

Line 500: $row['releaseDate'] = DateTime::createFromString($row['releaseDate'], null, false);
</code></pre>

<p>Is there anything I can do to fix this?</p>

<php><admin><updating>
How do I fix PHP Notice - Undefined index: releaseDate?
# How do I fix PHP Notice - Undefined index: releaseDate?

(Asked by: username_0 on 2017-03-05)

I'm getting this error: 
Undefined index: releaseDate in craft/app/etc/behaviors/AppBehavior.php(500)

Line 500: $row['releaseDate'] = DateTime::createFromString($row['releaseDate'], null, false);

Is there anything I can do to fix this?

**Tags:** php, admin, updating

---

## 2 answers

### Answer by username_1 on 2017-03-06. Score: 3

I've run into this issue myself with Craft version: 2.6.2962.
The line in question is expecting a column from the database called "releaseDate".
In my case, that column no longer exists. It might have gotten dropped or lost with one of the updates, I am not sure.
A short-term solution would be to edit that line of code and pass in some different value.
In my case, I changed the line to:
$row['releaseDate'] = DateTime::createFromString($row['dateUpdated'], null, false);

And to clarify, looking at the changelog, it seems they are in the process of tweaking the craft()->releaseDate() function call.
Update 03/06/2017:
It appears that my code-base was outdated with the version in my database. I updated to the latest version of craft and that line that I edited above is now gone.
My question to you: Is your craft version up to date?

> **Comments:**
> **username_0**: Thanks for the help sturakov. I updated to the latest 2.6.2966 and this began happening, although my live site works perfectly and doesn't show this error. This only seems to happen on my local .dev version.  I also can't find the:  `$row['releaseDate'] = DateTime::createFromString($row['releaseDate'], null, false);`   from line 500.  
> **username_1**: Just to verify, you're saying you updated to the latest version and the error is still happening? And no problem, happy to help.  
> **username_0**: Yep, I've updated, but my local version is getting this error. The live site is working fine. Quite strange, not sure what to do?  
> **username_1**: Yeah, definitely strange. Are you getting the same error message even though the line is missing from that file? If so, that makes me think there's some sort of caching going on. I'm not sure what you're development environment is like, but if you give me some details, we might be able to narrow it down.  
> **username_0**: Yep, I'm getting to the same error message. I've tried to find that line in Sublime, but doesn't seem to exist. I'm running Mamp Pro 3.5.2, PHP 7.0.8 and Craft 2.6.2966 according to `info.php` in the `app` folder.  
> **username_1**: That is really, really strange. I wonder if it's being cached somehow? Have you tried restarting the system / web-server?  
> **username_0**: I have, but it doesn't seem to work. I'm committing to GitHub and the local dev version is working on other computers. I've tried deleting my files and re-cloning my repository again, but it seems to be stuck with this issue. When I initially installed the `2.6.2966` update it didn't recognize the changes on the local version, but when I pushed the changes the live version updated. My local one seems to be stuck and I can't work on the site.  
> **username_1**: Well that really sucks. Does your local MAMP install rely on having your files in the web-server path? For example, if you develop say locally, on your main machine (assuming OS X), do you then have to upload them to the web-server directory?  
> **username_0**: Not sure I quite understand, how do you mean sorry? My local site gets pushed to GitHub and then deployed to the live environment via DeployBot. Not sure that helps? Thanks again for helping out.  
> **username_1**: All good. Maybe we'll figure it out some day haha :).  Your deployment makes sense... How do you use MAMP? Like, do you edit your files, hit save, and then the changes show up when visiting a URL from your browser? Or do you have to upload your changed file to a local web-server directory?  
> **username_0**: That's how I do it, yes. I've updated my .dev with the production database file as well.  
> **username_1**: I'm not sure what could be the problem at this point. If you want, I could attempt to help you through like a GoTo meeting or something, so I can see what you're seeing. Might be able to debug and figure out the problem that way.  
> **username_0**: Hello sturakov, thanks again for all the help. Turns out I'd pointed my .dev in Mamp to an older version of the files. Really sorry to have wasted your time, thanks for your patience. All working now, very embarrassing!  
> **username_1**: Hahaha, that's awesome! Glad you figured out what the issue was! And no worries, glad we finally got some closure. Wish you well in the future!  

---

### Answer by username_2 on 2018-02-02. Score: 1

1. Backup your DB.
2. I updated the CMS on my live site to the newest version.
3. download the newest version of Craft and replace `craft/app` with the new `craft/app`


---

