GithubHelp home page GithubHelp logo

alexmorrisnz / moodle-filter_filtercodes Goto Github PK

View Code? Open in Web Editor NEW

This project forked from michael-milette/moodle-filter_filtercodes

0.0 0.0 0.0 1.52 MB

FilterCodes filter for Moodle enables content creators to easily customize and personalize course and site content using plain text tags (no HTML).

License: GNU General Public License v3.0

PHP 100.00%

moodle-filter_filtercodes's Introduction

FilterCodes filter plugin for Moodle

PHP Moodle GitHub Issues Contributions welcome License

Table of Contents

Basic Overview

FilterCodes filter for Moodle enables content creators to easily customize and personalize Moodle sites and course content using over 135 plain text tags that can be used almost anywhere in Moodle. Support may also vary depending on the theme used.

In addition, it also enables you to:

  • Add user interface (UI) elements
  • Inserting non-breaking spaces;
  • Tagging text as being in a different language;

Usage of the FilterCodes tags requires no knowledge of HTML but could be important for sites wishing to comply with accessibility requirements.

IMPORTANT: This STABLE release has been tested on many Moodle sites. Although we expect everything to work, if you find a problem, please help by reporting it in the Bug Tracker.

ALPHA TAGS: There may be some tags identified as ALPHA in this documentation. These may still require some development and are not guarantied to be implemented at all or implemented in the same way in future releases. Please let us know if you think they are useful if they work for you or what changes you might like to see.

(Back to top)

Requirements

This plugin requires Moodle 2.7+ from https://moodle.org/ . Note that some tags may require more recent versions of Moodle.

(Back to top)

Download FilterCodes for Moodle

The most recent STABLE release of FilterCodes for Moodle is available from: https://moodle.org/plugins/filter_filtercodes

The most recent DEVELOPMENT release can be found at: https://github.com/michael-milette/moodle-filter_filtercodes

(Back to top)

Installation

Install the plugin, like any other plugin, to the following folder:

/filter/filtercodes

See https://docs.moodle.org/en/Installing_plugins for details on installing Moodle plugins.

In order for the filters to work, the plugin must be installed and activated.

To activate, go to Site Administration > Plugins > Filters > Manage filters" and set the FilterCodes plugin to "On". Make sure it is set to Apply To: Content or optionally "Content and headings" if you also want the tags to affect headings.

(Back to top)

Usage

IMPORTANT: This STABLE release has been tested on many Moodle sites. Although we expect everything to work, if you find a problem, please help by reporting it in the Bug Tracker.

FilterCodes are meant to be entered as regular text in the Moodle WYSIWYG editor through they will work equally well if entered in the HTML code view.

List of FilterCode tags

Creating FilterCodes Documentation

  • [{ }] : You can escape tags so they are not processed by adding [brackets] around the tag. Can be disabled in the plugin's settings if it causes you problems.
  • [%7B %7D] : You can escape %7Bencoded%7D tags too so they are not processed by adding [brackets] around them.

Profile

  • {firstname} : Display the user's first name.
  • {surname} or {lastname} : Display the user's surname (family/last name).
  • {fullname} : Display the user's first name and surname.
  • {alternatename} : Display the user's alternate name. If blank, will display user's first name instead.
  • {city} : Display the user's city.
  • {country} : Display the user's country.
  • {timezone} : Display the user's preferred timezone.
  • {preferredlanguage} : Display the user's preferred language in that language. Because of this, it will be encapulated in an HTML span tag with an appropriately set lang attribute.
  • {email} : Display the user's email address.
  • {userid} or %7Buserid%7D : Display the user's Moodle ID.
  • {idnumber} : Display the user's idnumber from their profile.
  • {username} : Display the user's username.
  • {userdescription} : Display the user's description.
  • {webpage} : Display the user's webpage as seen in their profile.
  • {institution} : Display the name of the institution from the user's profile.
  • {department} : Display the name of the department from the user's profile.
  • {userpictureurl X} : Display the user's profile picture URL. X indicates the size and can be sm (small), md (medium) or lg (large). If the user does not have a profile picture or is logged out, the default faceless profile photo URL will be shown instead.
  • {userpictureimg X} : Generates an html tag containing the user's profile picture. X indicates the size and can be sm (small), md (medium) or lg (large). If the user does not have profile picture or is logged out, the default faceless profile photo will be used instead.
  • {profile_field_shortname} : Display's custom user profile field. Replace "shortname" with the shortname of a custom user profile field all in lowercase. NOTE: Will not display if the custom user profile field's settings are set to Not Visible.
  • {profilefullname}: Similar to {fullname} except that it displays a profile owner's name when placed on the Profile page.
  • {firstaccessdate dateTimeFormat} : Date that the user first accessd the site. For information on the optional dateTimeFormat format, see Supported dateTimeFormats Formats in the FAQ section of this documentation.

System Information

  • {filtercodes} : Will display version and release of FilterCodes plugin. Not that this information is only available to those who can edit the tag.
  • {usercount} : Count total number of registered users on the site. Does not included deleted users, primary admin or guest.
  • {usersactive} : Count total number of registered users on the site. Does not included deleted users, disabled users, primary admin or guest.
  • {usersonline} : Total number of users who were online in the last 5 minutes.
  • {userscountrycount} : Total number of countries that users are from according to their profile.
  • {siteyear} : 4-digit current year.
  • {now dateTimeFormat} : Display's the current date. For information on the optional dateTimeFormat format, see Supported dateTimeFormats Formats in the FAQ section of this documentation.
  • {coursecount} : Total number of courses on this Moodle site (not including Front Page).
  • {diskfreespace} : Display amount of free disk space for application folder. Infinite symbol will be displayed if greater than about 84,703.29 Yottabytes (YB) or failure to get size from operating system.
  • {diskfreespacedata} : Display amount of free disk space for moodledata folder. Infinite symbol will be displayed if greater than about 84,703.29 Yottabytes (YB) or failure to get size from operating system.
  • {wwwroot} : Root URL of the Moodle site.
  • {supportname} : Support name as seen on Site Administration > Server > Support contact.
  • {supportemail} : Support email address as seen on Site Administration > Server > Support contact.
  • {supporturl} : Support page as seen on Site Administration > Server > Support contact.

UI Elements

  • {teamcards}: Displays photos, name (optionally linked) and optional description of user's who are teachers. Only Verbose format is suitable for use in side-blocks.
  • {coursecards} or {coursecards categoryID}: (ALPHA) Display available courses as cards. You can optionally specify the ID number of a category. Example: {coursecards 1} will only display courses in the default Miscellaneous category. Note: The categoryID is not the "Category ID Number" field that you can optionally specify when creating a category.
  • {coursecardsbyenrol} (ALPHA): Display course cards for most popular courses based on enrolment. Maximum number of cards is configurable in the plugin settings.
  • {courseprogress}: (ALPHA) Displays course progress status in words. Only works within a course.
  • {courseprogressbar}: (ALPHA) Displays course progress status as a status bar. Only works within a course.
  • {categorycards} or {categorycards id}: (ALPHA) Display top level categories as cards using the current location as the top level category. For example, on the Front Page, it will display all top level categories. However, if you are inside the Miscellaneous category (e.g., in Miscellaneous > Your Course) , it will only display the next level of categories under the Miscellaneous category. You can optionally specify a category in the tag.
  • {mycourses} : Display an unordered list of links to all my enrolled courses.
  • {mycoursescards} : Displays a series of cards for my enrolled courses.
  • {courserequest} : Displays a Request a Course link.
  • {label type}{/label} : Display text over background colour. The Boost theme supports the following types: info, important, secondary, success and warning. Other themes may also support primary, danger, light, dark and more. Example: {label info}For your information{/label}. Actual foreground and background colours vary depending on the theme. If the type is not specified, it will default to info. If the type specified is not supported by your theme, it may default to secondary.
  • {button URL}Label{/button} : Create a clickable button link formatted like a primary button.
  • {chart radial x Title text} (ALPHA): Create a radial (circle / doughnut) chart given it a value of x between 0 and 100 and a title.
  • {chart pie x Title text} (ALPHA) : Create a pie chart given a value of x between 0 and 100 and a title.
  • {chart progressbar x Title text} (ALPHA) : Create a horizontal progress bar chart giving it a value of x between 0 and 100 and a title.
  • {showmore}{/showmore} (ALPHA) : Toggle showing content between opening and closing more tags. Limitations: Can only be used inline with text. Must now weave into other opening and closing tags.

For use in courses

  • {coursename} : Display the full name of the current course or the site name if not in a course.
  • {courseshortname} : Display the short name of t he current course or the site short name if not in a course.
  • {coursestartdate dateTimeFormat} : Course star t date. Will display "Open event" if there is no start date. For information on the optional dateTimeFormat format, see Supported dateTimeFormats Formats in the FAQ section of this documentation.
  • {courseenddate dateTimeFormat} : Course end date. Will display "Open event" if there is no end date. For information on the optional dateTimeFormat format, see Supported dateTimeFormats Formats in the FAQ section of this documentation.
  • {coursecompletiondate dateTimeFormat} : Course completion date. If not completed, will display "Not completed". Will also detect if completion is not enabled. For information on the optional dateTimeFormat format, see Supported dateTimeFormats Formats in the FAQ section of this documentation.
  • {courseprogress}: (ALPHA) Displays course progress status in words.
  • {courseprogressbar}: (ALPHA) Displays course progress status as a status bar.
  • {course_fields}: Displays the custom course fields. NOTE: Respects a custom course field's Visible To setting.
  • {course_field_shortname} : Display's custom course field. Replace "shortname" with the shortname of a custom course field all in lowercase. NOTE: Respects a custom course field's Visible To setting.
  • {coursesummary} : Display's the course summary. If placed in a site page, displays the site summary.
  • {courseimage} : Display's the course image.
  • {courseparticipantcount} : Displays the number of students enrolled in the current course.
  • {courseid} or %7Bcourseid%7D : Display a course's ID.
  • {coursecontextid} or %7Bcoursecontextid%7D : Display a course's context ID.
  • %7Bcoursemoduleid%7D : Display a course's activity module ID - for use in URLs. Only for use in course activity modules.
  • {courseidnumber} : Display a course's ID number.
  • {sectionid} or %7Bsectionid%7D : Display the section ID (not to be confused with the section number).
  • {sectionname} : Display the section name in which the activity is located.
  • {coursecontacts}: List of course contacts with links to their profiles, email address or messaging or phone number, and their user description (there are settings for these). Note: This tag was formerly called {courseteachers}.
  • {coursegradepercent}: Displays the current accumulated course grade of the student.

Also see Courses section below.

Categories

  • {categoryid} : If in a course, the ID of the course's parent category, the category ID of a course category page, otherwise 0.
  • {categoryname} : If in a course, the name of the course's parent category, otherwise blank.
  • {categorynumber} : If in a course, the number of the course's parent category, otherwise blank.
  • {categorydescription} : If in a course, the number of the description of a course's parent category, otherwise blank.
  • {categories} : Display an unordered list of links to all course categories.
  • {categories0} : Display an unordered list of just top level links to all course categories.
  • {categoriesx} : Display an unordered list of other categories in the current category.

Custom menu

Note: Filtering must be supported in custom menu by your theme.

  • {categoriesmenu} : A second level list of categories with links for use in custom menus.
  • {categories0menu} : A second level list of just top level categories with links for use in custom menus.
  • {categoriesxmenu} : A second level list of other categories in the current category with links for use in custom menus.
  • {toggleeditingmenu} : A Turn Editing On or Turn Editing Off custom menu item. Note that you need to add your own dash(es).
  • {mycoursesmenu} : A second level list of courses with links for use in custom menus .
  • {courserequestmenu0} : Request a course / Course request in a top level custom menu.
  • {courserequestmenu} : Request a course / Course request in submenu.
  • {menuadmin} : Useful dynamic menu for Moodle teachers, managers and administrators.
  • {menudev} : Useful dynamic menu for Moodle developers.

URL

  • {pagepath} : Path of the current page without wwwroot.
  • {thisurl} : The complete URL of the current page.
  • {thisurl_enc} : The complete encoded URL of the current page.
  • {urlencode}{/urlencode} : URL encodes any content between the tages.
  • {referer} : Referring URL
  • {protocol} : http or https
  • {referrer} : Alias of {referer}
  • {ipaddress} : User's IP Address.
  • {sesskey} or %7Bsesskey%7D : Moodle session key.
  • {wwwcontactform} : Action URL for Contact Form forms. (requires Contact Form plugin).

Content

  • {global_...} : Use your own custom FilterCodes tags in the filter's settings. This is sometimes referred to as global blocks. An example of this might be if you wanted to define a standardized copyright or other text, email address, website URL, phone number, name, link, support information and more. Define and centrally manage up to 20 global block tags.
  • {note}content{/note} : Enables you to include a note which will not be displayed.
  • {help}content{/help} : Enables you to create popup help icons just like Moodle does.
  • {info}content{/info} : Enables you to create popup help icons just like the popup Help icons but with an "i" information icon.
  • {alert style}content{/alert}: (ALPHA) Creates an alert box containing the specified content. You can change the style by specifying an optional parameter. Example: {alert primary} or {alert success}. List of styles
  • {highlight}{/highlight} : Highlight text like a highlighter in bright yellow. NOTE: Must only be used within a paragraph.
  • {marktext}{/marktext} : Highlight text using HTML5's mark tag. You can style this tag using CSS in your theme using a fc-marktext class.
  • {markborder}{/markborder} : Surrounds text with a red dashed border. You can style this tag using CSS in your theme using a fc-markborder class (border and padding with !important to override).
  • {scrape url="..." tag="..." class="..." id="..." code="..."} : Scrapes the content from another web page. Must be enabled in FilterCodes settings.
  • {getstring:component_name}stringidentifier{/getstring} or {getstring}stringidentifier{/getstring}: Display a Moodle language string in the current language. If no component name (plugin) is specified, will default to "moodle".
  • {fa/fas/far/fal fa-...} : Insert FontAwesome icon. Note: FontAwesome Font/CSS must be loaded as part of your theme.
  • {glyphicon glyphicon-...} : Insert Glyphicons icon. Note: Glyphicons Font/CSS must be loaded as part of your theme.

Contact Form templates

The following tags are replaced by Contact Form templates and therefore require that you have the Contact Form for Moodle plugin installed.

  • {formquickquestion} : Adds a "quick question" form to your course. Form includes Subject and Message fields. Note: User must be logged in or the form will not be displayed.
  • {formcontactus} : Adds a "Contact Us" form to your site (example: in a page). Form includes Name, Email address, Subject and Message fields.
  • {formcourserequest} : Adds a "Course Request" form to your site (example: in a page). Unlike Moodle's request-a-course feature where you can request to create your own course, this tag allows users to request that a course they are interested in be created. Could also be used to request to take a course. Form includes Name, Email address, Course name, Course Description.
  • {formsupport} : Adds a "Support Request" form to your site (example: in a page). Form includes Name, Email address, pre-determined Subject, specific Subject, URL and Message fields.
  • {formcheckin} : Adds a "I'm here!" button to your to your course. Form does not include any other fields. Note: User must be logged in or the button will not be displayed.

Useful for creating Custom Contact Forms and Links

  • {lang} : 2-letter language code of current Moodle language.
  • {recaptcha} : Display the ReCAPTCHA field - for use with Contact Form for Moodle. Note: Will be blank if user is logged-in using a non-guest account.
  • {readonly} : To be used within form input fields to make them read-only if the user is logged-in.
  • {editingtoggle} : "off" if in edit page mode. Otherwise "on". Useful for creating Turn Editing On/Off links.
  • {wwwcontactform} : Action URL for Contact Form forms. (requires Contact Form plugin).
  • {formsesskey} : Not a form. This can be used instead of having to insert the required hidden input field and JavaScript Snippet.

Conditionally display content filters (All versions of Moodle)

Note: {ifrolename} and {ifminrolename} type tags are based on role archetypes, not role shortnames. For example, you could have a role called students but, if the archetype for the role is teacher, the role will be identified as a teacher. Roles not based on archetypes will not with these tags.

Logged in/out

  • {ifloggedin}{/ifloggedin} : Will display the enclosed content only if the user is logged in as non-guest.
  • {ifloggedout}{/ifloggedout} : Will display the enclosed content only if the user is logged out or is loggedin as guest.
  • {ifloggedinas}{/ifloggedinas} : Will display the enclosed content only if you are logged-in-as (loginas) a different user.
  • {ifnotloggedinas}{/ifnotloggedinas} : Will display the enclosed content only if you are logged-in as yourself and not a different user.

Courses

  • {ifenrolled}{/ifenrolled} : Will display the enclosed content only if the user is enrolled as a student in the current course. This tag does not take any other roles into consideration.
  • {ifnotenrolled}{/ifnotenrolled} : Will display the enclosed content only if the user is not enrolled as a student in the current course. This tag does not take any other roles into consideration.
  • {ifincourse}{/ifincourse} : Will display the enclosed content only if the user is in a course other than the Front page.
  • {ifinsection}{/ifinsection} : Will display the enclosed content only if the user is in a section of a course which is not the Front Page.
  • {ifnotinsection}{/ifnotinsection} : Will display the enclosed content only if the user is not in a section of a course.
  • {ifingroup id|idnumber}{/ifingroup} : Display content if the user is part of the specified course group ID or group ID number.
  • {ifnotvisible}{/ifnotvisible} : Display content if the course visibility is set to Hide.

Roles

  • {ifguest}{/ifguest} : Will display the enclosed content only if the user is logged-in as guest.
  • {ifstudent}{/ifstudent} : Will display the enclosed content only if the user is logged-in and enrolled in the course (no other roles).
  • {ifassistant}{/ifassistant} : Will display the enclosed content only if the user is logged-in as a non-editing teacher in the current course.
  • {ifminassistant}{/ifminassistant} : Will display the enclosed content only if the user is logged-in as a non-editing teacher or above in the current course.
  • {ifteacher}{/ifteacher} : Will display the enclosed content only if the user is logged-in as a teacher in the current course.
  • {ifminteacher}{/ifminteacher} : Will display the enclosed content only if the user is logged-in as a teacher or above in the current course.
  • {ifcreator}{/ifcreator} : Will display the enclosed content only if the user is logged-in as a course creator.
  • {ifmincreator}{/ifmincreator} : Will display the enclosed content only if the user is logged-in as a course creator or above.
  • {ifmanager}{/ifmanager} : Will display the enclosed content only if the user is logged-in as a manager.
  • {ifminmanager}{/ifminmanager} : Will display the enclosed content only if the user is logged-in as a manager or above.
  • {ifminsitemanager}{/ifminsitemanager} : Will display the enclosed content only if the user is logged-in as a site manager or above.
  • {ifadmin}{/ifadmin} : Will display the enclosed content only if the user is logged-in as an administrator.
  • {ifcustomrole roleshortname}{/ifcustomrole} : Will display enclosed content only if the user has the custom role specified by its shortname within the current context.
  • {ifnotcustomrole roleshortname}{/ifnotcustomrole} : Will display enclosed content only if the user does not have the custom role specified by its shortname within the current context.
  • {ifincohort CohortID|idnumber}{/ifincohort} : Will display enclosed content only if user is a member of the specified cohort. You can specify the Cohort ID in your cohort settings or its ID number. Cohort ID can contain a combination of letters from a to z, A to Z, numbers 0 to 9 and underscores. It will not work if it contains spaces, dashes or other special characters.

Miscellanious

  • {ifdev}{/ifdev} : Will display the enclosed content only if the user is logged-in as an administrator and developer debugging mode is enabled.
  • {ifhome}{/ifhome} : Will display the enclosed content only if the user is on the Moodle Home Front Page.
  • {ifnothome}{/ifnothome} : Will not display the enclosed content if the user is on the Moodle Home Front Page.
  • {ifdashboard}{/ifdashboard} : Will display the enclosed content only if the user is on the Moodle Dashboard.
  • {ifcourserequests}{/ifcourserequests} : Will display enclosed contents only if the Request a Course feature is enabled.
  • {ifeditmode}{/ifeditmode} : Will display the enclosed content only if editing mode is turned on.
  • {ifprofile_field_shortname}{/ifprofile_field_shortname} : Will display the enclosed content if the custom user profile field is not blank/zero.

If the condition is not met in the particular context, the specified tag and it's content will be removed.

Conditionally display content filters (For Moodle Workplace)

  • {iftenant idnumber|tenantid}{/iftenant} : (ALPHA) Will display the content if a tenant idnumber or tenant id is specified. Only {iftenant 1} will work in Moodle classic.
  • {ifworkplace}{/ifworkplace} : (ALPHA) Will display the content only if displayed in Moodle Workplace.

HTML and "lang" tagging

  • {-} : Is substituted for ­, a soft hyphen that only appears when needed.
  • {nbsp} : Is substituted for a non-breaking space when displayed.
  • {hr} : Horizontal rule.
  • {details}{summary}{/summary}{/details} : An easy way to create an HTML 5 Details/Summary expandable section in your page. IMPORTANT: {details}{summary}{/summary} must all be on one line (it is ok if the line wraps). The rest of the details can be on multiple lines followed by the {/details}. This is an experimental feature which may result in invalid HTML but it works.
  • {langx xx}{/langx} : Tag specific text in a particular language by wrapping the text in a plain text pair of {langx xx} {/langx} or {langx xx-XX} {/langx} tags. This makes no visible changes to the content but wraps the content in an HTML inline tag. As a result, screen readers will make use of this localization information to apply a particular pronunciation if the text is in a different language than the language of the rest of the page. This is required for compliance with W3C Web Content Accessibility Guidelines (WCAG 2.0)

The opening {langx xx} tag should include two ISO 639-1 language code abbreviation letters in lowercase associated with language's name. French, for example, has the code fr:

{langx fr}Contenu{/langx}

The {langx fr}{/langx} filter will convert this into the following HTML

<span lang="fr">Contenu</span>

The opening {langx xx} may also include a culture code used in countries and regions. This includes an additional dash and two uppercase letters associated with language's region or country. French Canadian, for example, has the code fr-CA:

{langx fr-CA}Contenu{/langx}

The {langx fr-CA}{/langx} filter will convert this into the following HTML

<span lang="fr-CA">Contenu</span>

Define your own custom global tags

You can define your own global tags, sometimes also called global blocks. This can only be configured by Moodle Administrators by going to Site Administration > Plugins > Filters > FilterCodes.

You can create up to 20 custom global tags by specifying the tag name. The tag name will automatically be prefixed by global. For example, if you define a tag called copyright, it will create a FilterCodes tag {global_copyright}.

The content which you can insert is only limited by your imagination. You can include plain text content, such as one or more words, HTML source code or even a JavaScript snippet (wrap in a script tag). You can also enter almost any content using the WYSIWYG Atto editor by checking the "Pretty HTML format" checkbox. This allows you to create formatted content, uploaded images and more. Note: It does not support PHP code.

Let's say you want to include a support email address in some of your courses. You could define a global tag called "global_email" and set it to "[email protected]". Then, wherever you want that email address to appear on your site, you just need to add the tag {global_email}. That way, when you decide to change the email address to "[email protected]", you need just change it here in the clobal custom tag settings.

FilterCodes in a custom menu

Here are a few examples of how to create really useful custom menus using FilterCodes. Just copy and paste the code into the Custom menu items field (Site administration > Appearance > Theme settings). Feel free to customize these for your own needs and to make more of these for other roles like Moodle Managers, Course creators, Teachers, Teacher assistants and even Students.

Multi-language support

The examples often make use of strings defined in Moodle. So, if you renamed your Dashboard to My Dashboard using the Moodle language editor, it will be reflected when the menu is displayed and change language when the user changes language in Moodle.

In cases where a string is not available as a Moodle language strings, some of the examples below also demonstrate how you can make use of the excellent Multi-Language Content (v2) plugin to add support for {mlang} tags. In the examples below, English and French are used. If you only use one langauge, remove the {mlang} tags along with the alternate language text.

Doesn't work?

If FilterCodes doesn't work with your theme's custom menu, contact the developer / maintainer of the theme and refer them to the FAQ section of this documentation. It will provide them with an easy way for them to enable support for Moodle filters.

Alternatively, apply the Moodle core patch mentioned in https://tracker.moodle.org/browse/MDL-63219 . But remember, you will need to re-apply this after each Moodle update/upgrade. The advantage of this method is that it will add support for filters in the custom menu of most Moodle themes, not just your particular theme.

Some themes may not support horizontal menu separators. Again, contact the developer / maintainer of the theme to get them to fix this or remove the -### lines.

General menu

This will add a Home link, a listing of top-level categories, a listing of courses in which you are currently enrolled, and a Logout link, but only if you are currently logged in.

{fa fa-home} {getstring}home{/getstring}|/{ifloggedin}?redirect=0{/ifloggedin}
{fa fa-th} {mlang en}Course catalogue{mlang}{mlang fr}Répertoire des cours{mlang}
{categories0menu}
    -###
    -{getstring}fulllistofcourses{/getstring}|/course/
{ifloggedin}
{fa fa-tachometer} {getstring}myhome{/getstring}|/my/
{fa fa-graduation-cap} {getstring}mycourses{/getstring}
{mycoursesmenu}
{courserequestmenu}
{getstring}logout{/getstring}|/login/logout.php?sesskey={sesskey}
{/ifloggedin}
{fa fa-question} {getstring}help{/getstring}|/mod/page/view.php?id=275

Admin menu

Parts of this menu will only appear for Moodle administrators, managers, course creators and teachers depending on the user's role within the current context. For example:

  • {ifincourse} menu items will only appear in a course.

  • Category Course Creators will only see the Admin menu within categories where they have that role.

  • Teachers will only see the Admin menu within the course where they are a teacher.

    {ifminteacher} {fa fa-wrench} {getstring}admin{/getstring} {/ifminteacher} {ifmincreator} -{getstring}administrationsite{/getstring}|/admin/search.php -{toggleeditingmenu} -Moodle Admin Basics course|https://learn.moodle.org/course/view.php?id=23353|Learn.Moodle.org -### {/ifmincreator} {ifminmanager} -{getstring}user{/getstring}: {mlang en}Management{mlang}{mlang fr}Gestion{mlang}|/admin/user.php {ifminsitemanager} -{getstring}user{/getstring}: {getstring:mnet}profilefields{/getstring}|/user/profile/index.php -### {/ifminsitemanager} -{getstring}course{/getstring}: {mlang en}Management{mlang}{mlang fr}Gestion{mlang}|/course/management.php -{getstring}course{/getstring}: {getstring}new{/getstring}|/course/edit.php?category={coursecategoryid}&returnto=topcat {/ifminmanager} {ifminteacher} -{getstring}course{/getstring}: {getstring}restore{/getstring}|/backup/restorefile.php?contextid={coursecontextid} {ifincourse} -{getstring}course{/getstring}: {getstring}backup{/getstring}|/backup/backup.php?id={courseid} -{getstring}course{/getstring}: {getstring}participants{/getstring}|/user/index.php?id={courseid} -{getstring}course{/getstring}: {getstring:badges}badges{/getstring}|/badges/index.php?type={courseid} -{getstring}course{/getstring}: {getstring}reset{/getstring}|/course/reset.php?id={courseid} -Course: Layoutit|https://www.layoutit.com/build" target="popup" onclick="window.open('https://www.layoutit.com/build','popup','width=1340,height=700'); return false;|Bootstrap Page Builder {/ifincourse} -### {/ifminteacher} {ifminmanager} -{getstring}site{/getstring}: System reports|/admin/category.php?category=reports {/ifminmanager} {ifadmin} -{getstring}site{/getstring}: {getstring:admin}additionalhtml{/getstring}|/admin/settings.php?section=additionalhtml -{getstring}site{/getstring}: {getstring:admin}frontpage{/getstring}|/admin/settings.php?section=frontpagesettings|Including site name -{getstring}site{/getstring}: {getstring:admin}plugins{/getstring}|/admin/search.php#linkmodules -{getstring}site{/getstring}: {getstring:admin}supportcontact{/getstring}|/admin/settings.php?section=supportcontact -{getstring}site{/getstring}: {getstring:admin}themesettings{/getstring}|/admin/settings.php?section=themesettings|Including custom menus, designer mode, theme in URL -{getstring}site{/getstring}: Boost|/admin/settings.php?section=themesettingboost -{getstring}site{/getstring}: {getstring}notifications{/getstring} ({getstring}admin{/getstring})|/admin/index.php {/ifadmin}

Tips: If you are not using the Boost theme, customize the link in the 3rd to last line to your theme's settings page.

Even better, try out {menuadmin}. It includes all of the above and more. Best of all, it only includes menu items for features that are enabled within the context of the current page.

Developer Tools menu

If you are a developer, this little menu is worth installing FilterCodes alone.

Together with the Administration menu above, these can be a real productivity boost for developers who are tired of always digging through the Site administration block to find the options they are looking for. Tailor it to your particular projects with links to any page you use regularly.

This will display the enclosed content only if the user is logged-in as an administrator and developer debugging mode is enabled. If you want it to display regardless of the state of developer debugging,change {ifdev} and {/ifdev} to {ifadmin} and {/ifadmin} respectively.

{ifdev}
Dev tools
-{getstring:tool_installaddon}installaddons{/getstring}|/admin/tool/installaddon
-###
-{getstring:admin}debugging{/getstring}|/admin/settings.php?section=debugging
-{getstring:admin}purgecachespage{/getstring}|/admin/purgecaches.php?confirm=1&sesskey={sesskey}
-###
-Code checker|/local/codechecker
-Moodle PHPdoc check|/local/moodlecheck
-Adminer|/local/adminer
-{getstring}phpinfo{/getstring}|/admin/phpinfo.php
-###
-Developer docs|https://moodle.org/development|Moodle.org
-Developer forum|https://moodle.org/mod/forum/view.php?id=55|Moodle.org
-Tracker|https://tracker.moodle.org/|Moodle.org
-AMOS|https://lang.moodle.org/|Moodle.org
-Development Tutorial|https://www.youtube.com/watch?v=UY_pcs4HdDM
-Moodle Development School|https://moodledev.moodle.school/
{/ifdev}

Notes:

Even better, try out the dynamic {menudev}. It includes all of the above and more. Best of all, it only includes menu items for the developer tools that you have installed. Just replace everything below the words "Dev tools" and above the "{/ifdev}" line.

FilterCodes in custom menus

Note: The source code in this section was updated in May 2021.

FilterCodes can work in custom menus but but, unfortunately, only if the theme supports it or you patched Moodle. If it does not work for you, contact the theme's developer and request that they add support for Moodle filters. See instructions are included below.

Note: As of version 1.0.0 of FilterCodes, experimental support was added for Clean and Boost themes in Moodle 3.2 to 3.4. In order to work, this had to be enabled in FilterCodes settings and Filtering will not be applied to the Moodle Theme Settings page. Unfortunately things changed in Moodle 3.5 and it has since not been possible for FilterCodes to do this on its own.

There are two ways to make FilterCodes work in Moodle's custom menu:

  1. Add a few lines of code to your Moodle theme. Even better, your theme's developer to enable this in their themes.

For themes based on boost (Moodle 3.2 and later)

Note: Supported in Moodle 3.2 and later.

Add the following code to core_renderer section of your theme. Note: Your theme may even already have such a class (they often do):

use filter_manager;

class core_renderer extends \theme_boost\output\core_renderer {
    /**
     * Applies Moodle filters to custom menu and custom user menu.
     *
     * @param string $custommenuitems Current custom menu object.
     * @return Rendered custom_menu that has been filtered.
     */
    public function custom_menu($custommenuitems = '') {
        global $CFG, $PAGE;

        // Don't apply auto-linking filters.
        $filtermanager = filter_manager::instance();
        $filteroptions = ['originalformat' => FORMAT_HTML, 'noclean' => true];
        $skipfilters = ['activitynames', 'data', 'glossary', 'sectionnames', 'bookchapters', 'urltolink'];

        // Filter custom user menu.
        // Don't filter custom user menu on the settings page. Otherwise it ends up
        // filtering the edit field itself resulting in a loss of the tag.
        if ($PAGE->pagetype != 'admin-setting-themesettings' && stripos($CFG->customusermenuitems, '{') !== false) {
            $CFG->customusermenuitems = $filtermanager->filter_text($CFG->customusermenuitems, $PAGE->context,
                    $filteroptions, $skipfilters);
        }

        // Filter custom menu.
        if (empty($custommenuitems) && !empty($CFG->custommenuitems)) {
            $custommenuitems = $CFG->custommenuitems;
        }
        if (stripos($custommenuitems, '{') !== false) {
            $custommenuitems = $filtermanager->filter_text($custommenuitems, $PAGE->context, $filteroptions, $skipfilters);
        }
        $custommenu = new custom_menu($custommenuitems, current_language());
        return $this->render_custom_menu($custommenu);
    }

    /**
     * We want to show the custom menus as a list of links in the footer on small screens.
     * Just return the menu object exported so we can render it differently.
     */
    public function custom_menu_flat() {
        global $CFG, $PAGE;
        $custommenuitems = '';

        // Don't apply auto-linking filters.
        $filtermanager = filter_manager::instance();
        $filteroptions = ['originalformat' => FORMAT_HTML, 'noclean' => true];
        $skipfilters = ['activitynames', 'data', 'glossary', 'sectionnames', 'bookchapters', 'urltolink'];

        if (empty($custommenuitems) && !empty($CFG->custommenuitems)) {
            $custommenuitems = $CFG->custommenuitems;
        }
        if (stripos($custommenuitems, '{') !== false) {
            $custommenuitems = $filtermanager->filter_text($custommenuitems, $PAGE->context, $filteroptions, $skipfilters);
        }
        $custommenu = new custom_menu($custommenuitems, current_language());
        $langs = get_string_manager()->get_list_of_translations();
        $haslangmenu = $this->lang_menu() != '';

        if ($haslangmenu) {
            $strlang = get_string('language');
            $currentlang = current_language();
            if (isset($langs[$currentlang])) {
                $currentlang = $langs[$currentlang];
            } else {
                $currentlang = $strlang;
            }
            $this->language = $custommenu->add($currentlang, new moodle_url('#'), $strlang, 10000);
            foreach ($langs as $langtype => $langname) {
                $this->language->add($langname, new moodle_url($this->page->url, ['lang' => $langtype]), $langname);
            }
        }

        return $custommenu->export_for_template($this);
    }
}

For themes based on the older bootstrapbase (Moodle 2.7 to 3.6)

Note: Supported in Moodle 2.7 to 3.6.

Add the following code to core_renderer section of your theme for Moodle 2.7 to 3.6. Be sure to replace "themename" with the name of the theme's directory. Note: Your theme may even already have such a class (they often do):

class theme_themename_core_renderer extends theme_bootstrapbase_core_renderer {
    /**
     * Applies Moodle filters to custom menu and custom user menu.
     *
     * Copyright: 2017-2022 TNG Consulting Inc.
     * License:   GNU GPL v3+.
     *
     * @param string $custommenuitems Current custom menu object.
     * @return Rendered custom_menu that has been filtered.
     */
    public function custom_menu($custommenuitems = '') {
        global $CFG, $PAGE;

        // Don't apply auto-linking filters.
        $filtermanager = filter_manager::instance();
        $filteroptions = ['originalformat' => FORMAT_HTML, 'noclean' => true];
        $skipfilters = ['activitynames', 'data', 'glossary', 'sectionnames', 'bookchapters', 'urltolink'];

        // Filter custom user menu.
        // Don't filter custom user menu on the theme settings page. Otherwise it ends up
        // filtering the edit field itself resulting in a loss of tags.
        if ($PAGE->pagetype != 'admin-setting-themesettings' && stripos($CFG->customusermenuitems, '{') !== false) {
            $CFG->customusermenuitems = $filtermanager->filter_text($CFG->customusermenuitems, $PAGE->context,
                    $filteroptions, $skipfilters);
        }

        // Filter custom menu.
        if (empty($custommenuitems) && !emty($CFG->custommenuitems)) {
            $custommenuitems = $CFG->custommenuitems;
        }
        if (stripos($custommenuitems, '{') !== false) {
            $custommenuitems = $filtermanager->filter_text($custommenuitems, $PAGE->context, $filteroptions, $skipfilters);
        }
        $custommenu = new custom_menu($custommenuitems, current_language());
        return $this->render_custom_menu($custommenu);
    }
}
  1. Patch your instance of Moodle. Even better, encourage Moodle HQ to enable this functionality in future releases of Moodle. For more information and to vote for this functionality, see michael-milette#67 .

To patch Moodle to handle this properly for most Moodle themes, apply the following patch to Moodle:

Scrape'ing content

Note: This feature must be enabled in FilterCodes settings.

IMPORTANT: You cannot use this feature to scrape content from any website that requires you to be logged-in in order to access the content. The {scrape} tag can only access content as a non-authenticated user, even if you are logged-in.

As of version 0.4.7, you can now use FileterCodes to scrape content from another web page. Your mileage may vary and depends a lot on your configuration, the website from which you are scraping content and more.

{scrape url="..." tag="..." class="..." id="..." code="..."}

Tip: When adding this tag in one of Moodle's WYSIWYG editors like Atto or TinyMCE, the tag may end up embedded in a set of HTML paragraph tags. If this happens, the content you are scraping may not result in valid HTML. To fix the problem, you will need to go into the source code view of the editor and replace the P (paragraph) tags with div and then save. Alternatively, if there is nothing else in the editor, you can remove everything before and after the tag and save.

Parameters:

  • url = The URL of the webpage from which you want to grab its content.
  • tag = The HTML tag you want to capture.
  • class = Optional. Default is blank (class is irrelevant). Class attribute of the HTML tag you want to capture. Must be an exact match for everything between the quotation marks.
  • id = Optional. Default is blank (id is irrelevant). id tag of the HTML tag you want to capture.
  • code = Optional. Default is blank (no code). This is URL encoded code that you want to insert after the content. Will be decoded before being inserted into the page. Can be things like JavaScript for example. Be careful with this one. If not encoded, will result in error.

If the URL fails to produce any content (broken link for example), a message will be displayed on the page encouraging the visitor to contact the webmaster. This message can be customized through the Moodle Language editor.

If a matching tag, class and/or id can't be found, will return all of the page content without being filtered.

Back to section / Back to course

Help students navigate your Moodle site by implementing this handy-dandy BACK button. Works at both the section and activity level.

<p style="float:right;"><a href="{wwwroot}/course/view.php?id={courseid}&amp;section={sectionid}" class="btn btn-outline" style="font-size:14px;">Go Back</a></p>

If you are in a section and want to go directly back to the main course outline but scroll down to the current section, try this:

<p style="float:right;"><a href="{wwwroot}/course/view.php?id={courseid}#section-{sectionid}" class="btn btn-outline" style="font-size:14px;">Back to course outline</a></p>

Optional FilterCodes for Moodle settings

FilterCodes for Moodle includes the following settings. These are available on the plugin's Settings page by going to:

Site administration > Plugins > Filters > Filter Codes

Custom navigation support

Experimental: Only available in Moodle 3.2, 3.3 and 3.4. Enable support for FilterCode tags in Moodle custom navigation menu. Note: Is known to be compatible with Clean and Boost based themes.

NOTE: Does not filter tags on the Moodle Theme Settings page. This is not a bug, just a limitation.

For information on enabling FilterCodes in custom menus of other versions of Moodle, see FilterCodes in a custom menu

Escape tags

When this option is checked, you will be able to display FilterCode tags without them being interpreted by this filter by wrapping your tag in [ brackets ]. This can be very useful when creating FilterCodes documentation for the teachers and course creators on your Moodle site.

Hide completed courses

Enable to filter out completed courses in {mycoursesmenu} tag listings. When checked, only incomplete courses and courses where completion tracking is not enabled will be displayed. Default (unchecked) is to display all courses regardless of completion status..

Scrape tag support

Enable or disable the {scrape} tag.

Show contact picture

Enable or disable showing of contact profile picture in {coursecontacts} tag.

Contact link type

Choose the type of link for the teacher\s link in the {coursecontacts} tags. Profile, Messaging, Email address or None. Choose None if you don't want just the name witout a link.

Show {categorycards} background

Enable or disable the background pattern/image for {categorycards}. You can also optionally configure the look of {categorycards} using CSS on the .fc-categorycards class.

Global custom tags

Define your own global tags, sometimes also called global blocks. This feature enables you to create your own tags that are prefixed by global_ . You can currently define up to 20 custom {global_...} tags.

Customizing or translating the forms generated by the {form...} tags

You can translate or customize the form tags in Moodle's language editor. Here is how to do it:

  1. Navigate to Site Administration > Language > Language Customization.
  2. Select the language you want to customize.
  3. Click the Open Language Pack for Editing button.
  4. Wait until the Continue button apppears. This may take a little time. Please be patient.
  5. In the Show Strings of These Components field, scroll down and select filter_filtercodes.php.
  6. Click the Show Strings button.
  7. Scroll down to the strings called formcheckin, formcontactus, formcourserequest, formquickquestion and formsupport. This is the HTML for the tags of the same name.
  8. Edit the form as needed.
  9. Scroll to the bottom of the page and click the Save changes to the language pack button.

For more information on editing language strings in Moodle, visit: https://docs.moodle.org/en/Language_customisation.

Alternatively, you could simply insert the HTML for the form in the Atto editor. These {form...} tags are just provided to quickly create generic forms on your Moodle site.

(Back to top)

Updating

There are no special considerations required for updating the plugin.

The first public ALPHA version was released on 2017-07-07, BETA on 2017-11-11 and STABLE as of 2018-11-26.

For more information on releases since then, see CHANGELOG.md.

(Back to top)

Uninstallation

Uninstalling the plugin by going into the following:

Home > Administration > Site Administration > Plugins > Manage plugins > FilterCodes

...and click Uninstall. You may also need to manually delete the following folder:

/filter/filtercodes

Note that, once uninstalled, any tags and content normally handled by this plugin will become visible to all users.

Limitations

  • Be aware that enabling the Moodle "Download course content" feature may not process some tags correctly or at all through Moodle filters. As a result, tags may be displayed instead of content. This is a known Moodle issue MDL-72894 which will hopefully be resolved in the near future.
  • Do not use For use in courses type tags inside your course summary. Course listings and course descriptions pages are not displayed within the context of a course. These only work properly within courses. Keep context in mind.
  • The {langx xx}{/langx} tag only supports inline text, not blocks of text.
  • Unpredictable results may occur if you interweave HTML code with {FilterCodesTag} tags.

Incorrect example:

<strong>{FilterCodesTag}Content</strong>{/FilterCodesTag}

Correct example:

{FilterCodesTag}<strong>Content</strong>{/FilterCodeTag}

Language Support

This plugin includes support for the English language.

If you need a different language that is not yet supported, please feel free to contribute using the Moodle AMOS Translation Toolkit for Moodle at

https://lang.moodle.org/

If the content replacing the tag contains language filtering tags, be sure to have FilterCodes above the language filter in the Moodle filter settings.

This plugin has not been tested for right-to-left (RTL) language support. If you want to use this plugin with a RTL language and it doesn't work as-is, feel free to prepare a pull request and submit it to the project page at:

https://github.com/michael-milette/moodle-filter_filtercodes

Troubleshooting

Why are tags displayed as entered instead of being converted to expected content/data?

Here are a few things you can check:

  • Make sure the plugin is enabled (On) for both Headings and Content in Site Administration > Plugins > Filters > Manage Filters. See installation instructions.
  • Make sure that the tag you are trying to use is supported in the version of FilterCodes you currently have installed on your Moodle site. See the CHANGELOG.md for the history of when tags were added.
  • Try testing using the {firstname} tag. It was one of the very first (it's not even in the history). If it works with this tags, it should work with others.
  • Make sure you specified any required parameters in your tag. In the case of the {langx} tag for example, make sure you included the 2 letter language code in the opening tag. Example: {langx fr}.
  • If the tags required a closing tag, make sure that it includes a forward slash and does not include any parameters. Example: {/ifenrolled}.
  • If the tag requires a closing tag, Make sure that the closing tag does not contain any parameters. Only opening tags may contain parameters.
  • If it doesn't work with a particular 3rd party theme (i.e. not included with Moodle), try it using it in the Boost theme.
  • If it doesn't work with a particular 3rd party plugin (i.e. not included with Moodle), try using the tag in an HTML block or label.
  • If you have determined that the problem is with a 3rd party plugin or theme, please report the issue to its developer using the Bug Tracker link on the plugin's page located at moodle.org/plugins. Provide as much information as you can. It may be helpful to point them to the Moodle Output API documentation, specifically the format_text() and format_string() functions.
  • If it still doesn't work, chances are that this some part of Moodle doesn't support filters yet. It is rare but it happens (example: Badges). Please report the part of Moodle that doesn't support filters in the Moodle Tracker.
  • Read the rest of this FAQ section.
  • If all else fails, ask questions. There are links on the FilterCodes plugin page to the Discussion forum for getting help and the Bug Tracker on GitHub for reporting bugs.

More helpful information can be found in the FAQ below.

FAQ

Answers to Frequently Asked Questions

IMPORANT: Although we expect everything to work, this release has not been fully tested in every situation. If you find a problem, please help by reporting it in the Bug Tracker.

Can I combine/nest conditional tags?

Yes. You can only combine (AND) them. The two or more tags must be true in order for the content to be displayed. For example:

{ifloggedin}{ifenrolled}You are logged-in and enrolled in this course.{/ifenrolled}{/ifloggedin}

This plugin does not support {IF this OR that} type conditions at this time. Depending on your requirement, the {ifmin...} tags might help you achieve this. These tags enable you to display content to users with a minimum role level. This could be useful if you wanted to only display a message to faculty such as (teacher or above).

I am using FilterCodes on a multi-language site. Some of my non-FilterCode tags are not being processed. How can I fix this?

This is actually a pretty common question. Simply move FilterCodes to the top of the list in your Moodle Filter Management. The only exception to this would be if one of your other filters were generating content that included FilterCode tags. In that case, place that plugin above FilterCodes.

How can I use this to pre-populate one or more fields in a Contact Form for Moodle?

Just put the tag in the input's value parameter. Here are a couple of examples:

<input id="email" name="email" type="email" required="required" value="{email}">
<input id="name" name="name" type="text" required="required" value="{fullname}">

Pro Tip: You can pre-populate a field and make it non-editable for logged-in users using a conditional tag:

<input id="email" name="email" type="email" required="required" {ifloggedin}readonly{/ifloggedin} value="{email}">
<input id="name" name="name" type="text" required="required" {ifloggedin}readonly{/ifloggedin} value="{fullname}">

Why do administrators see the text of all other roles when using {ifminxxxx}Content{/ifminxxxx} tags?

This is normal as the administrator has the permission of all other roles. The {ifmin...} tags will display content if the user has a minimum of the specified role or above. For example, {ifminteacher}Content here!{/ifminteacher} will display "Content here!" whether the user is a teacher, course creator, manager or administrator even if they are not a teacher.

Is there a tag to display...?

Only the tags listed in this documentation are currently supported (version on GitHub is often newer than on Moodle.org). We are happy to add new functionality in future releases of FilterCodes. Please post all requests in the Bug Tracker. You'll also find a link for this on the plugin's page. The subject line should start with "Feature Request: ".

When requesting a new tag, please provide:

  • As much detail as possible on what you are trying to accomplish.
  • An example of how it would be used.
  • If possible, where in Moodle the information would come from.

Be sure to check back on your issue as we may have further questions for you.

Why does the {button} tag not work?

It works just fine. Here are 3 examples:

{button https://www.tngconsulting.ca}TNG Consulting Inc.{/button}

This one just creates a button called TNG Consulting Inc. that will take you to the website when clicked.

{button https://google.ca" target="_blank}Google{/button}

This one will create a button called "Google" which will open a new tab in your browser and then take you to the website.

{button {wwwroot}/my}{getstring}myhome{/getstring}{/button}

The last one will create a button called "Dashboard", using the Moodle language strings ({getstrings} is a FilterCode too). When clicked, it will take the user to your Moodle site's dashboard, regardless of where Moodle is installed (webroot or subdirectory).

The trick is to make sure that Moodle doesn't convert the URL to a link in the editor. If it does (probably blue, underlined), you will need to use the Unlink tool to turn it back into plain text. Once saved, it will appear as a button. Alternatively, disable the Convert URLs into links and images filter in Site Administration > Plugins > Filters > Manage Filters and then re-enter the {button} FilterCode.

How can I style the {coursecontacts} tag?

Here is an example that reduces the image and places the information next to it. Just add this CSS to your site:

.fc-coursecontacts li {
    clear:both;
    font-size: 1.3rem;
    line-height: initial;
}
.fc-coursecontacts img {
    width: 40%;
    float: left;
}
.fc-coursecontactroles {
    display: block;
}
.fc-coursecontacts div {
border-top: 1px solid lightgrey;
margin-top: 5px;
padding-top: 5px
}

Do you have examples, samples and ways to which tags are working in my version of FilterCodes?

Create a Page on your Moodle site, preferably in a course, so that those tags work too, and include the following code:

View page content code
  • First name [{firstname}]: {firstname}
  • Surname [{surname}]: {surname}
  • Last name [{lastname}]: {lastname}
  • Full name [{fullname}]: {fullname}
  • Alternate name [{alternatename}]: {alternatename}
  • City [{city}]: {city}
  • Country [{country}]: {country}
  • Preferred timezone [{timezone}]: {timezone}
  • Preferred language [{preferredlanguage}]: {preferredlanguage}
  • Email [{email}]: {email}
  • User ID [{userid}]: {userid}
  • User ID (encoded) [%7Buserid%7D]: %7Buserid%7D
  • ID Number [{idnumber}]: {idnumber}
  • User name [{username}]: {username}
  • User description [{userdescription}] : {userdescription}
  • User web page URL [{webpage}] : {webpage}
  • Scrape h1 from example.com: {scrape url="https://example.com/" tag="h1"}
  • User profile picture URL (small) [{userpictureurl sm}]: {userpictureurl sm}
  • User profile picture URL (medium) [{userpictureurl md}]: {userpictureurl md}
  • User profile picture URL (large) [{userpictureurl lg}]: {userpictureurl lg}
  • User profile picture URL (small) [{userpictureimg sm}]: {userpictureimg sm}
  • User profile picture URL (medium) [{userpictureimg md}]: {userpictureimg md}
  • User profile picture URL (large) [{userpictureimg lg}]: {userpictureimg lg}
  • Total number of registered users [{usercount}]: {usercount}
  • Total number of active users [{usersactive}]: {usersactive}
  • Total number of online users [{usersonline}]: {usersonline}
  • Total number of users [{userscountrycount}]: {userscountrycount}
  • Current 4-digit year [{siteyear}]: {siteyear}
  • You first accessed the site on [{firstaccessdate strftimedatetime}] : {firstaccessdate strftimedatetime}
  • Course or Site full name [{coursename}]: {coursename}
  • Course or Site short name [{courseshortname}]: {courseshortname}
  • Course start date [{coursestartdate strftimedatetime}]: {coursestartdate strftimedatetime}
  • Course end date [{courseenddate strftimedatetime}]: {courseenddate strftimedatetime}
  • Completion date [{coursecompletiondate strftimedatetime}]: {coursecompletiondate strftimedatetime}
  • Course progress (ALPHA) [{courseprogress}]: {courseprogress}
  • Course progress bar (ALPHA) [{courseprogressbar}]: {courseprogressbar}
  • Course cards (ALPHA) [{coursecards}]: {coursecards}
  • Course cards by enrolment (ALPHA) [{coursecardsbyenrol}]: {coursecardsbyenrol}
  • Team cards Our faculty team [{teamcards}]: Our faculty team
    {teamcards}
  • Category cards (ALPHA) [{categorycards}]: {categorycards}
  • Category 1 cards (ALPHA) [{categorycards 1}]: Sub-categories of Miscellaneous category include {categorycards 1}
  • Total courses [{coursecount}]: {coursecount}
  • Institution [{institution}]: {institution}
  • Department [{department}]: {department}
  • Course ID [{courseid}]: {courseid}
  • Course ID (encoded) [%7Bcourseid%7D]: %7Bcourseid%7D
  • Course Context ID [{coursecontextid}]: {coursecontextid}
  • Course Context ID (encoded) [%7Bcoursecontextid%7D]: %7Bcoursecontextid%7D
  • Course Module ID (encoded) [%7Bcoursemoduleid%7D]: %7Bcoursemoduleid%7D (Note: Only available in a course activity)
  • Course ID number [{courseidnumber}]: {courseidnumber}
  • Section ID [{sectionid}]: {sectionid}
  • Section ID (encoded) [%7Bsectionid%7D]: %7Bsectionid%7D
  • Section Name [{sectionname}] : [{sectionname}]
  • Contacts in this course [{coursecontacts}]: {coursecontacts}
  • You current grade in this course is [{coursegradepercent}]: {coursegradepercent}
  • Available free application disk space [{diskfreespace}]: {diskfreespace}
  • Available free moodledata disk space [{diskfreespacedata}]: {diskfreespacedata}
  • My Enrolled Courses [{mycourses}]: {mycourses}
  • My Enrolled Courses menu [{mycoursesmenu}]: 
    {mycoursesmenu}
  • My Enrolled Courses as cards [{mycoursescards}]:
    {mycoursescards}
  • Link to the request a course page (blank if not enabled) [{courserequest}]: {courserequest}
  • Request a course / Course request in top level menu [{courserequestmenu0}]: 
    {courserequestmenu0}
  • Request a course / Course request in submenu [{courserequestmenu}]: 
    {courserequestmenu}
  • Label [{label info}]Criteria for completion[{/label}]: {label info}Criteria for completion{/label}
  • Button [{button https://moodle.org}]Go to Moodle.org{/button}]: {button https://moodle.org.org}Go to Moodle{/button}
  • 80% radial chart [{chart radial 80 Are you over 70%?}]: {chart radial 80 Are you over 70%?}
  • 60% pie chart [{chart pie 60 Are you over 70%?}]: {chart radial 60 Are you over 70%?}
  • 75% progressbar chart [{chart progressbar 75 Are you over 70%?}]: {chart radial 75 Are you over 70%?}
  • Moodle Admin custom menu items [{menuadmin}]: 
    {menuadmin}
  • Moodle Dev custom menu items [{menudev}]: 
    {menudev}
  • Course's category ID (0 if not in a course or category list of course) [{categoryid}]: {categoryid}
  • Course's category name (blank if not in a course) [{categoryname}]: {categoryname}
  • Course's category number (blank if not in a course) [{categorynumber}]: {categorynumber}
  • Course's category description (blank if not in a course) [{categorydescription}]: {categorydescription}
  • Course categories [{categories}]: {categories}
  • Course categories menu [{categoriesmenu}]: 
    {categoriesmenu}
  • Top level course categories [{categories0}]: {categories0}
  • Top level course categories menu [{categories0menu}]: 
    {categories0menu}
  • Other course categories in this category [{categoriesx}]: {categoriesx}
  • Other course categories in this categories menu [{categoriesxmenu}]: 
    {categoriesxmenu}
  • List of custom course fields [{course_fields}]: {course_fields}
  • Course custom fields [{course_field_location}] (assumes you have created a custom course field called "location"): {course_field_location}
  • Course description [{coursesummary}] : {coursesummary}
  • [{courseimage}] : {courseimage}
  • Number of participants in the course [{courseparticipantcount}] : {courseparticipantcount}
  • The base (root) URL of your Moodle site [{wwwroot}]: {wwwroot}
  • Site support name [{supportname}]: {supportname}
  • Site support email address [{supportemail}]: {supportemail}
  • Site support web page [{supportpage}]: {supportpage}
  • WWW for Contact Form [{wwwcontactform}]: {wwwcontactform}
  • Page path [{pagepath}]: {pagepath}
  • This URL [{thisurl}]: {thisurl}
  • This URL encoded [{thisurl_enc}]: {thisurl_enc}
  • Double encode this URL (useful for whatsurl parameters) [{urlencode}][{thisurl_enc}][{/urlencode}]: {urlencode}{thisurl_enc}{/urlencode}
  • Protocol [{protocol}]: {protocol}
  • IP Address [{ipaddress}]: {ipaddress}
  • Moodle session key [{sesskey}]: {sesskey}
  • Moodle session key [%7Bsesskey%7D]: %7Bsesskey%7D
  • Referer [{referer}]: {referer}
  • Referrer [{referrer}]: {referrer}
  • ReCAPTCHA [{recaptcha}]: {recaptcha}
  • Readonly (for form fields when logged-in) [{readonly}]: {readonly}
  • Soft hyphen [{-}]: AHyphenWillOnlyAppearHere{-}WhenThereIsNotEnoughSpace.
  • Non-breaking space [{nbsp}]: This{nbsp}: Is it! (view source code to see the non-breaking space)
  • Horizontal rule line [{hr}]: {hr}
  • English [{langx en}]Content[{/langx}]: {langx en}Content{/langx}
  • String with component [{getstring:filter_filtercodes}]filtername[{/getstring}]: {getstring:filter_filtercodes}filtername{/getstring}
  • String [{getstring}]Help[{/getstring}]: {getstring}help{/getstring}
  • Toggle editing menu [{toggleeditingmenu}]: {toggleeditingmenu}
  • Editing Toggle [{editingtoggle}]: Toggle editing
  • FontAwesome "fa-globe": v4.x [{fa fa-globe}] {fa fa-globe}, v5.x [{fas fa-globe}] {fas fa-globe}. Must be supported by your theme.
  • Glyphicons "glyphicon-envelope": Glyphicons [{glyphicon glyphicon-envelope}] {glyphicon glyphicon-envelope}. Must be supported by your theme.
  • Details/summary [{details}][{summary}]This is the summary[{/summary}] followed by the details.[{/details}]: {details}{summary}This is the summary{/summary} followed by the details.{/details}
  • You should not see the following note [{note}]This could be a comment, todo or reminder.[{/note}]: {note}This could be a comment, todo or reminder.{/note}
  • Click for [{help}content{/help}] : {help}Enables you to create popup help icons and bubbles just like Moodle does.{/help}
  • Click for [{info}content{/info}] : {Info}Enables you to create popup info icons and bubbles just like the Help popup but with an info icon. Useful for adding extra information or hidden tips in your content.{/info}
  • {alert}This is an example of an alert box.{/alert}
  • [{highlight}]This text is highlighted in yellow.[{/highlight}] : {highlight}This text is highlighted in yellow.{/highlight}
  • [{marktext}]This text is highlited in a different colour[{/marktext}] : {marktext}This text is highlited in a different colour{/marktext}
  • [{markborder}]This text has a red border around it[{/markborder}] : {markborder}This text has a red border around it{/markborder}
  • This is a course description. [{showmore}]These are the details.[{/showmore}] : This is a course description. {showmore}These are the details.{/showmore}
  • Current language [{lang}] : {lang}
  • Display content of custom user profile field [{profile_field_learningstyle}] - assuming you have a custom user profile field with a shortname called 'learningstyle': {profile_field_learningstyle}
  • Display profile owner's full name on profile pages [{profilefullname}]: This is the profile of {profilefullname}.
  • If you are logged-in as a different user [{ifloggedinas}] : {ifloggedinas}You are logged-in as a different user.{/ifloggedinas}
  • If you are NOT logged-in as a different user [{ifloggedinas}] : {ifnotloggedinas}You are logged-in as yourself.{/ifnotloggedinas}
  • If Editing mode activated (on) [{ifeditmode}]Don't forget to turn off editing mode![{/ifeditmode}]: {ifeditmode}Don't forget to turn off editing mode!{/ifeditmode}
  • If defined custom user profile field with a shortname called "iswoman" is not blank or zero [{ifprofile_field_iswoman}Female{/ifprofile_field_iswoman}]: {ifprofile_field_iswoman}Female{/ifprofile_field_iswoman}
  • If Editing mode is deactivated (off) [{ifnoteditmode}]<a href="{wwwroot}/course/view.php?id={courseid}&sesskey={sesskey}&edit=on">Turn edit mode on<a/>[{/ifnoteditmode}]: {ifnoteditmode}Turn edit mode on{/ifnoteditmode}
  • If Enrolled [{ifenrolled}]You are enrolled in this course.[{/ifenrolled}]: {ifenrolled}You are enrolled in this course.{/ifenrolled}
  • If Not Enrolled [{ifnotenrolled}]You are not enrolled in this course.[{/ifnotenrolled}]: {ifnotenrolled}You are not enrolled in this course.{/ifnotenrolled}
  • If LoggedIn [{ifloggedin}]You are logged-in.[{/ifloggedin}]: {ifloggedin}You are logged-in.{/ifloggedin}
  • If LoggedOut [{ifloggedout}]You are logged-out.[{/ifloggedout}]: {ifloggedout}You are logged-out.{/ifloggedout}
  • If Guest [{ifguest}]You are a guest.[{/ifguest}]: {ifguest}You are a guest.{/ifguest}
  • If Student [{ifstudent}]You are student who is logged-in and enrolled in this course and have no other roles.[{/ifstudent}]: {ifstudent}You are student who is logged-in and enrolled in this course and have no other roles.{/ifstudent}
  • If Non-editing Teacher [{ifassistant}]You are an assistant teacher.[{/ifassistant}]: {ifassistant}You are an assistant teacher.{/ifassistant}
  • If Non-editing Teacher (minimum) [{ifminassistant}]You are an assistant teacher or above.[{/ifminassistant}]: {ifminassistant}You are an assistant teacher or above.{/ifminassistant}
  • If Teacher [{ifteacher}You are a teacher.{/ifteacher}]: {ifteacher}You are a teacher.{/ifteacher}
  • If Teacher (minimum) [{ifminteacher}]You are a teacher or above.[{/ifminteacher}]: {ifminteacher}You are a teacher or above.{/ifminteacher}
  • If Course Creator [{ifcreator}]You are a course creator.[{/ifcreator}]: {ifcreator}You are a course creator.{/ifcreator}
  • If Course Creator (minimum) [{ifmincreator}]You are a course creator or above.[{/ifmincreator}]: {ifmincreator}You are a course creator or above.{/ifmincreator}
  • If Manager [{ifmanager}]You are a manager.[{/ifmanager}]: {ifmanager}You are a manager.{/ifmanager}
  • If Manager (minimum) [{ifminmanager}]You are a manager or administrator.[{/ifminmanager}]: {ifminmanager}You are a manager or administrator.{/ifminmanager}
  • If Site Manager (minimum) [{ifminsitemanager}]You are a site manager or administrator.[{/ifminsitemanager}]: {ifminsitemanager}You are a site manager or administrator.{/ifminsitemanager}
  • If Admin [{ifadmin}]You are an administrator.[{/ifadmin}]: {ifadmin}You are an administrator.{/ifadmin}
  • If Developer [{ifdev}]You are an administrator with debugging set to developer mode.[{/ifdev}]: {ifdev}You are an administrator with debugging set to developer mode.{/ifdev}
  • If user has a parent custom role [{ifcustomrole parent}]You have a parent custom role in this context[{/ifcustomrole}]: {ifcustomrole parent}You have a parent custom role in this context{/ifcustomrole}.
  • If user does not have a parent custom role [{ifnotcustomrole parent}]You do not have a parent custom role in this context[{/ifnotcustomrole}]: {ifnotcustomrole parent}You do not have a parent custom role in this context{/ifnotcustomrole}.
  • If on Home page [{ifhome}]You are on the Home Front page.[{/ifhome}]: {ifhome}You are on the Home Front page.{/ifhome}
  • If not on the Home page [{ifnothome}]You are NOT on the Home Front page.[{/ifnothome}]: {ifnothome}You are NOT on the Home Front page.{/ifnothome}
  • If on Dashboard [{ifdashboard}]You are on the Dashboard page.[{/ifdashboard}]: {ifdashboard}You are on the Dashboard page.{/ifdashboard}
  • If in a course [{ifincourse}]Yes[{/ifincourse}]? {ifincourse}Yes{/ifincourse}
  • If in a section of a course [{ifinsection}]Yes[{/ifinsection}][{ifnotinsection}]No[{/ifnotinsection}]? {ifinsection}Yes{/ifinsection}{ifnotinsection}No{/ifnotinsection}
  • If Request a course is enabled [{ifcourserequests}]Yes[{/ifcourserequests}]? {ifcourserequests}Yes{/ifcourserequests}
  • Are you a member of the "moodlers" cohort [{ifincohort moodlers}]Yes[{/ifincohort}]? {ifincohort moodlers}Yes{/ifincohort} (will be blank of not a member of cohort)
  • Is your tenant id 1? [{iftenant 1}]Yes[{/iftenant}] : {iftenant 1}Yes{/iftenant} Note: In Moodle classic, tenant id is assumed to be 1.
  • Is this Moodle Workplace? [{ifworkplace}]Yes[{/ifworkplace}] : {ifworkplace}Yes{/ifworkplace}
  • This is FilterCodes version [{filtercodes}] : {filtercodes} Note: Will be blank if you do not have the ability to edit this tag.
  • Are you a member of the ATEAM group [{ifingroup ATEAM}]Yes[{/ifingroup}] ? : {ifingroup ATEAM}Yes{/ifingroup} Note: Only works in courses.
  • [{ifnotvisible}]Warning: Course visibility is set to Hide.[{/ifnotvisible}] : {ifnotvisible}Warning: Course visibility is set to Hide.{/ifnotvisible}
  • It is now [{now}] : {now}
  • It is now [{now backupnameformat}] : {now backupnameformat}
  • It is now [{now strftimedate}] : {now strftimedate}
  • It is now [{now strftimedatemonthabbr}] : {now strftimedatemonthabbr}
  • It is now [{now strftimedatefullshort}] : {now strftimedatefullshort}
  • It is now [{now strftimedateshort}] : {now strftimedateshort}
  • It is now [{now strftimedateshortmonthabbr}] : {now strftimedateshortmonthabbr}
  • It is now [{now strftimedatetime}] : {now strftimedatetime}
  • It is now [{now strftimedaydate}] : {now strftimedaydate}
  • It is now [{now strftimedaydatetime}] : {now strftimedaydatetime}
  • It is now [{now strftimedayshort}] : {now strftimedayshort}
  • It is now [{now strftimedaytime}] : {now strftimedaytime}
  • It is now [{now strftimemonthyear}] : {now strftimemonthyear}
  • It is now [{now strftimerecent}] : {now strftimerecent}
  • It is now [{now strftimerecentfull}] : {now strftimerecentfull}
  • It is now [{now strftimetime}] : {now strftimetime}
  • It is now [{now strftimetime12}] : {now strftimetime12}
  • It is now [{now strftimetime24}] : {now strftimetime24}
You can switch to different roles to see how each will affect the content being displayed.

When a user is logged out, the First name, Surname, Full Name, Email address and Username are empty. How can I set default values for these tags?

You can do this using the language editor built into Moodle. There is currently support for the following defaults: defaultfirstname, defaultsurname, defaultusername, defaultemail. By default, these are blank. As for the Full Name, it is made up of the first name and surname separated by a space and is therefore not settable.

I added the "{mycoursesmenu}" to my custom menu. How can I hide it if the user is not logged in?

You can use the {ifloggedin}{/ifloggedin} tags to conditionally hide it when users are not logged in. Example:

{ifloggedin}My Courses {mycoursesmenu}{/ifloggedin}

How can I add a "Logout" link in my custom menu?

Just add the following line to your custom menu (under Appearance > Theme settings)

{ifloggedin}Logout|/login/logout.php?sesskey={sesskey}{/ifloggedin}

Bonus: This is also how you would hide it for users who are not logged-in.

How can I create a menu that is just for administrators or some other roles?

Building on the previous two questions, see the usage section for some examples. Feel free to share your own ideas in the discussion forum.

Why is the IP Address listed as 0:0:0:0:0:0:0:1?

0:0:0:0:0:0:0:1 is the same as localhost and it means that your web browser is probably on the same computer as your web server. This shouldn't happen with users accessing your Moodle site from their own desktop or mobile device.

Why does it show me as enrolled on the front page?

The Front Page is a course in Moodle. All users are enrolled by default in this course.

I added the {recaptcha} tag in my web form. Why doesn't the reCAPTCHA show up?

First, the reCAPTCHA is only made to work with forms processed by the Contact Form for Moodle plugin. That said, it is 100% generated by Moodle API so, if you have some other purpose, it will probably work as well as long as the receiving form is made to process it.

In order for reCAPTCHA to work, you need to configure the site and secret keys in Moodle. For more information, log into your Moodle site as an Administrator and the navigate to Home > Site Administration > Authentication > Manage Authentication and configure the ReCAPTCHA site key and ReCAPTCHA secret key. You will also need to enable ReCAPTCHA in the settings of the Contact Form plugin.

If you are using older versions of Moodle before 3.1.11+, 3.2.8+, 3.3.5+, 3.4.5+ and 3.5+, ReCAPTCHA is no longer supported.

How can I get the {scrape} tag to work?

You need to enable this feature in the FilterCodes settings in Moodle.

How can I scrape content from more than one web page or more than one website?

Use multiple {scrape} tags.

How can I scrape content based on a pattern of HTML tags instead of just one HTML tag with a class or id? Example, an h1 tag inside the div class="content" tag.

That is not possible at this time. This is a very simple scraper. With some funding or contributions, this feature can be enhanced.

How can I get the {getstring} tag to work? It doesn't seem to be replaced with the correct text.

Verify that the component (plugin) name and/or the string key are correct. If a component name is not specified, it will default to "moodle". If you recently modified a language file manually in Moodle, you may need to refresh the Moodle cache.

How can I customize or translate the forms generated by the {form...} tags?

See Customizing or translating the forms generated by the {form...} tags in the Usage section.

What are the Supported dateTimeFormat formats?

The date and time formats, defined in Moodle (langconfig.php)[https://github.com/moodle/moodle/blob/master/lang/en/langconfig.php], control how dates and times will be displayed.

At this time, only the following formats are supported:

  • backupnameformat
  • strftimedate
  • strftimedatemonthabbr
  • strftimedatefullshort
  • strftimedateshort
  • strftimedateshortmonthabbr
  • strftimedatetime
  • strftimedaydate
  • strftimedaydatetime
  • strftimedayshort
  • strftimedaytime
  • strftimemonthyear
  • strftimerecent
  • strftimerecentfull
  • strftimetime
  • strftimetime12
  • strftimetime24

Note: the displayed date and/or time format can vary depending on the language pack in use. While you can customize these using the Moodle language customization tool included with Moodle, be aware that this will have affect displayed dates that use the modified format throughout your Moodle site. Pro tip: Standardize the date format used throughout your site as much as possible in order to minimize the chance of potentially confusing your learners.

ALPHA WARNING: You may discover that you can also use (strftime)[https://www.php.net/manual/en/function.strftime.php] formats. However, in some situations, strftime may produce undesirable results - missing unrelated content in your page for example. The strftime formats are officially unsupported at this time. This is a known issue and is not recommended at this time. Please do not report issues with it. Use strftime formats at your own risk.

Are there any security considerations?

There are no known security considerations at this time.

How can I get answers to other questions?

Got a burning question that is not covered here? If you can't find your answer, submit your question in the Moodle forums or open a new issue on Github at:

https://github.com/michael-milette/moodle-filter_filtercodes/issues

(Back to top)

Contributing

If you are interested in helping, please take a look at our contributing guidelines for details on our code of conduct and the process for submitting pull requests to us.

Contributors

Michael Milette - Author and Lead Developer

Big thank you to the following contributors. (Please let me know if I forgot to include you in the list):

  • 3iPunt and abertranb: New {ifcustomrole} tag (2020).
  • 3iPunt and abertranb: New {ifnotcustomrole} tag (2020).
  • andrewhancox: Enhanced {coursecards} tag (2020).
  • comete-upn: New {getstring} tag (2018).
  • ewallah: Testing of phpunit testing script (2019).
  • pablojavier: New {iftenant} tag (2020).
  • petermApredne: New {coursecompletiondate} tag (2020).
  • petermApredne: New {courseenddate} tag (2020).
  • petermApredne: New {coursestartdate} tag (2020).
  • petermApredne: New {firstaccessdate} tag (2020).
  • rschrenk: Enhanced [{tag}] commenting options (2020).
  • vpn: Enhanced {alert} tag (2020).

Thank you also to all the people who have requested features, tested and reported bugs.

Pending Features

Some of the features we are considering for future releases include:

  • Catch-up on developing unit testing.
  • Add ability to access course meta information.
  • Add ability to list courses in the current course's category.
  • Add ability to list subcategories of the current category.
  • Add settings page with option to disable unused or unwanted filters in order to optimize performance or simply disable features.
  • Create an Atto add-on (separate plugin) to make it easier to insert FilterCodes tags.

If you could use any of these features, or have other requirements, consider contributing or hiring us to accelerate development.

(Back to top)

Motivation for this plugin

The development of this plugin was motivated through our own experience in Moodle development, features requested by out clients and topics discussed in the Moodle forums. The project is sponsored and supported by TNG Consulting Inc.

(Back to top)

Further Information

For further information regarding the filter_filtercodes plugin, support or to report a bug, please visit the project page at:

https://github.com/michael-milette/moodle-filter_filtercodes

(Back to top)

License

Copyright © 2017-2022 TNG Consulting Inc. - https://www.tngconsulting.ca/

This file is part of FilterCodes for Moodle - https://moodle.org/

FilterCodes is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

FilterCodes is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with FilterCodes. If not, see https://www.gnu.org/licenses/.

(Back to top)

moodle-filter_filtercodes's People

Contributors

michael-milette avatar pablojavier avatar vpn avatar petermaprende avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.