ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Member Groups Encounter Login Error

March 15, 2011 6:58pm

Subscribe [3]
  • #1 / Mar 15, 2011 6:58pm

    Geoff Towle

    330 posts

    This question may be related to a resolved thread.

    We have created a number of Member Groups.  When I attempt to login as a member, via the system login page, I get a “An Error Was Encountered” Message.  However, if I delete everything after ~/system/ in the address bar and hit return, I’m logged in to the CP.

    I tried the settings Ingmar suggested in the above thread, but that didn’t change anything.

    Any ideas?

  • #2 / Mar 16, 2011 12:38pm

    Sue Crocker

    26054 posts

    Hi, Geoff. Can you tell us more about the domain you’re working with? Has it finished replicating? Can you tell us which version/build of EE1.x you’re using? See EEWiki:// HowTo Determine My EE Version

  • #3 / Mar 17, 2011 5:17pm

    Geoff Towle

    330 posts

    Hi Sue.  EE version 2.1.1.  EE is installed on a load balancer, behind a VPN (company intranet).  Everything else works fine.

  • #4 / Mar 18, 2011 1:33pm

    Lisa Wess

    20502 posts

    Hi, Geoff,

    The people attempting to login are internal, or coming externally, to the site?

    Have you played at all with turning off Secure Forms in Admin > System and Security preferences?  Or even perhaps not requiring an IP? Normally that would lead to the “Not Authorized” error but it is worth a shot anyway.

    The error you posted as well - that’s the exact error?

    We’ll work with you on this, but definitely need a bit more information along the way.

    Thank you!

  • #5 / Mar 18, 2011 7:52pm

    Geoff Towle

    330 posts

    Hi Lisa,

    I figured it out.  Structure is installed, and we had the Redirect to Structure on login and publish options set to “yes.”  Since these member groups that we created do not have access to Structure, they were getting that error.  Turning those settings to “no” solved the problem.

    Case closed.

    Thanks!

  • #6 / Mar 20, 2011 4:32pm

    Greg Salt

    3988 posts

    Hi Geoff,

    Thanks for the update and glad that you got this figured out.

    Cheers

    Greg

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases