Jump to content

LemonGrenade

Clients
  • Joined

  • Last visited

  1. I actually validated that member via admin in the end. So to test it, I used a different IP and email address, registered and received the validation email. It then gave me the member validated via email confirmation within members in admin. So it seems to work ok. But, on both the screen pictured and on clicking the email and getting the Awaiting Approval screen, it goes into a loading loop and loads the page over and over, so the footer is flashing. This was on both edge on desktop and Safari on iPhone. Clicking continue as guest loads the homescreen fine again.
  2. Thanks @Marc It's hard to provide an example other than a copy of the email sent. It seems that he clicked the validation link but then received the message that he needed to validate his email address to view the board via the link. If another validation link was issued, would that mean he would have to click on that newer one, and the original/older one would be invalid? I'm just trying to rule out any issue. I think I'll try and create a test user from another IP and email and see if I can replicate it.
  3. I have noticed since 4>5 that more members seem to be still sitting in validation. We have user and admin validation set up. I was just emailed from a member who clicked the validate my account on his email after registering, but then on accessing the board gets the 'you must validate your email address' message. At first, I assumed there may have been an issue with new members getting the validation email, but after his message, I think maybe they are clicking but not being validated. I can't be sure it's a bug with 5, but worth looking into as haven't had an issue with validations before.
  4.    LemonGrenade reacted to a post in a topic: v5 Avatar in Nav Bar
  5. LemonGrenade posted a post in a topic in Feedback
    Works but on mobile view, and it's only the desktop view I was looking for. 😀
  6.    LemonGrenade reacted to a post in a topic: v5 Avatar in Nav Bar
  7. LemonGrenade posted a post in a topic in Feedback
    I am adding it via theme editor - custom CSS, and not seeing any change?
  8. LemonGrenade posted a post in a topic in Feedback
    Thanks, but strangely it isn't doing a thing when I add it as custom CSS on desktop.
  9. LemonGrenade posted a post in a topic in Feedback
    It wasn't that one.
  10.    LemonGrenade reacted to a post in a topic: v5 Avatar in Nav Bar
  11. LemonGrenade posted a post in a topic in Feedback
    Is it this one to adjust avatars in posts and profiles only?
  12.    Maxxius reacted to a post in a topic: Invision Community 5.0.6 Released
  13. Just a heads up, the email to notify update only triggers when you click check updates in admin. It might be just Betas this is on, but pretty sure it's always done it since 4>5.
  14.    LemonGrenade reacted to a post in a topic: Invision Community 5.0.6 Released
  15.    LemonGrenade reacted to a post in a topic: Invision Community 5.0.6 Released
  16. Is that even better than beta 2?
  17.    LemonGrenade reacted to a post in a topic: Invision Community 5.0.5 Releases
  18.    LemonGrenade reacted to a post in a topic: Invision Community 5.0.6 Released
  19.    Matt reacted to a post in a topic: Invision Community 5.0.6 Released
  20. Ignore the above, I just uploaded a fresh file from client area and all sorted. It must be where I edited it for the fix before.
  21. Is it giving me an error for permissions on the upgrade sitemap file? Any ideas?
  22. Hi Derek, I was having problems with ads not filling the spaces set, which I thought might've been the issue, as all the other areas were fine. It seemed to be more focused on ads within topics after x posts. While a lot of the time, these ads are now showing, I am still seeing around a 50% reduction. I am trying to determine whether they are not loading quickly enough or merely lower traffic/less revenue moving into Q2, and nothing connected to upgrading. I have also noticed the quality of ads can be poor, which again, could be adding to it.
  23. Had the same error and @James Myddelton fix worked for me too.