Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-65975

Mobile features should reflect new features supported by Moodle App version 3.7 (backport of MDL-61199)

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Enable "Mobile services": Plugins ► Web Services ► Mobile
      2. Create a WS Token for one user on the site:
        • Click on Site administration ► Plugins ► Web services ► Manage tokens
      3. Go to Site administration ►Mobile app ►Mobile features - Disabled features option
      4. Select the "Comments", and "Ratings" options
      5. Open a terminal/console and execute the following command:
        • You need to replace the wstoken with the token created in step 2 and the URL of your moodle instance

          curl 'http://localhost/m/stable_master/webservice/rest/server.php?moodlewsrestformat=json' --data 'wsfunction=tool_mobile_get_config&wstoken=3af67232a7596ceb658df4db329e5ad6&section=mobileapp' | python -m "json.tool"

      6. Check that in the WS response, in the tool_mobile_disabledfeatures value field, you see the following value (maybe not in the same order): "NoDelegate_CoreRating, NoDelegate_CoreComments"
      7. Now, go back to Site administration ►Mobile app ►Mobile features - Disabled features option, and unselect all the options
      8. Execute the CURL request again and check that the tool_mobile_disabledfeatures value is empty
      Show
      Enable "Mobile services": Plugins ► Web Services ► Mobile Create a WS Token for one user on the site: Click on Site administration ► Plugins ► Web services ► Manage tokens Go to Site administration ►Mobile app ►Mobile features - Disabled features option Select the "Comments", and "Ratings" options Open a terminal/console and execute the following command: You need to replace the wstoken with the token created in step 2 and the URL of your moodle instance curl 'http://localhost/m/stable_master/webservice/rest/server.php?moodlewsrestformat=json' --data 'wsfunction=tool_mobile_get_config&wstoken=3af67232a7596ceb658df4db329e5ad6&section=mobileapp' | python -m "json.tool" Check that in the WS response, in the tool_mobile_disabledfeatures value field, you see the following value (maybe not in the same order): "NoDelegate_CoreRating, NoDelegate_CoreComments" Now, go back to Site administration ►Mobile app ►Mobile features - Disabled features option, and unselect all the options Execute the CURL request again and check that the tool_mobile_disabledfeatures value is empty
    • Affected Branches:
      MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_36_STABLE
    • Pull from Repository:
    • Pull 3.6 Branch:

      Description

      Using Moodle site administration options it is possible to disable certain features of the app (via Admin -> Mobile app -> Mobile app features).
      This is widely used because lots of site admins prefer to disable certain features in the app but keeping the same feature enabled in the web version.
      Everytime we add a new feature in the app we try to include a new option in that site settings.

      This is causing some issues because the development and release cycles of both the app and the web version are different, so we can have the following scenarios (among others):

      • New features in the app, like Blogs, available in the app version 3.7 but that works since Moodle 3.6 onwards (and admins won't be able to disable because there is not an admin option for that in 3.6 - there is one in 3.7 though)
      • New features in the app that will be available in the app version 3.7.1 (and admins won't be able to disable because there is not an option in 3.7 for that)

      In this issue, I'm requesting to update one existing Moodle 3.6 admin setting to reflect the new features added in Moodle app 3.7 like rating, blogs and other ones.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  9/Sep/19

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour
                  1h