Right now, users who are not allowed to seee the ranking page (as well as guests) are still presented with the link to the ranking page. Shouldn't this link be removed if one can't see the page anyway?

    Pollux That would be great, only problem is that the link to the ranking page is loaded before the user data, so we can't check if the user is allowed to see the link, before it is loaded. I'll see if there is any way around it. If not, I could make it so it pops up the login modal when they try to click it.

        Kyrne

        Pollux That would be great, only problem is that the link to the ranking page is loaded before the user data, so we can't check if the user is allowed to see the link, before it is loaded. I'll see if there is any way around it. If not, I could make it so it pops up the login modal when they try to click it.

        What about adding a class to the body element (like haveRankingAccess) after loading the user data which as a result makes the link to the ranking page element visible?

        body:not(.haveRankingAccess) .item-rankings {display: none}

          Kyrne there are two ways pages are displayed.

          • On direct access or page refresh. This is done using a controller in PHP. You can restrict access from there.
          • On browsing to it via the SPA. This is handled in the Page component, that component knows about the logged in user with app.session.user.

              luceos so he wants the navigation button (under all discussions) to be hidden. That page is normally on first visit. I've found that the page renders out the button, before app.session.user is available. I already have the controller deny access.

                  Kyrne must have missed that, carry on

                  Silently moves away into the darkest corners of the coding realm to talk to the mystic god of Constructor, Destructor, Mutator and others.

                    Kyrne I can't make the extension to use the Spanish locale, I only see the "reflar-gamification.admin.page.convert.help" (tags)
                    Please advice.

                        Sabo did you clear your cache after installing?

                        • Sabo replied to this.
                            6 days later

                            @Kyrne
                            Any chance we can get some of this action? ? (see screenshot at end of post)

                            ♦.# of posts needed before upvote counts?
                            or
                            ♦.# of days as member before upvote counts?

                            Utlimate Victory: Able to set a gamification status to privileges.

                            IE: must have X-Status to do whoopty-woo

                            Imgur

                              Kyrne
                              Yeah maybe that is the correct term.

                              Example:
                              ♦ Must have a rank of Bronze or 8 points to be able to view Rankings♦
                              (a new member would not have the option to view Rankings util that member has created a few posts or replied to a few posts)

                              Not sure how that could be done.

                              My suggestion is mostly about not allowing new members to up-vote until they had achieved some sort of points or reputation. (The blue notification in above image)

                                  0E800 that seems like it would be out of the scope of this ext. It could be made into a more complete package to allow certain things after a certain rep.

                                    12 days later

                                    So apparently my implementation of floodgate doesn't work. I'll fix this ASAP.

                                    Triple post

                                    2.0.0-rc.2

                                    Report any issues you find here.

                                    • Real working spam protection for votes
                                    • Huge refactorings to the vote system
                                      • Votes register to the database faster
                                      • Less system overhead

                                    Please run php flarum migrate in Flarum's root dir after installing this update.

                                    Work hard. Code harder.

                                      2.0.0-rc.4

                                      Report any issues you find here.

                                      • Further optimizations
                                        • Votes register to the database even faster
                                        • Even less system overhead
                                        • Shrank the SaveVotesToDatabase file by ~30 lines
                                      • Votes are now disabled on locked posts
                                      • The points button to show who voted is now properly disabled for users without permission
                                      • Post authors can now see who gave them which vote in the notification.
                                      • Combined DownvoteBlueprint and UpvoteBlueprint into VoteBlueprint
                                      • Combined DownvoteNotification and UpvoteNotification into VoteNotification
                                      • Combined PostWasDownvoted and PostWasUpvoted into PostWasVoted - Now includes $type

                                      It’s not a bug – it’s an undocumented feature.

                                      matteocontrini I have a few more features I want to add, optimize a few more things. There will likely be 1 more rc before release. RC 1 and 2 probably should have been beta.

                                        0E800 that looks nice, I think the votes on left or right side look really good, similar to stackoverflow and reddit ?