Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
MadMikeyB Posted July 10, 2015 Posted July 10, 2015 Only on a custom skin - I can't figure it out. Guests are being created as members on every visit. This is stopping registrations as the login / sign up bars aren't working.. Tried disabling plugins and everything, nothing. switch to default skin and it is fine. I tried reverting my changes to the userBar template, as I thought I'd flubbed an if / else combo, but nothing changes. Also, why would it be creating accounts? So confusing.. Help!
Daniel F Posted July 10, 2015 Posted July 10, 2015 Are you doing something with the member object?we had many tickets with the same issue, which was caused by siads instant information plugin.
MadMikeyB Posted July 10, 2015 Author Posted July 10, 2015 @Daniel F thanks for the reply. The only thing I've done with the site is create the skin and install some very basic plugins, which I have disabled for testing purposes and this still happens on my custom skin. Not the default even with the plugins.Marcher suggested it might be a missing = in a conditional where guests are checked for, eg:{if \IPS\Member::loggedIn()->member_group_id = \IPS\Settings::i()->guest_group}However I cannot find anything to do with guest_group in the three templates I've modified - navBar, userBar and globalTemplate. All I've done is move the create menu to navBar and move user drop down to the navbar. I can't find any unclosed conditions, and I'm sure the suite would alert me (no?) - I'll keep looking as it does appear to be a skin issue.
Kevin Carwile Posted July 10, 2015 Posted July 10, 2015 It looks like the guest member object is being saved. Do you have any calls to $member-> save () in your custom theme anywhere?
Kevin Carwile Posted July 10, 2015 Posted July 10, 2015 Well, if you really want to track it down, you could put the following code in the beginning part of the save() method inside the ./system/Member/Member.php file and browse around as a guest until you get the backtrace output.if ( ! $this->member_id ) { print "<pre>"; print_r( debug_backtrace() ); exit; }That should give you a backtrace of where in particular the faulty code is saving the guest member object.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.