wrongecho JosephWithCOR Probably not. We moved database updates to be in front of code updates because it's generally better that you get the latest DB before getting any more code..
JosephWithCOR johnny So it sounds like The database update was performed but failed so they may have refreshed the screen. and it continued to fail, this time on the first entry which we was creating the login folder id field in the logins table. That is exactly what I did.
E-werd johnny I just did a manual pull and I was able to go through with the database updates through the site. It appears to be good now.
klockemy johnny I logged in this morning and saw the updates but was forced to upgrade the DB and not see the "Update App" buttons. Did a manual git pull then ran the DB updates. All is well.
JosephWithCOR Not quite. My instance at work the ticket_status column had 8 'In-Progress'. To resolve I had to drop the login_folder_id column and set the ticket_status 'In-Progress' to 2. After I did this I was able to cycle through the database updates.
wrongecho JosephWithCOR I also had to do this on PR Review. We had a ticket stuck in the old 'Working'.