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

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

[apesorguk]

Slightly confused everywhere saying this is fixed but I still get this issue when installing the Birthday App.

Invalid database configuration
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'profile.birthday' in 'field list' The SQL being executed was: SELECT *, `user`.*, `profile`.*, DATE_ADD(profile.birthday, INTERVAL YEAR(CURDATE())-YEAR(profile.birthday) + IF((CURDATE() > DATE_ADD(`profile`.birthday, INTERVAL (YEAR(CURDATE())-YEAR(profile.birthday)) YEAR)),1,0) YEAR) as next_birthday FROM `user` LEFT JOIN `profile` ON `user`.`id` = `profile`.`user_id` WHERE (DATE_ADD(profile.birthday, INTERVAL YEAR(CURDATE())-YEAR(profile.birthday) + IF((CURDATE() > DATE_ADD(`profile`.birthday, INTERVAL (YEAR(CURDATE())-YEAR(profile.birthday)) YEAR)),1,0) YEAR) BETWEEN CURDATE() AND DATE_ADD(CURDATE(), INTERVAL 2 DAY)) AND (`user`.`status`=1) ORDER BY `next_birthday` LIMIT 10

But yet this link https://git.cloudron.io/packages/humhub-app/-/commit/aec1ea94b82b8ba26ab6504aefecfe0198478a23 and this post says it's not an issue.

[apesorguk]

Although just to let you know, I found a quicker and easier way of fixing just by adding the Birthday Field to a category called Profile Information fixed it.