Jump to content
You're invited! Join our 4.6 Live Event on ZOOM 6/24 ×

Community

dancingbear

+Clients
  • Posts

    234
  • Joined

  • Last visited

About dancingbear

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dancingbear's Achievements

Community Regular

Community Regular (7/13)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

31

Reputation

  1. it's great that you've added value to your product by including the app. However, for forums which have their revenue stream via ads, it's not added value its detracting value as the app doesn't include the ads. Could the app include code from the ACP adverts feature? If so, it would perhaps be best to be able to flag specific adverts for inclusion in the app. Alternatively, as I also have subscription users who pay to not see the adverts, could the app be usable by a specific user group(s)?
  2. I've discovered what the change is within v4.1.16, and that's that a call to the necessary IPB login code will kill a session you've created in your own code (it didn't do this in previous versions). It was easily rectified in my code by starting the session after verifying the user against IPB. Hope that helps someone.
  3. I've been using the IPS login as verification for access to my website's content manager. IPB have changed the login stuff in v4.1.16. So now my content manager doesn't work, and my websites are stuffed. Until now, I've been passing the following function the username & pw, but what do I do now? Any help hugely appreciated. $IPSLogin = new \IPS\Login\Internal; $IPSLogin->init(); // Catch exceptions here (bad pass/unregistered) // Doesn't check if account is locked/banned etc $member = $IPSLogin->authenticate(array('auth' => $username, 'password' => $password)); if ($member) { $expire = new \IPS\DateTime; $expire->add( new \DateInterval( 'P7D' ) ); \IPS\Request::i()->setCookie( 'member_id', $member->member_id, $expire ); \IPS\Request::i()->setCookie( 'pass_hash', $member->member_login_key, $expire ); return "true"; }else{ return "false"; }
  4. doesn't seem to work for me - nexus 7, v6.01. Has it really been addressed?
  5. yep - as you've told me in the support email you've just sent me. So it's clearly an identified system issue, even tho the cause of me raising it is a numptie user.
  6. or alternatively, IPB should have a way of logging out just the affected user. You might as well be saying "turn it off and back on again". I thought the IT world moved on from that about 20 years ago ... it certainly did where I worked.
  7. It's not impossible, so would you like to tell me where you think I have?
  8. yep. But it's become an IPB issue, because IPB shares the password across different sessions. his 'friend' doesn't now have access to his email (because his mail password isn't shared across sessions), but it's naff-all use for the user to do anything with reseting his own IPB password - because the password is shared across sessions.
  9. I'm not going to be logging everyone out. Using nuclear weapons against a bank robbery isn't anything the sane world does. The sessions table isn't showing any instance of that user logged in, so I've just changed the user password in ACP and hopefully that's locked out the 'friend'. Thanks for that suggestion, and my fingers are firmly crossed. But it does because....? That's how your company have designed the login system.
  10. that's only good if the 'friend' user goes offline, and I have some way of knowing that they have. They're deliberately not going offline so they can stay logged in. You're not saying anything I've not thought of myself, but the problem is it's not a guaranteed solution. I need something that's guaranteed to work.
  11. because the 'friend' user would remain logged in, and if their IP changes they'll have access again. It's not a secure solution.
  12. one of my users inadvertently revealed his password, and now one of his friends is logged in and is posting as him. He's tried changing his password, but the password change appears to be getting passed across to his friend's session, as the friend remains logged in. I've just tried replicating that with a dummy account and two different browsers, and yep, if the password is changed in one browser the other browser stays logged in. Is there some method I can use to log out all instances of that user before I change their password? Or another method I can use to remove the 'friend' from having access to his account?
  13. I can't be sure now, but I think I might have had to set the permissions of my chosen s3 'bucket' to public, but other than that IPB handled it* all automatically. (I say 'handled it', but because of the size of some files it didn't, and IPB support had to advise me to change some of my PHP settings temporarily to enable the transfer of files to s3 to complete) More than that I can't tell you, sorry.
  14. it works fine with my install. View the page source, and one of the top lines should be <meta charset="utf-8"> Also, check your database setup, to ensure that both the database and any tables have "utf8_unicode_ci" as the collation. If it doesn't have that as a collation, you'll need to google for the best way to change it - and note that changing the table collation without also running some code on the table content might not be enough by itself (I forget what I had to do to change mine, but I think some of the content data needed acting on as well as the table setup).
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy