Did Kyrne Shout and Neon Chat have duplicate variable names?
When they start at the same time, they cannot be displayed normally.

"If you don't see the user you are looking for, they don't have private messaging setup." message is truncated on mobile. And it is a little hard to translate this message to fit container even for desktops.

    6 days later

    @Kyrne don't think I have the latest version, but on 0.1.11 I the sign up model won't redirect after clicking the register button even though the request seems to went through (refreshing the page log you in). I think that is probably the root cause of this too

      15 days later

      Thought I would update as I am getting the same issue as @huuduy216.

      Flarum: 0.1.0-beta.13
      PHP: 7.3.21
      Browser: Firefox

      Fresh install; only other 3rd party extensions installed are Verified Emails & FoF Categories.

      Steps to replicate:

      • Attempt to make an account.
      • Attempt to log in with an already registered account.
      • Log-in modal just spins indefinitely.
      • Manually refreshing the page shows you as "logged in" with last successful account.
      • Disabling the extension (++ NGINX restart) allowed users to be created/log in as expected.

      Nothing held in console log for error details as nothing appears to be erroring. It just doesn't appear to be reloading the page / finishing the log-in modal.

      Have tested on other browsers and it seems to work fine. Seems to be an issue with FireFox.

      Let me know if you want anything else hunted out Kyrne

          ChrisAppleby I'm still not able to reproduce this at all. Can you provide a website address as well as your php flarum info output?

            Kyrne There seems to be an issue with the assets here...
            production.ERROR: InvalidArgumentException: File not found at path: /opt/flarum/vendor/kyrne/shout/js/dist/admin.js in /opt/flarum/vendor/flarum/core/src/Frontend/Compiler/Source/FileSource.php:27

                iPurpl3x whoops! Must've direct copied from my "working" version which has a different path. Go ahead and update again.

                  @Kyrne do you think we need SSH access/ ability to execute scripts or cron jobs to get this working?

                    Gatsu please enable debug mode, reproduce, the click the "debug" button on the red popup.

                        Kyrne I solved with this, but now I have a new problem.

                        I can see the conversation popup but not my user. They don't see the conversation link.

                            Gatsu Make sure users have permission to start conversations.

                            Can you also share how you solved the issue?

                                Kyrne How? In permissions I don't find any entry related to your extension.

                                I solved it by editing PMuser to 0 in phpmyadmin.

                                    Gatsu there should be a entry in there. I'll verify later.

                                    Careful about editing anything in the database related to shout when not directed by myself. Shout is a fully featured cryptographic suite and even small changes can cause subtle problems that can lead to security holes.

                                      0.2.0

                                      • Fixed (hopefully) all Firefox issues. It was so broken on Firefox I'm confused how any of you used it at all on that browser.
                                      • Removed 50 conversations limit. When a user nears this limit, they will be prompted to generate new keys on their end.
                                      • Prefixed all routes with /shout

                                      Note: I will be mostly unavailable in the near future as I will be moving and starting school. Please test and report any issues to me ASAP!

                                        • [deleted]

                                        • Post #214

                                        Kyrne There is an issue with the latest release. Nothing reported in the logs, but I see the below in the console.

                                        Downgrading to 0.1.9 resolves the error and the site loads properly.