Content
View differences
Updated by Benjamin Bädorf over 5 years ago
### **Environment**:
Your OpenProject Version: 11.1
### **Logs**
\`\`\`
web\_1 | I, \[2020-12-18T16:28:25.852244 #32\] INFO -- : method=GET path=/ format=html controller=HomescreenController action=index status=500 duration=117.84 view=14.78 db=8.15 user=2
web\_1 | I, \[2020-12-18T16:28:27.678923 #32\] INFO -- : method=PATCH path=/user\_settings format=html controller=OnboardingController action=user\_settings status=302 duration=18.42 view=0.00 db=5.16 location=http://localhost:8080/ user=2
web\_1 | E, \[2020-12-18T16:28:27.759850 #32\] ERROR -- : \[current\_user=OpenProject Admin\] PG::UndefinedColumn: ERROR: column "updated\_on" of relation "settings" does not exist
web\_1 | LINE 1: UPDATE "settings" SET "value" = $1, "updated\_on" = $2 WHERE ...
web\_1 | ^
web\_1 | : PG::UndefinedColumn: ERROR: column "updated\_on" of relation "settings" does not exist
web\_1 | LINE 1: UPDATE "settings" SET "value" = $1, "updated\_on" = $2 WHERE ...
web\_1 | ^
web\_1 |
web\_1 | I, \[2020-12-18T16:28:27.772141 #32\] INFO -- : method=GET path=/ format=html controller=HomescreenController action=index status=500 duration=60.70 view=10.27 db=9.07 user=2
\`\`\`
https://github.com/opf/openproject-deploy/issues/4
This seems to highlight a critical issue where some parts of the code still try to access the `update_on` column, which was renamed to `updated_at` for 11.1
### **Steps to reproduce:**
1. Clone the deploy repo
2. docker-compose pull
3. docker-compose up
4. Access the page, try to update some part of the settings
### **Actual Behavior**
The above should work.
### **Expected Behavior**
It throws a 500 error
Your OpenProject Version: 11.1
### **Logs**
\`\`\`
web\_1 | I, \[2020-12-18T16:28:25.852244 #32\] INFO -- : method=GET path=/ format=html controller=HomescreenController action=index status=500 duration=117.84 view=14.78 db=8.15 user=2
web\_1 | I, \[2020-12-18T16:28:27.678923 #32\] INFO -- : method=PATCH path=/user\_settings format=html controller=OnboardingController action=user\_settings status=302 duration=18.42 view=0.00 db=5.16 location=http://localhost:8080/ user=2
web\_1 | E, \[2020-12-18T16:28:27.759850 #32\] ERROR -- : \[current\_user=OpenProject Admin\] PG::UndefinedColumn: ERROR: column "updated\_on" of relation "settings" does not exist
web\_1 | LINE 1: UPDATE "settings" SET "value" = $1, "updated\_on" = $2 WHERE ...
web\_1 | ^
web\_1 | : PG::UndefinedColumn: ERROR: column "updated\_on" of relation "settings" does not exist
web\_1 | LINE 1: UPDATE "settings" SET "value" = $1, "updated\_on" = $2 WHERE ...
web\_1 | ^
web\_1 |
web\_1 | I, \[2020-12-18T16:28:27.772141 #32\] INFO -- : method=GET path=/ format=html controller=HomescreenController action=index status=500 duration=60.70 view=10.27 db=9.07 user=2
\`\`\`
https://github.com/opf/openproject-deploy/issues/4
This seems to highlight a critical issue where some parts of the code still try to access the `update_on` column, which was renamed to `updated_at` for 11.1
### **Steps to reproduce:**
1. Clone the deploy repo
2. docker-compose pull
3. docker-compose up
4. Access the page, try to update some part of the settings
### **Actual Behavior**
The above should work.
### **Expected Behavior**
It throws a 500 error