• Resources
  • Free Flarum hosting on an expert platform by FreeFlarum.com

I have a weird glitch with private discussions. When I send them, it hangs there, I have a "Something went wrong" error but the message was actually sent. Is it just me?

    arteteco Connection to tcp://smtps.aruba.it:465 Timed Out
    This seems like an issue in your mail settings. Byobu then can't send the mail notification when a new discussion is started with you. Please, double-check them and let me know if that helped. If not, I can reset them for you.

      SKevo Thanks, the conf was actually wrong, I had tls instead of ssl. Seems like it's solved now, dummy me!

      20 days later

      FreeFlarum beta.14 update status


      Hello folks! It's been some time since we've updated our beta.14 update to-do issue. Flarum beta.14/beta.14.1 was around for quite some time now, and it would be a pity if we wouldn't update. Actually, we are going to update very soon, we just needed to give extension developers some time to update their amazing extensions 🙂

      First of all, I want to thank the awesome Flarum team & all the developers that worked really hard during this update & extensions update. I am really happy to see such a strong and amazing community. Us updating wouldn't be possible without your help with fixing some bugs I've found during the testing, so thank you very much for that!

      Information you should know:

      And now for the update itself. Yesterday, I spend quite some time (R. I. P. Saturday) testing the beta.14 update.

      I've setup a testing forum independent to other FreeFlarum forums, but with setup equal to other forums (there were some small downtimes at our service sometimes, so I want to apologize for that). This was a very important step, because it allowed us to debug and squash some bugs before we update all forums for real. I've ran through every single extension we've got at FreeFlarum (plus, a few new ones you've been requesting for quite some time now ;D) and took a notes of what bugs occurred during the testing, what needs to be reported, changed or (sadly) removed.

      Speaking of removals, some extensions sadly won't make it to this update (yet):

      Those are a lot of incompatible extensions... But don't worry, some of them got replaced with updated versions. They will all come back when they become compatible. We promised to update when 2/3 of the extensions are compatible, so let's go!

      Also, don't be upset, we've got a few new ones in our disposal too:


      We're aware that we've removed quite a lot of extensions in this update. But we have to move forward. All of them will come back when compatible versions become available, so don't worry 🙂

      Other things you might need to know

      1. We will put a notice about the update in the header of every forum with link to this post. This should disappear as soon as your forum updates.
      2. There might be downtime during the upgrade. Do not panic, we will try to resolve that as quickly as we can.
      3. Your data won't be deleted. You can re-enable the extensions and continue discussing ;D

      We will try our best to ensure that everything goes smoothly. The update might take from 2 - 24 hours, depends on the forum amount to upgrade. For now, sit tight and do what you do best - you all deserve a break ;D

      If anything goes wrong, we will try to fix it as fast as we can. We've got backups, obviously, so don't worry 😃

      Update, as of 12:34

      So far, everything is going smoothly and we're currently letting our system to synchronize the files, this will take some time. There shouldn't be any downtime and your forum should be updated automatically. If a problem appears, just reply to this thread 👍

      After nearly 6 hours, every forum has been successfuly updated to beta.14.1. Remember that if you've got any issues, please report them accordingly.

      I never imagined it to go this smoothly, with almost no downtime. Good job to all of you for being patient, for developers updating their extensions and the Flarum team for providing such an amazing software!

      Enjoy new features everyone! 👏 👏 👏

      Congratulations @SKevo with the smooth result, 100% due to your careful preparations. And thanks on behalf of all FF users, who can now enjoy the greatest Flarum so far!

      In addition, two extensions have been added to support Google and LinkedIn OAuth, and the Money extension is now back too after a fast bug-fix from the developer!

        SKevo i cant login my forum for hours. When i login an error page appears "An error occurred while trying to load the page."

          xdass could you try logging in now to see if it works?

            SKevo yes i can login now. Thank you for fast answer and fix.

            Is it too early to do bug report?

            The profile fields, added with Masquerade, do not display properly.
            Instead of my telegram handle, for example, I see Telegram: function(){return t.content()}

              arteteco please, report this issue here, I am not sure if it's FreeFlarum or Masquerade related, so if you tell me your forum name I'll try to fix it, just in case.

                Gommzy1 The German language pack that you used, has been abandoned and replaced by kakifrucht/flarum-de. If you enable this extension in your admin area, everything will work.

                SKevo thanks, I will. At the moment for some reason I can't access my profile, it just keeps loading. This only happens on one forum (I have another one) and just to me, the others can access their profile just fine. I am also the only one who filled masquerade fields, may that be something useful?

                In the Console I have this following error repeated:

                mount-redraw.js:15 TypeError: Cannot read property 'onbeforeupdate' of undefined
                    at render.js:929
                    at f (render.js:407)
                    at h (render.js:302)
                    at render.js:477
                    at f (render.js:416)
                    at h (render.js:302)
                    at render.js:477
                    at f (render.js:416)
                    at render.js:488
                    at f (render.js:419)

                I'm trying to figure out what's wrong, forum is forum.asnuaps.it in case, I'll report back
                Thanks!

                Generally speaking that error occurs after something else breaks mithril state. What's the first JS error you see?