Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.6
    • Component/s: Web Services
    • Labels:
    • Testing Instructions:
      Hide

      Testing:

      Use this client: https://gist.github.com/jleyva/6669774
      The curl.php file is here: https://github.com/moodlehq/sample-ws-clients/blob/master/PHP-REST/curl.php

      You need a token related to the Mobile service, for get a token you can go to:

      yourmoodle.com/login/token.php?service=moodle_mobile_app&username=XX&password=YYY

      1 Edit the client.php for adding your custom token and Moodle URL
      2 Open the script in a browser
      3 Check that the user device is stored in Moodle (database user_devices)
      4 Open the script again, you will receive a message "Warning this key already exists for this user"

      Remember to upgrade your Moodle once downloaded the code, it requires some upgrading for adding anew webservice to the moodle mobile app service

      Show
      Testing: Use this client: https://gist.github.com/jleyva/6669774 The curl.php file is here: https://github.com/moodlehq/sample-ws-clients/blob/master/PHP-REST/curl.php You need a token related to the Mobile service, for get a token you can go to: yourmoodle.com/login/token.php?service=moodle_mobile_app&username=XX&password=YYY 1 Edit the client.php for adding your custom token and Moodle URL 2 Open the script in a browser 3 Check that the user device is stored in Moodle (database user_devices) 4 Open the script again, you will receive a message "Warning this key already exists for this user" Remember to upgrade your Moodle once downloaded the code, it requires some upgrading for adding anew webservice to the moodle mobile app service
    • Affected Branches:
      MOODLE_25_STABLE
    • Fixed Branches:
      MOODLE_26_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-41914-weekly

      Description

      We need a core table for storing the user devices ids that have installed the Moodle Mobile app.

      When a user enables receive Notifications in Moodle Mobile the device unique token must be stored in Moodle so messaging plugins can send PUSH messages to the device.

      We are going to:

      • Create a new core table "user_devices"
      • Create a new web service for storing the devices
      • Add this new web service to the existing Mobile Services file

      New core table user_devices:

      id
      userid
      appid (com.moodle.moodlemobile) or (edu.myuniversity.mycustomoodlemobile)
      name (iPhone)
      model (iPhone3,1)
      platform (iOs)
      version (6.1.2)
      key
      uuid
      timecreated
      timemodified

      See MOBILE-452 for more information

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    18/Nov/13