View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005573 | SOGo | GUI | public | 2022-08-12 17:31 | 2022-08-15 08:22 |
| Reporter | BrotherJ | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | AMD64 | OS | Debian Bullseye | OS Version | 11 |
| Product Version | 5.7.0 | ||||
| Summary | 0005573: Login after upgrade no longer possible | ||||
| Description | After upgrading from a working SOGo 5.0.1 to SOGo 5.7.0, I can no longer log in with my user. After entering the login and sending, the Sogo login mask appears again. Greetings | ||||
| Tags | No tags attached. | ||||
|
Did you do the SQL Updates from /usr/share/doc/sogo |
|
|
Thanks Jan for your feedback. No, I didn't do the SQL Updates from /usr/share/doc/sogo. Because I wasn't aware of the existence of these upgrade files. Unfortunately, I hadn't found any direct documentation on upgrades. But now the login works again. I do have one additional question. The MySQL dumps of the SoGO-DB seem very small to me, given that the calendar contains a large number of appointments. Where does SoGO generally store these appointment entries? |
|