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

Hidden activities can still be made "visible" through their settings page

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Minor Minor
    • None
    • 2.5.2
    • General, Other
    • MOODLE_25_STABLE
    • Hide

      Workaround would be to not allow users to edit the visibility of the activity to Show /Hide if the parent topic is hidden

      Show
      Workaround would be to not allow users to edit the visibility of the activity to Show /Hide if the parent topic is hidden
    • Hide

      1. Add a new topic to a course
      2. Add a label activity to the topic just created
      3. Back on the course page, hide the topic using the 'eye' icon. This also hides the activity in the topic.
      4. Click on the 'spanner' icon for the greyed out activity and set the visible value to 'Show'
      5. Although the topic and the activity is still hidden , the eye icon is in open state suggesting that the activity is visible

      Show
      1. Add a new topic to a course 2. Add a label activity to the topic just created 3. Back on the course page, hide the topic using the 'eye' icon. This also hides the activity in the topic. 4. Click on the 'spanner' icon for the greyed out activity and set the visible value to 'Show' 5. Although the topic and the activity is still hidden , the eye icon is in open state suggesting that the activity is visible

      The functionality works as intended but it doesnt reflect it in the correct manner. Activites can still be made 'visible' through their settings page even when the topic on the whole is hidden. Same behaviour with 'Orphaned Activities'

            Unassigned Unassigned
            hitteshahuja Hittesh Ahuja
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.