clarkwinkelmann Expected add-on. Nice job. Congratulations...

I translate this plugin into my language, but it doesn't work. I'm uploading the file tr.yml to vendor / flagrow / user-directory / resources / locale. Or should I upload my own language to my directory? I am having such a problem with other flagroW extensions. What should I do?

      wwwn while not a safe method (all files in vendor might be removed/overriden on composer actions) it should work. Make sure your file name matches the extension language ID (it might be tr-COUNTRYCODE). Also make sure you're running in debug mode on your local setup or clear the cache if you're doing that on a production forum.

        6 days later

        Why is there a permanent "Loading" icon on the plugin page?

          Artuu this is just a PHP warning. You should change your PHP configuration to not output warnings (look at the error_reporting configuration)

          The second issue (EmitterException) is because the warning was printed to the page, the remaining of the response can't be sent.

              Artuu that's one way, ideally you should change this in the php config if you can.

              Also I'm really not familiar with that php setting but I believe what you did also suppressed the errors, not only the warnings. There's a way to just disable warnings by passing some constants instead of 0 but I won't copy anything here as I'm never sure how it works 😅

                  clarkwinkelmann To be honest, I do not know either. It's important that it works. I do not have access to the php configuration by the fact that it is web hosting.

                    clarkwinkelmann this is just a PHP warning. You should change your PHP configuration to not output warnings (look at the error_reporting configuration)

                    Suppressing all warnings is not a solution, this is really bad advice...

                        rob006 yes it might not be clear but I was talking about hiding them from page output here, which is an industry standard for web application. No visitor needs to see them anyway.

                        It doesn't mean we shouldn't log them or investigate the underlying issue. If somebody has the time to find out what exactly causes it, an issue or PR is welcome 😉

                            @clarkwinkelmann the issue @Artuu is experiencing, I can duplicate as well and as much as PHP errors aren't as helpful, I learned a thing or two while working on extensions (finally 😉)

                            The error stems from this line more specifically the second parameter in the array_get() function, it's expecting a string and was given an array for the key instead.

                            Not sure how to fix other than just making it an empty string, but to my knowledge of how to read code, I am not even sure what the drawbacks are or what the actual fix for this is 🙁

                              rob006 For hiding errors you should use display_errors and display_startup_errors directives

                              Ooops, my bad then. These were the settings I was thinking about.

                              Ralkage thanks, I'll have a look at it 👍️

                                  7 days later

                                  Hmm, can anyone confirm that it is working? I still cannot see it in the left administration menu...updated to 0.2.0, enabled, cache cleared, no errors...

                                    petr_kazda are you looking for the feature at the right place ? As explained in the first topic this extension adds a page to the front-end of Flarum, and you need to add your own link to it.

                                    FriendsOfFlarum An extension that generates a new url /users that provides a list of users [...] You can add a link to the page using the links extension.

                                    Confusion might come from the users-list extension (not compatible with b8), that adds a user list to the admin panel. The two will soon be merged together.

                                    @luceos might be worth updating the link to the "links" extension in the first post to the FoF fork.

                                        OK, my bad. I really confused those two plugins. Thanks for explanation.