Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-4464

Improve identification of types in site plugins

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major Major
    • 4.4.0
    • DEV backlog
    • Site add-ons
    • Hide

      This issue should be tested by a developer.

      It can be tested on Webapp or Android (it doesn't require to be tested in both).

      1. Login with an user and open any activity of a site plugin. For example, mod_hvp.
      2. Open the element inspector and check that core-site-plugins-module-index and core-site-plugins-plugin-content has a class with the siteplugin name.
      Show
      This issue should be tested by a developer. It can be tested on Webapp or Android (it doesn't require to be tested in both). Login with an user and open any activity of a site plugin. For example, mod_hvp. Open the element inspector and check that core-site-plugins-module-index and core-site-plugins-plugin-content has a class with the siteplugin name.
    • MOODLE_404_STABLE
    • Moodle Apps - 2023 Sprint i4.1

      We need to improve the identification of types of site plugins to apply custom styles by type of site plugin.

      For example, currently we cannot set styles exclusively for site plugins of "x" type.

      To fix that we can add a class to identify the type of the site plugin in core-site-plugins-module-index, core-site-plugins-block, core-site-plugins-course-format and core-site-plugins-plugin-content.

        1. screenshot-1.png
          screenshot-1.png
          195 kB

            alfonso.salces@moodle.com Alfonso Salces
            alfonso.salces@moodle.com Alfonso Salces
            Dani Palou Dani Palou
            Juan Leyva Juan Leyva
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

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