Announcement

Collapse
No announcement yet.

User not activated error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • User not activated error

    Hi all,
    I've hit a brick-wall in the deployment of a simple two application project. The project is secured at "user" level.

    The database, used during development and deployment, is on a remote server.

    In the development system the applications behaves as expected.

    After deployment to the remote host, once the connection has been configured, the login application appears. Using a valid login and password, i.e. the same one used in the development cycle, I get "Sorry, but user not active".

    Checking the user data table, I see the user is active.

    I've run out of ideas, so any ideas for further trouble shooting?

    Thanks
    The GuiGuy
    ... from Down Under

  • #2
    OK, now I am confused - this is the SC generated snippet from app_login:
    if(count({rs}) == 0)
    {
    sc_log_add('login Fail', {lang_login_fail} . {login});
    sc_error_message({lang_error_login});
    sc_error_exit();
    }
    else if({rs[0][1]} == 'Y')
    {
    [usr_login] = {login};
    [usr_priv_admin] = {rs[0][0]};
    [usr_name] = {rs[0][2]};
    [usr_email] = {rs[0][3]};
    }
    else
    {
    sc_error_message({lang_error_not_active});
    sc_error_exit();
    }
    Why would "if({rs[0][1]} == 'Y')" fail if, as I have confirmed, rs[0][1] contains the char "Y"????
    The GuiGuy
    ... from Down Under

    Comment


    • #3
      I am having this same issue. Any ideas?

      Comment


      • #4
        Don't know if this is a possibility...

        After deploying to Prod, did the database connection bit actually configure okay?

        I get the same "not active" at login app, but I know now that this is because I didn't get the db connection configured properly in the prod environment. All was okay except (when configuring the connection) the very bottom drop-down did NOT list the databases available, even though it indicated success for the test connection.

        Turns out this is because my Prod environment uses PHP 5.5 and SC needs 5.4. If you are also using 5.5 then that could be the cause.

        See http://www.scriptcase.net/forum/show...OD-environment

        Comment

        Working...
        X