Internal Server Error: profile.firstname / profile.lastname / profile.birthday
-
Got that line on the root.dev (test humhub)
2023-07-13T14:20:44.000Z ==> Create admin user
2023-07-13T14:20:44.000Z ==> Finish configuration
2023-07-13T14:20:44.000Z ==> Running upgrade
2023-07-13T14:20:44.000Z ==> Setup completeBut I added these tables manually:
ALTER TABLE profile ADD COLUMN lastname VARCHAR(255);
ALTER TABLE profile ADD COLUMN firstname VARCHAR(255);
ALTER TABLE profile ADD COLUMN birthdayVARCHAR(255);And after that I could open the members table. Need to test the rest if that fixes the rest of the problem as well.
Can anyone possibly show their database profiles table?
Mines got firstname, lastname, birthday in it.
But I’m not sure if there’s more or not.EDIT:
Tried to find it in their github repo:
This could possibly all of the colomns?
https://paste.cloudbasis.nl/?e458eab20259eb41#EhytDcgtGdio68qJ7BNLpzqyJEtpLce5BMLimBoDgPJK -
@nebulon I've tested again a new install on a Digital Ocean Droplet (cloudron)
I can reproduce this error, same problem with the missing colomns.When I install it manually without cloudron on a test Digital Ocean vm it works out of the box.
When I install Humhub via a droplet, it also works out of the box.I think there must be something wrong with package humhub inside cloudron?
-
Same issue here, I was surprised that such software was so buggy but hopefully it’s a package bug?
-
I've reproduced it over here:
https://files.cloudbasis.nl/yAhu8/TImiNulo31.gif -
No issue for me, I was just exploring and testing to decide if I bring it to production.
-
@randyjc https://git.cloudron.io/cloudron/humhub-app/-/commit/aec1ea94b82b8ba26ab6504aefecfe0198478a23 was the fix. My understanding
$yii migrate/up --includeModuleMigrations=1
is supposed to run the db migrations of modules but it doesn't. I haven't investigated why. I instead went with whatever the web installer is doing.In HumHub, profile fields etc are implemented as "modules". The user module has the first name, last name, bday fields etc. Since the module db migration never ran, those db fields were never created.