phylaxis

Members
  • Content count

    32
  • Joined

  • Last visited

  1. I wonder if you can't delete it because the hook isn't there. I'm afraid I'm new to this area. Did you at least get past the log-in/ log-out issues?
  2. SatOri, Did you disable/remove the hooks in IPB before turning it off? Also did you delete the settings group under the Hooks tab in the System Settings? I assume what's happening is that you are still seeing log-ins and log outs calling the 'wp-ssoapi.php' file? I'm just throwing out ideas, so sorry if you've already been through all this.
  3. I've been hoping to implement SSO on a project and I purchased it in the IPS Marketplace a while back, but now it seems like the hook has been removed. Is this product no longer being supported? Also strangely any email I send to info[at]invisionpower.com or ahobbs[at]invisionpower.com seems to bounce.
  4. We have noticed something similar. The issue related to this seems to be for us that members added to the SPAM group can still PM our moderators. Is there a way to stop that? I don't see any way of controlling the permissions of Spam Members separately.
  5. I just figured out that my hack above will only effect the main member image and not the thumbnails. So you also need to add the following at line 8070 of the core.php file Change: if( $member['_has_photo'] ) { $member['pp_thumb_photo'] = $member['pp_main_photo']; } else { $member['pp_thumb_photo'] = ipsRegistry::$settings['img_url'] . '/profile/default_thumb.png'; } to: if( $member['_has_photo'] ) { $member['pp_thumb_photo'] = $member['pp_main_photo']; } else if ($member['avatar_type'] == 'upload') { $member['pp_thumb_photo'] = ipsRegistry::$settings['upload_url'] . '/' . $member['avatar_location']; } else { $member['pp_thumb_photo'] = ipsRegistry::$settings['img_url'] . '/profile/default_thumb.png'; } I should have also noted that I haven't fully tested this, so please backup the core.php file before you hack it and if anyone has improvement or alternatives to this hack let me know.
  6. Based on this suggestion I made the following changes to the core.php file for my 3.1.2 install. The idea being that if the user has an Avatar image set, but not a Photo then it will use the avatar image. If neither is set it should use the default image. I haven't fully tested it yet, but it seems to be working on the profile pages, but not in the 'Member' list. at line 8053 in /sources/base/core.php. Change: $member['pp_main_photo'] = ipsRegistry::$settings['img_url'] . '/profile/default_large.png'; to if($member['avatar']) { $dom = new DOMDocument(); $dom->loadHTML($member['avatar']); $avatar_path = $dom->getElementsByTagName('img')->item(0)->getAttribute('src'); $member['pp_main_photo'] = $avatar_path; } else { $member['pp_main_photo'] = ipsRegistry::$settings['img_url'] . '/profile/default_large.png'; }
  7. On a somewhat related topic, do you simply have the ability to password protect a directory based on a members group? What I would like to do is use IP.Subscription to set up paid membership groups and then use that login to allow or disallow access to some various kinds of content. It could include RSS feeds, downloads, etc. I didn't know if maybe combining IP.Content, IP.Download, IP.Subscription was required or not.