Upgrading from 1.3 to 1.9.1 the installs goes smoothly and the month view shows up. Logging out I can't log back in.

[JimMlWilson]

I have tried 1.9.10, 1.9.8 and 1.9.1. I had the best luck with 1.9.1. In the case of 1.9.10 and 1.9.8 both installs leave me with an internal server error 500. With 1.9.1 I can complete the upgrade but each time I launch I have a logout button. Clicking on that and I can't log back in.

[42daha]

@JimMlWilson, that sounds similar to one of the issues I had when I upgraded from from 1.2.9 to 1.9.10: login was failing with my existing account. What I found was that the webcal_user table needed to be updated so that the cal_passwd column was a varchar(255) instead of varchar(64). That update was supposed to happen as part of the upgrade process, along with a handful of other sql statements from install/sql/upgrade-*.sql, but did not happen. I did the statements manually to my database, and then I was able to login.

Before I modified the table, webcalendar was attempting to upgrade the hashed password into the database, but the new hash would not fit, so the update statement failed but was not reported.

[JimMlWilson]

I have been holding off on this for now. I may give your suggestion a try early next year. Thank You ! From: Daryl Hanson ***@***.***> Date: Sunday, December 15, 2024 at 12:16 AM To: craigk5n/webcalendar ***@***.***> Cc: JimMlWilson ***@***.***>, Mention ***@***.***> Subject: Re: [craigk5n/webcalendar] Upgrading from 1.3 to 1.9.1 the installs goes smoothly and the month view shows up. Logging out I can't log back in. (Issue #501) @JimMlWilson<https://github.com/JimMlWilson>, that sounds similar to one of the issues I had when I upgraded from from 1.2.9 to 1.9.10: login was failing with my existing account. What I found was that the webcal_user table needed to be updated so that the cal_passwd column was a varchar(255) instead of varchar(64). That update was supposed to happen as part of the upgrade process, along with a handful of other sql statements from install/sql/upgrade-*.sql, but did not happen. I did the statements manually to my database, and then I was able to login. Before I modified the table, webcalendar was attempting to upgrade the hashed password into the database, but the new hash would not fit, so the update statement failed but was not reported. — Reply to this email directly, view it on GitHub<#501 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ2T3URFG5SYUT2YL66J6X32FUGBZAVCNFSM6AAAAABK2OEQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGQ2TEOBXHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>