Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1.8, 2.2.2, 2.3.1
    • Fix Version/s: 2.2.6, 2.3.3
    • Component/s: Web Services
    • Labels:
    • Testing Instructions:
      Hide

      Require web service client creation experience.

      1) Enable mobile service in the Moodle admin
      2) http://docs.moodle.org/dev/Creating_a_web_service_client#How_to_get_a_user_token
      Call login/token.php following the documentation. Checks Moodle logs (in the Moodle admin), you should see the new info about token created for the user.

      Show
      Require web service client creation experience. 1) Enable mobile service in the Moodle admin 2) http://docs.moodle.org/dev/Creating_a_web_service_client#How_to_get_a_user_token Call login/token.php following the documentation. Checks Moodle logs (in the Moodle admin), you should see the new info about token created for the user.
    • Affected Branches:
      MOODLE_21_STABLE, MOODLE_22_STABLE, MOODLE_23_STABLE
    • Fixed Branches:
      MOODLE_22_STABLE, MOODLE_23_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-35242-master

      Description

      I got this e-mail errormessage from my server:

      array (
        'time' => 1346614071,
        'userid' => '5052',
        'course' => '1',
        'ip' => '91.177.224.235',
        'module' => 'webservice',
        'cmid' => 0,
        'action' => 'Maak automatisch een token voor een gebruiker',
        'url' => '',
        'info' => 'User ID: 5052',
      )

      The reason is that the error message is more then 40 chars long (size limit of the action field in the logs database)

      But the point is that log messages shouldn't be translated (this one is in Dutch)

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    12/Nov/12