Sessions Restricted to One Subdomain

  • Resolved Ryan Bayne

    (@ryan-bayne)


    7 years, 2 months ago

    When we switch language in WPML we are taking to the login page and it appears as if we aren’t logged in. When Gaurd is disabled everything works fine.

    This problem is not a bug in Gaurd though because when TwitchPress is disabled we can switch language just fine. So we have a sort of triangle of plugins that ruin the users experience.

    The conflict really begins with the new TwitchPress plugin or one of its extensions i.e. TwitchPress Login Extension.

    I just wondered if someone could give a hint as to what would get in the way of the users session continuing when the subdomain changes?

    Could it be TwitchPress Login Extension (login via Twitch) hooking into WP login functionality too early or too late – resulting in the users session missing database values or cookies?

    It is my plan to build a common package of plugins to recommend to Twitch streamers. WPML, Guard, and TwitchPress are essential so any help to explore this problem is greatly appreciated. I’m not being paid to resolve this and that the work I do is provided on the www.remarpro.com repo.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Paul

    (@paultgoodchild)

    Very hard to say here what’s going on with subdomains.

    I took a cursory look at the TwitchPress Login code and while I’d need to spend longer, it appears they’re not really hooking into the WordPress login and firing off the standard WordPress hooks. I can’t say 100%.

    I’m not sure why the 3 aren’t playing together, but you might have to test disabling the user management and/or Login Protection modules to see what exactly isn’t working.

    This is really hard to guess… Shield uses standard WordPress API (hooks/filters) and if the plugin doesn’t use that but still authenticates the users, this might by-pass certain Shield processes that are necessary.

    Plugin Author Paul

    (@paultgoodchild)

    I’m going to mark this as ‘resolved’, but please feel free to come back to us if you have any further questions/suggestions about this.
    Thanks!

    Thread Starter Ryan Bayne

    (@ryan-bayne)

    I was still looking into it and I don’t think the issue is with Shield anyway.

    Thanks for your time.

    Should anyone have a similar issue with a login related plugin and WPML. Look at WPML sessions and how language switching using WPML itself uses a range of methods to ensure cookies are generated for each subdomain.

    It seems a login plugin needs to maintain those cookies using WPML functionality. Shield only appears to interfere because there is an issue with the user’s session when moving between sub-domains – I think!

    Plugin Author Paul

    (@paultgoodchild)

    I’d been keen to hear the technicals on what you discover, and so if there’s further additions we can make to Shield to cooperative with other 3rd party plugins, we’d be happy to do that. We’ll be adding increasing support for 3rd party plugins in our pro version of the plugin that in the works, so this would be a sensible addition.

    Cheers!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Sessions Restricted to One Subdomain’ is closed to new replies.