Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Humhub
  3. Internal Server Error: profile.firstname / profile.lastname / profile.birthday

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

Scheduled Pinned Locked Moved Humhub
26 Posts 5 Posters 3.7k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • imc67I Offline
    imc67I Offline
    imc67
    translator
    wrote on last edited by
    #21

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

    girishG 1 Reply Last reply
    0
    • randyjcR randyjc

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

      Again, thanks!

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #22

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

      1 Reply Last reply
      1
      • imc67I imc67

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

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #23

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

        1 Reply Last reply
        1
        • randyjcR Offline
          randyjcR Offline
          randyjc
          wrote on last edited by randyjc
          #24

          Confirmed fix btw I’ll close the upstream ticket.

          1 Reply Last reply
          1
          • apesorgukA Offline
            apesorgukA Offline
            apesorguk
            wrote last edited by
            #25

            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.

            1 Reply Last reply
            0
            • apesorgukA Offline
              apesorgukA Offline
              apesorguk
              wrote last edited by
              #26

              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.

              screenshot-intranettest_apes_org_uk-2025_06_20-21_47_50.png

              1 Reply Last reply
              1
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search