XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      1. switch course tagging on in the tag block settings
      2. create two courses A and B.
      3. Add the tag block to the site home page and configure it to display throughout the site.
      4. Add tags 'one' and 'two' to course A, and 'two' and 'three' to course B. Do this by visiting the course, and typing each tag in turn in the tag block text entry field and pressing return. Note that as you start to type in the box, matching existing tags should appear for your re-use (this isn't autocomplete though, just a suggestion).
      5. Make tags 'one' 'two' and 'three' official thorugh the tag editing screen.
      6. Add tags 'four' and 'five' to course A, and 'five' and 'six' to course B. Leave these tags as default.
      7. Go to the site home page, you should see all 6 tags in the block. Click on a tag to view the tag's page showing what is tagged with that word.
      8. Edit the block settings and change the tagtype dropdown to 'official'. Save and recheck that only official tags are shown on the site home page in the block.
      9. Repeat 8 for default tags only.
      10. Log in as a different user, create a few more tags. Go to the 'my home' page and ensure that only tags you've just created (not one to six) are displayed.
      11. Log back in as admin, change the permissions on the authenticated user role so that that role cannot create or flag tags.
      12. Log back in as an ordinary user. Ensure that you can no longer add tags in a course or flag tags as inappropriate on the tag page.

      Show
      1. switch course tagging on in the tag block settings 2. create two courses A and B. 3. Add the tag block to the site home page and configure it to display throughout the site. 4. Add tags 'one' and 'two' to course A, and 'two' and 'three' to course B. Do this by visiting the course, and typing each tag in turn in the tag block text entry field and pressing return. Note that as you start to type in the box, matching existing tags should appear for your re-use (this isn't autocomplete though, just a suggestion). 5. Make tags 'one' 'two' and 'three' official thorugh the tag editing screen. 6. Add tags 'four' and 'five' to course A, and 'five' and 'six' to course B. Leave these tags as default. 7. Go to the site home page, you should see all 6 tags in the block. Click on a tag to view the tag's page showing what is tagged with that word. 8. Edit the block settings and change the tagtype dropdown to 'official'. Save and recheck that only official tags are shown on the site home page in the block. 9. Repeat 8 for default tags only. 10. Log in as a different user, create a few more tags. Go to the 'my home' page and ensure that only tags you've just created (not one to six) are displayed. 11. Log back in as admin, change the permissions on the authenticated user role so that that role cannot create or flag tags. 12. Log back in as an ordinary user. Ensure that you can no longer add tags in a course or flag tags as inappropriate on the tag page.
    • Affected Branches:
      MOODLE_20_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      wip-MDL-15471

      Description

      Following MDL-11992 commit, we will need to improve the integration of the initial course tagging patch with the rest of the tagging system. Among things that need to be improved:
      1) use of "hardcoded" font-style - course tagging uses dynamic css font-size plus: better mathematical distribution, minus: harder to theme) while tags uses s?? classes -,
      2) the choice of "tag type" in the block (all, mine, course, official, community)
      3) push back into /tag/lib.php as much common code as possible

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  3/Dec/12