Internal Server Error: profile.firstname / profile.lastname / profile.birthday

[nebulon]

we use humhub internally yes, but I can't seem to hit this issue there.

[randyjc]

I'm trying to exclude cloudron, but I don't have another cloudron instance anymore to test humhub on another server.

If someone could possibly deploy a temporary humhub as well and see if the same errors happens?
I could report upstream if it is

[nebulon]

hm from your support ticket with more logs, it kinda looks like the initial app startup didn't even succeed, as the errors indicate, that basic db columns don't exist.

On a fresh installation, can you ensure that in the app logs you see echo "==> Setup complete" at some point?

[randyjc]

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 complete

But 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

[randyjc]

@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?

[girish]

I have seen this happen before when HumHub installation did not complete properly. I will investigate on a fresh install.

[imc67]

Same issue here, I was surprised that such software was so buggy but hopefully it’s a package bug?

[girish]

@imc67 is yours a fresh install too?

How can I reproduce this?

• Install HumHub
• Login as admin
• Visit /admin/user-profile and observe crash?

[randyjc]

I've reproduced it over here:
https://files.cloudbasis.nl/yAhu8/TImiNulo31.gif

https://files.cloudbasis.nl/yAhu8/VayuVuDe71.gif

[imc67]

@girish yes it was @randyjc thanks for your excellent reproducing! (en goed te zien dat ik niet de enige Nederlander ben :-))

[girish]

@imc67 @randyjc thanks, I can reproduce this one. It's a regression in the package.

[girish]

@imc67 @randyjc Can you please do a fresh installation and check? I have also updated our tests now to check if the migrations completed properly.

[girish]

Unfortunately, I couldn't find an obvious way to update from previous broken installations to a working one.

[randyjc]

Thanks! Will do a fresh install. Just from my understanding, what exactly was causing this?

Again, thanks!

[imc67]

No issue for me, I was just exploring and testing to decide if I bring it to production.

[girish]

@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.

[girish]

@imc67 It's a solid app Any bug is probably is in the package. We use it heavily internally to keep track of everyday progress and general chit chat.

[randyjc]

Confirmed fix btw I’ll close the upstream ticket.