• Resources

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

lakshya the issue persists just at the user's page, but going to your main forum homepage doesn't produce any issue and I can browse discussions normally.

The fact is that FreeFlarum can't fix this issue and you must wait until beta.16. There's nothing we can do for you right now, as we're not developers. Sorry.

      lakshya i am wondering why that is happening exactly. Clicking somewhere shouldn't trigger the UserMetaUpdater. @SKevo can you look at the logs again and maybe trigger the error yourself manually so that you are sure it's that exact problem that is causing all this? We would need the full trace.

          luceos Yes, in sense.........I also don't know why is this happening?

            luceos I pulled the latest logs with that error, so I assumed that it was related to that. Now it doesn't seem to log anything?

            But the console provides these errors:

            You can view this by yourself at the page, as no new logs seem to appear server-side (maybe client-side issue?)

                SKevo No kevo, that's not the case. I am experiencing this even in normal discussions.

                    lakshya well, there are no longer any server-side logs being logged so there should be errors in the JavaScript console. But when I go to the main page (https://bibnom.com) and click on a discussion, I can browse it normally. The only error I see while browsing it this way is:

                    Uncaught TypeError: Cannot read property 'lastNicknameRequest' of undefined
    at checkForApproval.js:18

                    Perhaps the nickname extension is causing this. Again, I am not a PHP dev, so I am not sure about any of this.

                        SKevo at least fof/username-request doesn't take deleted users into consideration. (so not the nickname extension)

                        lakshya do you see any js errors in the browser console?

                              SKevo No, I was/am not using nickname extension. Even then I uninstalled it......but nothing happened.

                                  lakshya No, I was/am not using nickname extension. Even then I uninstalled it......but nothing happened.

                                  My bad, it was related to FoF Username Request, trying to handle non-existent user. Technically not a bug, since the user is "missing" on the page, so it makes sense.

                                  That error is not related to Flarum BTW, your client just blocks some Google scripts.

                                      I disabled the adblock, even then it is not working.................I have also tried on different devices with diff. browsers.........the issue is still the same.

                                      lakshya I don't know what is causing the issue, it is your browser. I don't know what extensions you have enabled, what's your browser type and settings, and since I am not an expert on browsers, I can't help you. But I am sure that Google search might produce some valuable results.

                                          lakshya Tell me if i delete that user........will the issue resolve.

                                              lakshya yes, and I told you that I still don't know what the issue is. All I know is that your browser blocks the Google script resource. I can't deduct much from that, so I can't help you. Remember, this is NOT related to the user profile issue, but to a external Google script that you've put on your forum. Also, keep in mind that monetizing your forum by using Google Ads is prohibited, as stated in our Terms & Conditions, number 9.

                                              lakshya Tell me if i delete that user........will the issue resolve.

                                              Most likely, as it happens just for that specific user. But that seems quite like a radical solution for a rather barerly noticable error to me? I don't think that most of your users browse that user profile normally, so that's what I meant by it not being urgent - you don't need to delete the user. Also, there is a possibility that the user has already been deleted, but as the information came to the database, the connection got cut and the information didn't fully arrive, leaving the user to be bugged or to become a "ghost" user - it is deleted, but not all information related to that user profile was erased, leaving your forum with that error. That's my theory.

                                                    SKevo So, should i delete that user...... may this help