MoodleDocs - Contribuciones del usuario [es]

Seguridad de Moodle app

2025-04-30T08:48:12Z

Jleyva: /* Warnings typically raised by static code analysis tools */

{{Mobile}}
{{Urgente de traducir}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the Cordova and Moodle security recommendations:
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We do occasionally receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of existing non-official plugins to support it showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally (there are hundreds of thousands of sites, each one with its own URL, using Moodle), whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token.

These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

[[en:Moodle app security]]

Moodle app FAQ

2024-03-01T11:38:52Z

Jleyva: /* Administradores */

{{Frequently updated doc page
|docpagetitle = Mobile Moodle FAQ
}}{{Mobile}}{{Urgente de traducir}}{{Actualizar}}
{{Versiones|Esta documentación es para Moodle 3.7 y más recientes, pero existe una página antigua en [[30/Moodle Mobile FAQ]]}}

== Nuevos Planes para Moodle App Plans (a partir del 2 de Abril del 2020) ==

Por favor vea el anuncio oficial: [https://moodle.org/mod/forum/discuss.php?d=397926 Introducing our new Moodle App plans]

=== ¿La App sigue siendo gratuita para descargar y usar?===

Si; la App misma es gratuita. Students and teachers who use the Moodle app will never pay any fees. Moodle site administrators can choose to sign up for a plan.

=== ¿Pueden explicarme las diferentes limitaciones? ===

First and most important, the limitations are applied on a site basis.

* Basic custom branding via CSS: Site admins can upload a CSS file with basic styles for the app. The styles will only be applied on Premium sites. See [[Moodle app guía para administradores]] for more information about this functionality.
* Number of active devices for mobile push notifications: Calculated monthly, this is the number of user devices actively receiving push notifications from the site. For example, for a site with 100 users enrolled, if half of them are using the app with one device configured to receive notifications, the potential number of active devices per month will be 50. In the Free plan, where the limit is set to 50, only the first 50 devices in a month will receive notifications from the site.
* Offline access to content: Complete courses available offline. Contents downloaded individually will be still available offline, but the user will be able to download complete courses for offline access to a certain limit depending on the plan.
* Customisable app features: These are app features that can be configured via the Moodle site administration tools (Moodle app section). For details, see [[Moodle app guía para administradores#Características deshabilitadas]].

=== Soy un cliente de un Moodle Partner. ¿Esto me afecta? ===

If your Moodle site is hosted by a Moodle Partner, the changes will not affect you. However, if your Moodle Partner doesn't host your site, you may need to sign up for a plan, move to MoodleCloud or ask your Moodle Partner to host your site from April 2020 onwards.

=== Soy un profesor o un estudiante. ¡Tengo que hacer algo respecto a mi Moodle app? ===

No, you don’t have to do anything. We are notifying site administrators about the upcoming changes so they can take action if necessary.

=== ¿Tendré que instalar una nueva App a pertir del 2 de abril del 2020? ===

No, the app will remain the same, but depending on the plan your institution has signed up for, you may have limited access to certain functionalities.

=== ¿Cómo se si necesito actualizar a un Plan de Moodle App? ===

If you are using MoodleCloud or your site is hosted by a Moodle Partner, you won’t be affected by these changes. Otherwise, in the last week of March 2020, site administrators will be provided with a link to the Moodle App Portal, where they will be able to register their site and obtain information such as the number of active devices receiving push notifications during the last month.

Site administrators should also check if they are using any of the “Customisable app features” (via Site administration > Mobile app > Mobile app features) as continued use will require upgrading to a plan.

=== ¿Necesito apuntarme al plan gratuito para poder usar la App? ===

No, though we encourage all site administrators to sign up in our Moodle Apps portal in order to obtain information about active devices receiving push notifications.

=== ¿Cómo puedo actualizar a uno de los planes? ===

During the last week of March 2020, site administrators will be provided with a link to the Moodle App Portal, where they will be able to sign up for a plan.

Remember that you can also migrate to a MoodleCloud plan, ask a Moodle Partner to host your site or build your own version of the app using the open source code.

=== ¿Cómo pago un plan? ===

For activation of any of the paid plans, you will need to make a credit card payment, PayPal will be also supported.

For payments via bank transfer to Moodle Pty Ltd, a minimum of a two years Premium subscription will be required (so we can cover all the administrative work and bank fees). Once you've chosen this method, the Premium plan will be automatically activated (only during March and April this year). Notice that you'll have 4 weeks for processing payment. If after those 4 weeks we haven't received the payment yet, the plan will be canceled and you will get back to the free plan and penalties can be applied in further payments.

=== Will students lose access to the app if we don’t upgrade straight away on 2 April 2020? ===

No, students will still be able to use the app. Depending on the size of your installation, your use of push notifications and the use of customised features, your students may stop receiving notifications or no longer be able to use specific features.

=== Si somos una ONG o una organización no lucrativa, ¿Necesitamos actualizar? ¡Necesitamos pagar? ===

We will create a process to ensure that NGOs and non-profit organisations do not need to pay and can benefit from our Premium Plan. Upon receipt of the necessary documentation and validation from Moodle HQ, organisations will have full access. Please note though that the verification process may take several weeks. Public universities, colleges and schools are not eligible for this.

=== Is this affecting only certain Moodle versions? ===
The changes will affect all the Moodle versions supported by the app (Moodle 3.1 onward)

=== ¿Qué pasa con los sitios que no están registrados con Moodle? ===

We recommend all site administrators to register their site in order to receive important notifications about the product. Moreover, the validation process to sign up for a plan will be easier.

=== Con los nuevos planes que vendrán, ¿hay algún acmbio que potencialmente afectará la privacidad de los usuarios? ===

No.

==Estudiantes==

===¿Cómo puedo obtener la Moodle app?===

The Moodle app is available for free from Google Play and the Apple Store. See [https://download.moodle.org/mobile/ Moodle app downloads] for links. You can also install the app directly from your mobile device by searching for 'Moodle app' with author/owner 'Moodle Pty Ltd'.

===I can't get the app to work. What do I do?===

The Moodle app will ONLY work with Moodle sites that have been set up to allow it. Please talk to your Moodle administrator if you have any problems connecting.

===What permissions does the app require?===

The app requires the following permissions:

* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.

=== ¿Porqué no puedo subir mi Tarea a la app?===
Consulte a su administrador de Moodle.

===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your Moodle site administrator.

===Is there a space limit on my files?===
Assignments will have a size limit which you can see. For other space limit questions, check with your Moodle site administrator.

===Who should I contact for help with the app?===
Your Moodle site administrator can assist you in getting the app to work correctly.

===When are activities completed offline synchronized?===

Vea [[Sincronización de Moodle app]].

===Why the site is asking for my username and password when an activity is opened in the browser?===

Auto-login from the app is only supported in sites using Moodle 3.2 onwards. Also, for security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).

===I use LineageOS and I'm having problems using the app===

LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.

===Los paquetes H5P y contenidos externos incrustados vía iframes no están funcionando en iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.

=== No recibo notificaciones del calendario (recordatorios) cuando uso Android 12 o superior ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Profesores==

===How can I enable videos in my course to be downloaded?===

See the section 'Media download for offline usage' in [[Crear cursos amistosos para mobile]].

===Video subtitles are not working===

This may happen in old Android versions (Android < 4.4), in modern Android and iOS versions they should work fine.

===Which course format is it best to use?===

Topics or weekly course format is best suited to mobile devices.

===How do I make YouTube links open automatically in the app?===

Add YouTube links as a [[Recurso URL]].

===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.

=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).

===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.

===My protected Vimeo videos are not playing in the app===

Vimeo protected videos should work on Moodle 3.3.4 onwards, please note that you need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">

For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

===ReCaptcha doesn't work on my site===

You need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

===H5P packages don't work on my site===

You need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

=== I have problems playing SCORM packages ===

This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)

Please refer to [[Moodle app SCORM player]] for additional information.

=== My quizzes or lessons are not working offline ===

You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.

=== Maths notation is not displaying correctly in the app ===

The app doesn't yet support MathJax (see MOBILE-1611). Instead, the [[Filtro de notación TeX]] should be enabled.

=== How can I disable text selection / copy in the app? ===

You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes

=== My images, videos or audios stop working after the first time ===

Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administradores==

=== How can I debug errors in the app? ===

Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== I can connect with my iPhone but not with my Android phone ===

This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.geocerts.com/ssl_checker and https://www.ssllabs.com/ssltest/analyze.html

===I can't get the app to work. What can I do?===

Assuming you have enabled mobile services on your site, please check:

# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker] and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# [[Depuración]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, and /tokenpluginfile.php

If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

=== I cannot access with old users, but I can with recently created ones! ===

Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.

===I can't view the courses tab as an administrator===

The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.

===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===

See the section 'Mobile authentication' in the [[Moodle app guía para administradores]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===

SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:

* It launchs this URL https://yourmoodle/local/mobile/launch.php?service=local_mobile&passport=abc in the device browser (Moodle 3.2 onwards the URL is /tool/mobile instead local/mobile)
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/local/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol

Custom auth plugins may be failing in the last step,not redirecting back to local/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.

===I am having problems requesting an airnotifier access key===

If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===

Please check [[Mobile app notifications#Troubleshooting]]

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474

===I think I found a bug with the app. Where can I report it?===

# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button

===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

If the Moodle app is not yet available in your language, please contribute a translation! See [[:dev:Translating Moodle Mobile|Translating Moodle Mobile]] for details of what to do.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

==Error messages==

=== 'Can not find data record in database table external_functions' ===

This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.

==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 2.4 or later'===

Please check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)

==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===

Please check:
# You have followed all the steps listed in [[:dev:Moodle Mobile Developing a plugin tutorial|Moodle Mobile Developing a plugin tutorial]]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user

==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===

You need to create a token for the admin account (only) as follows:

# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.

==='Invalid response value detected' when accessing the site ===

The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].

=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===

This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)

==='Invalid response value detected' when accessing My Courses or Course Overview ===

This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".

==='A required parameter (username) was missing'===

This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.

==='Invalid json in request: No error'===

There is a bug in Moodle 3.3 that can cause this error. Please update to Moodle 3.3.2.

==='Cannot get course contents'===

This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.

==='Access control exception' or 'Your authentication token is invalid or has expired'===

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:

# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Categoría:FAQ]]

[[de:Moodle Mobile FAQ]]
[[ca:Moodle Mobile FAQ]]
[[en:Moodle Mobile FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:モバイルMoodle FAQ]]

Moodle app FAQ

2024-03-01T11:38:37Z

Jleyva: /* Error messages */

{{Frequently updated doc page
|docpagetitle = Mobile Moodle FAQ
}}{{Mobile}}{{Urgente de traducir}}{{Actualizar}}
{{Versiones|Esta documentación es para Moodle 3.7 y más recientes, pero existe una página antigua en [[30/Moodle Mobile FAQ]]}}

== Nuevos Planes para Moodle App Plans (a partir del 2 de Abril del 2020) ==

Por favor vea el anuncio oficial: [https://moodle.org/mod/forum/discuss.php?d=397926 Introducing our new Moodle App plans]

=== ¿La App sigue siendo gratuita para descargar y usar?===

Si; la App misma es gratuita. Students and teachers who use the Moodle app will never pay any fees. Moodle site administrators can choose to sign up for a plan.

=== ¿Pueden explicarme las diferentes limitaciones? ===

First and most important, the limitations are applied on a site basis.

* Basic custom branding via CSS: Site admins can upload a CSS file with basic styles for the app. The styles will only be applied on Premium sites. See [[Moodle app guía para administradores]] for more information about this functionality.
* Number of active devices for mobile push notifications: Calculated monthly, this is the number of user devices actively receiving push notifications from the site. For example, for a site with 100 users enrolled, if half of them are using the app with one device configured to receive notifications, the potential number of active devices per month will be 50. In the Free plan, where the limit is set to 50, only the first 50 devices in a month will receive notifications from the site.
* Offline access to content: Complete courses available offline. Contents downloaded individually will be still available offline, but the user will be able to download complete courses for offline access to a certain limit depending on the plan.
* Customisable app features: These are app features that can be configured via the Moodle site administration tools (Moodle app section). For details, see [[Moodle app guía para administradores#Características deshabilitadas]].

=== Soy un cliente de un Moodle Partner. ¿Esto me afecta? ===

If your Moodle site is hosted by a Moodle Partner, the changes will not affect you. However, if your Moodle Partner doesn't host your site, you may need to sign up for a plan, move to MoodleCloud or ask your Moodle Partner to host your site from April 2020 onwards.

=== Soy un profesor o un estudiante. ¡Tengo que hacer algo respecto a mi Moodle app? ===

No, you don’t have to do anything. We are notifying site administrators about the upcoming changes so they can take action if necessary.

=== ¿Tendré que instalar una nueva App a pertir del 2 de abril del 2020? ===

No, the app will remain the same, but depending on the plan your institution has signed up for, you may have limited access to certain functionalities.

=== ¿Cómo se si necesito actualizar a un Plan de Moodle App? ===

If you are using MoodleCloud or your site is hosted by a Moodle Partner, you won’t be affected by these changes. Otherwise, in the last week of March 2020, site administrators will be provided with a link to the Moodle App Portal, where they will be able to register their site and obtain information such as the number of active devices receiving push notifications during the last month.

Site administrators should also check if they are using any of the “Customisable app features” (via Site administration > Mobile app > Mobile app features) as continued use will require upgrading to a plan.

=== ¿Necesito apuntarme al plan gratuito para poder usar la App? ===

No, though we encourage all site administrators to sign up in our Moodle Apps portal in order to obtain information about active devices receiving push notifications.

=== ¿Cómo puedo actualizar a uno de los planes? ===

During the last week of March 2020, site administrators will be provided with a link to the Moodle App Portal, where they will be able to sign up for a plan.

Remember that you can also migrate to a MoodleCloud plan, ask a Moodle Partner to host your site or build your own version of the app using the open source code.

=== ¿Cómo pago un plan? ===

For activation of any of the paid plans, you will need to make a credit card payment, PayPal will be also supported.

For payments via bank transfer to Moodle Pty Ltd, a minimum of a two years Premium subscription will be required (so we can cover all the administrative work and bank fees). Once you've chosen this method, the Premium plan will be automatically activated (only during March and April this year). Notice that you'll have 4 weeks for processing payment. If after those 4 weeks we haven't received the payment yet, the plan will be canceled and you will get back to the free plan and penalties can be applied in further payments.

=== Will students lose access to the app if we don’t upgrade straight away on 2 April 2020? ===

No, students will still be able to use the app. Depending on the size of your installation, your use of push notifications and the use of customised features, your students may stop receiving notifications or no longer be able to use specific features.

=== Si somos una ONG o una organización no lucrativa, ¿Necesitamos actualizar? ¡Necesitamos pagar? ===

We will create a process to ensure that NGOs and non-profit organisations do not need to pay and can benefit from our Premium Plan. Upon receipt of the necessary documentation and validation from Moodle HQ, organisations will have full access. Please note though that the verification process may take several weeks. Public universities, colleges and schools are not eligible for this.

=== Is this affecting only certain Moodle versions? ===
The changes will affect all the Moodle versions supported by the app (Moodle 3.1 onward)

=== ¿Qué pasa con los sitios que no están registrados con Moodle? ===

We recommend all site administrators to register their site in order to receive important notifications about the product. Moreover, the validation process to sign up for a plan will be easier.

=== Con los nuevos planes que vendrán, ¿hay algún acmbio que potencialmente afectará la privacidad de los usuarios? ===

No.

==Estudiantes==

===¿Cómo puedo obtener la Moodle app?===

The Moodle app is available for free from Google Play and the Apple Store. See [https://download.moodle.org/mobile/ Moodle app downloads] for links. You can also install the app directly from your mobile device by searching for 'Moodle app' with author/owner 'Moodle Pty Ltd'.

===I can't get the app to work. What do I do?===

The Moodle app will ONLY work with Moodle sites that have been set up to allow it. Please talk to your Moodle administrator if you have any problems connecting.

===What permissions does the app require?===

The app requires the following permissions:

* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.

=== ¿Porqué no puedo subir mi Tarea a la app?===
Consulte a su administrador de Moodle.

===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your Moodle site administrator.

===Is there a space limit on my files?===
Assignments will have a size limit which you can see. For other space limit questions, check with your Moodle site administrator.

===Who should I contact for help with the app?===
Your Moodle site administrator can assist you in getting the app to work correctly.

===When are activities completed offline synchronized?===

Vea [[Sincronización de Moodle app]].

===Why the site is asking for my username and password when an activity is opened in the browser?===

Auto-login from the app is only supported in sites using Moodle 3.2 onwards. Also, for security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).

===I use LineageOS and I'm having problems using the app===

LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.

===Los paquetes H5P y contenidos externos incrustados vía iframes no están funcionando en iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.

=== No recibo notificaciones del calendario (recordatorios) cuando uso Android 12 o superior ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Profesores==

===How can I enable videos in my course to be downloaded?===

See the section 'Media download for offline usage' in [[Crear cursos amistosos para mobile]].

===Video subtitles are not working===

This may happen in old Android versions (Android < 4.4), in modern Android and iOS versions they should work fine.

===Which course format is it best to use?===

Topics or weekly course format is best suited to mobile devices.

===How do I make YouTube links open automatically in the app?===

Add YouTube links as a [[Recurso URL]].

===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.

=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).

===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.

===My protected Vimeo videos are not playing in the app===

Vimeo protected videos should work on Moodle 3.3.4 onwards, please note that you need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">

For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

===ReCaptcha doesn't work on my site===

You need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

===H5P packages don't work on my site===

You need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

=== I have problems playing SCORM packages ===

This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)

Please refer to [[Moodle app SCORM player]] for additional information.

=== My quizzes or lessons are not working offline ===

You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.

=== Maths notation is not displaying correctly in the app ===

The app doesn't yet support MathJax (see MOBILE-1611). Instead, the [[Filtro de notación TeX]] should be enabled.

=== How can I disable text selection / copy in the app? ===

You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes

=== My images, videos or audios stop working after the first time ===

Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administradores==

=== How can I debug errors in the app? ===

Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== I can connect with my iPhone but not with my Android phone ===

This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.geocerts.com/ssl_checker and https://www.ssllabs.com/ssltest/analyze.html

===I can't get the app to work. What can I do?===

Assuming you have enabled mobile services on your site, please check:

# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker] and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# [[Depuración]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, and /tokenpluginfile.php

If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

=== I cannot access with old users, but I can with recently created ones! ===

Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.

===I can't view the courses tab as an administrator===

The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.

===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===

See the section 'Mobile authentication' in the [[Moodle app guía para administradores]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===

SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:

* It launchs this URL https://yourmoodle/local/mobile/launch.php?service=local_mobile&passport=abc in the device browser (Moodle 3.2 onwards the URL is /tool/mobile instead local/mobile)
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/local/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol

Custom auth plugins may be failing in the last step,not redirecting back to local/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.

===I am having problems requesting an airnotifier access key===

If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===

Please check [[Mobile app notifications#Troubleshooting]]

==Error messages==

=== 'Can not find data record in database table external_functions' ===

This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.

==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 2.4 or later'===

Please check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)

==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===

Please check:
# You have followed all the steps listed in [[:dev:Moodle Mobile Developing a plugin tutorial|Moodle Mobile Developing a plugin tutorial]]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user

==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===

You need to create a token for the admin account (only) as follows:

# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.

==='Invalid response value detected' when accessing the site ===

The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].

=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===

This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)

==='Invalid response value detected' when accessing My Courses or Course Overview ===

This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".

==='A required parameter (username) was missing'===

This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.

==='Invalid json in request: No error'===

There is a bug in Moodle 3.3 that can cause this error. Please update to Moodle 3.3.2.

==='Cannot get course contents'===

This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.

==='Access control exception' or 'Your authentication token is invalid or has expired'===

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:

# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Categoría:FAQ]]

[[de:Moodle Mobile FAQ]]
[[ca:Moodle Mobile FAQ]]
[[en:Moodle Mobile FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:モバイルMoodle FAQ]]

Moodle app FAQ

2024-03-01T11:38:07Z

Jleyva: /* Error messages */

{{Frequently updated doc page
|docpagetitle = Mobile Moodle FAQ
}}{{Mobile}}{{Urgente de traducir}}{{Actualizar}}
{{Versiones|Esta documentación es para Moodle 3.7 y más recientes, pero existe una página antigua en [[30/Moodle Mobile FAQ]]}}

== Nuevos Planes para Moodle App Plans (a partir del 2 de Abril del 2020) ==

Por favor vea el anuncio oficial: [https://moodle.org/mod/forum/discuss.php?d=397926 Introducing our new Moodle App plans]

=== ¿La App sigue siendo gratuita para descargar y usar?===

Si; la App misma es gratuita. Students and teachers who use the Moodle app will never pay any fees. Moodle site administrators can choose to sign up for a plan.

=== ¿Pueden explicarme las diferentes limitaciones? ===

First and most important, the limitations are applied on a site basis.

* Basic custom branding via CSS: Site admins can upload a CSS file with basic styles for the app. The styles will only be applied on Premium sites. See [[Moodle app guía para administradores]] for more information about this functionality.
* Number of active devices for mobile push notifications: Calculated monthly, this is the number of user devices actively receiving push notifications from the site. For example, for a site with 100 users enrolled, if half of them are using the app with one device configured to receive notifications, the potential number of active devices per month will be 50. In the Free plan, where the limit is set to 50, only the first 50 devices in a month will receive notifications from the site.
* Offline access to content: Complete courses available offline. Contents downloaded individually will be still available offline, but the user will be able to download complete courses for offline access to a certain limit depending on the plan.
* Customisable app features: These are app features that can be configured via the Moodle site administration tools (Moodle app section). For details, see [[Moodle app guía para administradores#Características deshabilitadas]].

=== Soy un cliente de un Moodle Partner. ¿Esto me afecta? ===

If your Moodle site is hosted by a Moodle Partner, the changes will not affect you. However, if your Moodle Partner doesn't host your site, you may need to sign up for a plan, move to MoodleCloud or ask your Moodle Partner to host your site from April 2020 onwards.

=== Soy un profesor o un estudiante. ¡Tengo que hacer algo respecto a mi Moodle app? ===

No, you don’t have to do anything. We are notifying site administrators about the upcoming changes so they can take action if necessary.

=== ¿Tendré que instalar una nueva App a pertir del 2 de abril del 2020? ===

No, the app will remain the same, but depending on the plan your institution has signed up for, you may have limited access to certain functionalities.

=== ¿Cómo se si necesito actualizar a un Plan de Moodle App? ===

If you are using MoodleCloud or your site is hosted by a Moodle Partner, you won’t be affected by these changes. Otherwise, in the last week of March 2020, site administrators will be provided with a link to the Moodle App Portal, where they will be able to register their site and obtain information such as the number of active devices receiving push notifications during the last month.

Site administrators should also check if they are using any of the “Customisable app features” (via Site administration > Mobile app > Mobile app features) as continued use will require upgrading to a plan.

=== ¿Necesito apuntarme al plan gratuito para poder usar la App? ===

No, though we encourage all site administrators to sign up in our Moodle Apps portal in order to obtain information about active devices receiving push notifications.

=== ¿Cómo puedo actualizar a uno de los planes? ===

During the last week of March 2020, site administrators will be provided with a link to the Moodle App Portal, where they will be able to sign up for a plan.

Remember that you can also migrate to a MoodleCloud plan, ask a Moodle Partner to host your site or build your own version of the app using the open source code.

=== ¿Cómo pago un plan? ===

For activation of any of the paid plans, you will need to make a credit card payment, PayPal will be also supported.

For payments via bank transfer to Moodle Pty Ltd, a minimum of a two years Premium subscription will be required (so we can cover all the administrative work and bank fees). Once you've chosen this method, the Premium plan will be automatically activated (only during March and April this year). Notice that you'll have 4 weeks for processing payment. If after those 4 weeks we haven't received the payment yet, the plan will be canceled and you will get back to the free plan and penalties can be applied in further payments.

=== Will students lose access to the app if we don’t upgrade straight away on 2 April 2020? ===

No, students will still be able to use the app. Depending on the size of your installation, your use of push notifications and the use of customised features, your students may stop receiving notifications or no longer be able to use specific features.

=== Si somos una ONG o una organización no lucrativa, ¿Necesitamos actualizar? ¡Necesitamos pagar? ===

We will create a process to ensure that NGOs and non-profit organisations do not need to pay and can benefit from our Premium Plan. Upon receipt of the necessary documentation and validation from Moodle HQ, organisations will have full access. Please note though that the verification process may take several weeks. Public universities, colleges and schools are not eligible for this.

=== Is this affecting only certain Moodle versions? ===
The changes will affect all the Moodle versions supported by the app (Moodle 3.1 onward)

=== ¿Qué pasa con los sitios que no están registrados con Moodle? ===

We recommend all site administrators to register their site in order to receive important notifications about the product. Moreover, the validation process to sign up for a plan will be easier.

=== Con los nuevos planes que vendrán, ¿hay algún acmbio que potencialmente afectará la privacidad de los usuarios? ===

No.

==Estudiantes==

===¿Cómo puedo obtener la Moodle app?===

The Moodle app is available for free from Google Play and the Apple Store. See [https://download.moodle.org/mobile/ Moodle app downloads] for links. You can also install the app directly from your mobile device by searching for 'Moodle app' with author/owner 'Moodle Pty Ltd'.

===I can't get the app to work. What do I do?===

The Moodle app will ONLY work with Moodle sites that have been set up to allow it. Please talk to your Moodle administrator if you have any problems connecting.

===What permissions does the app require?===

The app requires the following permissions:

* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.

=== ¿Porqué no puedo subir mi Tarea a la app?===
Consulte a su administrador de Moodle.

===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your Moodle site administrator.

===Is there a space limit on my files?===
Assignments will have a size limit which you can see. For other space limit questions, check with your Moodle site administrator.

===Who should I contact for help with the app?===
Your Moodle site administrator can assist you in getting the app to work correctly.

===When are activities completed offline synchronized?===

Vea [[Sincronización de Moodle app]].

===Why the site is asking for my username and password when an activity is opened in the browser?===

Auto-login from the app is only supported in sites using Moodle 3.2 onwards. Also, for security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).

===I use LineageOS and I'm having problems using the app===

LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.

===Los paquetes H5P y contenidos externos incrustados vía iframes no están funcionando en iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.

=== No recibo notificaciones del calendario (recordatorios) cuando uso Android 12 o superior ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Profesores==

===How can I enable videos in my course to be downloaded?===

See the section 'Media download for offline usage' in [[Crear cursos amistosos para mobile]].

===Video subtitles are not working===

This may happen in old Android versions (Android < 4.4), in modern Android and iOS versions they should work fine.

===Which course format is it best to use?===

Topics or weekly course format is best suited to mobile devices.

===How do I make YouTube links open automatically in the app?===

Add YouTube links as a [[Recurso URL]].

===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.

=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).

===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.

===My protected Vimeo videos are not playing in the app===

Vimeo protected videos should work on Moodle 3.3.4 onwards, please note that you need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">

For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

===ReCaptcha doesn't work on my site===

You need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

===H5P packages don't work on my site===

You need to enable this admin setting "Allow frame embedding" (allowframembedding admin setting). If that still doesn't work, make sure your server allows it by using this rule: X-Frame-Options "ALLOWALL"

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

=== I have problems playing SCORM packages ===

This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)

Please refer to [[Moodle app SCORM player]] for additional information.

=== My quizzes or lessons are not working offline ===

You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.

=== Maths notation is not displaying correctly in the app ===

The app doesn't yet support MathJax (see MOBILE-1611). Instead, the [[Filtro de notación TeX]] should be enabled.

=== How can I disable text selection / copy in the app? ===

You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes

=== My images, videos or audios stop working after the first time ===

Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administradores==

=== How can I debug errors in the app? ===

Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== I can connect with my iPhone but not with my Android phone ===

This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.geocerts.com/ssl_checker and https://www.ssllabs.com/ssltest/analyze.html

===I can't get the app to work. What can I do?===

Assuming you have enabled mobile services on your site, please check:

# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker] and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# [[Depuración]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, and /tokenpluginfile.php

If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

=== I cannot access with old users, but I can with recently created ones! ===

Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.

===I can't view the courses tab as an administrator===

The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.

===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===

See the section 'Mobile authentication' in the [[Moodle app guía para administradores]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===

SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:

* It launchs this URL https://yourmoodle/local/mobile/launch.php?service=local_mobile&passport=abc in the device browser (Moodle 3.2 onwards the URL is /tool/mobile instead local/mobile)
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/local/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol

Custom auth plugins may be failing in the last step,not redirecting back to local/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.

===I am having problems requesting an airnotifier access key===

If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===

Please check [[Mobile app notifications#Troubleshooting]]

==Error messages==

=== 'Can not find data record in database table external_functions' ===

This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.

==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 2.4 or later'===

Please check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)

==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===

Please check:
# You have followed all the steps listed in [[:dev:Moodle Mobile Developing a plugin tutorial|Moodle Mobile Developing a plugin tutorial]]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user

==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===

You need to create a token for the admin account (only) as follows:

# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.

==='Invalid response value detected' when accessing the site ===

The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].

=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===

This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)

==='Invalid response value detected' when accessing My Courses or Course Overview ===

This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".

==='A required parameter (username) was missing'===

This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.

==='Invalid json in request: No error'===

There is a bug in Moodle 3.3 that can cause this error. Please update to Moodle 3.3.2.

==='Cannot get course contents'===

This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.

==='Access control exception' or 'Your authentication token is invalid or has expired'===

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:

# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474

===I think I found a bug with the app. Where can I report it?===

# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button

===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

If the Moodle app is not yet available in your language, please contribute a translation! See [[:dev:Translating Moodle Mobile|Translating Moodle Mobile]] for details of what to do.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Categoría:FAQ]]

[[de:Moodle Mobile FAQ]]
[[ca:Moodle Mobile FAQ]]
[[en:Moodle Mobile FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:モバイルMoodle FAQ]]

MoodleMoot España 2015

2015-10-26T09:21:35Z

Jleyva: /* MoodleMobile 2 */

La MoodleMoot España 2015 se celebró entre los días 22 y 24 de octubre de 2015 en la Universitat de les Illes Balears de Palma de Mallorca.

Esta MoodleMoot és la primera en la que se celebra una Hackfest a nivel estatal español.

También és la primera MoodleMoot española en la que se redactan los apuntes de las sesiones colaborativamente mediante la herramienta [https://devpad.mood devpad]

'''Hashtag oficial''': [https://twitter.com/hashtag/mootes15 #mootes15]

==Notas de las ponencias==

===Sesión inaugural===

Jordi Vila "pica" a los representantes a sumarse al Moodle Association. Y se sienten picados.

===Moodle futures===
Mary Cooch (@moodlefairy) y Helen Foster (@moodlehelen)

Importante registrar el Moodle. ;-) https://docs.moodle.org/all/es/Registro_del_sitio

https://docs.moodle.org/dev/Mission

* Moodle no tiene previsto ni cambiar el modelo comercial ni cambiar la licencia GPL ni venderse a alguna gran compañía ni aceptar fondos de capital riesgo
* Moots seran publicadas en http://moodlemoot.org. Se grabaran para facilitar su "visita virtual"
* [https://www.youtube.com/user/moodlehq Canal de Moodle HQ en YouTube]
* [https://moodlecloud.com MoodleCloud]: versión gratis de Moodle. Incluye BigBlueButton
* Diseña el futuro de Moodle: https://moodleassociation.org/ (permite inscripción a newsletter)
* Moodle 3.0:
** La novedad principal es la incorporación de tipos nuevos de preguntas de cuestionario (las de la OU). (seleccionar palabras faltantes, drag&drop, arrastrar y soltar sobre imagen, arrastrar y soltar marcadores).
* Prioridades Moodle 3.1
** User Experience (UX)
** [https://tracker.moodle.org/browse/MDL-49458 Competency Based Education]
** Moodle Mobile
* [https://learn.moodle.net/ Learn Moodle MOOC], siguiente en enero de 2016
* Moodle 3.0 = Moodle 2.10 (no habrá problemas con la importación/exportación de cursos)

===MoodleMobile 2===
Juan Leyva - @moodlemobileapp - @jleyvadelgado (añado: el Gran Juan Leyva ;) )

[http://es.slideshare.net/juanleyva/moodle-mobile-2-moodlemoot-spain-2015 Presentación en Slideshare]

* La presentación es sobre la versión oficial de la App (no sobre el uso). En la presentación hay un par de enlaces sobre este otro tema.
* La APP está orientada para estudiantes y profesores (no para admins).
* Additional features plugin: recomendado para incorporar últimas novedades (cada 3-4 semanas hay versión nueva de Moodle Mobile y también de este plugin). Emula tener la última versión de Moodle desde el punto de vista de la app.
* Incorpora: todos los recursos y algunas actividades. Las tareas están parcialmente implementadas. (los cambios que se explican están sólo para Moodle 3.0 o para Moodle anteriores con additional features). La versión se publicó el pasado miércoles (en Android ya está disponible; para iOS aún no está porque hacen review).
** Todos los recursos se pueden dejar descargados para consultarlos offline.
*** Página y URL (la página se descarga y también está disponible offline)
*** Libro e IMS CP (navegables)
** Actividades:
*** Forums (las más recientes están en caché y se pueden consultar también offline). Desde la última versión ya es posible responder (no admite ni HTML ni ficheros adjuntos).
*** Tareas: se pueden descargar adjuntos para consultarlos offline
*** Consulta (permite participar i consultar )
*** Survey (diferentes pantallas para tablet que para teléfono)
*** LTI
** Compleción (tanto consulta como marcarlo)
** Calificaciones (diferentes pantallas para tablet que para teléfono)
** Participantes (mensaje instantaneo, añadir nota...)
** Gestionar los archivos del curso y del sitio. También subir archivos nuevos.
** Mensajería
** Calendario y eventos
** Notificaciones recibidas (por push)
*** Requiere registro de moodle y certificado para air notifier. Todo documentado.
** Se puede personalizar con un css en el moodle. La app lo carga.
** Open source GPL 2. Permite hacer versiones personalizadas (logotipo institución con funcionalidades añadidas/quitadas, sin necesidad de que escriban URL...)
* Futuro:
** Estarán en el core de Moodle 3.1 (pero si están antes, se publicarán antes): SCORM, Quiz, Glosario y wiki
*** Taller no está previsto a corto plazo porque no es de las más usadas
** Plataformas: versión de escritorio (para países/centros con problemas de conexión)
* Diferencia entre tema responsive y APP (hay una transparencia con las diferencias principales).
* Preguntas:
** Responder foros offline? De momento no es posible (no es fácil porque hay casos complejos: contestar mensaje borrado)... Lo tienen previsto a corto plazo.
** SCORM: su uso se ha pervertido. Inicialmente era para autoaprendizaje pero se está utilizando como contenedor.
* Se propone añadir posibilidad para poder borrar ficheros de forma selectiva.
* Moodle Mobile 1 no está previsto mantenerla (funciona para Android 2 y para Windows). No reciben errores.
* Previsión para feedback? Como está previsto que lo fusionen, de momento están esperando la versión definitiva.
* Tareas: a corto plazo tienen previsto que los alumnos puedan hacer entregas (la lógica e implementación es más compleja de lo que parece).

===OpenDrako===
Albert Calvet

La semana que viene publicarán la presentación en la web corporativa del proyecto: http://opendrako.org/ - http://cloud.opendrako.com

* Software open source diseñado para soportar la gestión académica
* OpenDrako es un Training Resource Planning (TRP), un ERP espacializado en formacion
* Si en Moodle el centro es el curso, en OpenDrako es el proceso
* Inicialmente el framework base era Moodle pero decidieron cambiar de idea (ahora se basa en Symphony)
* Durante la sesión se muestra un vídeo con la navegación. Ahora bien, en breve será posible acceder.
** Reordenar listas
** Exportación de listas
* La personalizacion está diseñada pensando en que la actualizacion de version no suponga un problema
* La comunicacion con Moodle es esencial:
** Desde OpenDrako se pueden crear cursos de Moodle, incorporando themes y usuarios matriculados
* De las tres capas, la versión actual sólo tiene la primera y una pequeña parte de la segunda.
* Empezaran con dos versiones: Enterprise (fecha de lanzamiento oficial 1 de noviembre) y Cloud (fecha de lanzamiento 15 de diciembre)
* La aplicacion no la liberaran hasta tener una version mas madura (no ha concretado fecha)
* Destaca en Open Drako la facilidad de uso para los clientes, porque al estar centrada en los procesos es fácilmente comprensible y adaptable
* Cuando se abra la web corporativa el 1 de noviembre habrá un espacio demo que se regenerará cada día.
* Preguntan sobre si está previsto que OpenDrako incopore información estadística necesaria en algunos casos para justificaciones (tripartita...).
** OpenDrako se puede integrar con otros LMS/CMS a través de servicios web.
* El idioma principal de Open Drako es el inglés porque es una herramienta pensada a nivel internacional y esa es su hoja de ruta, expandirse por diferentes países

===Student Experience and Improving===
Gavin Henrick (@ghenrick)

Gavin define algunos aspectos sobre la "organización del sitio" (Organization Systems) para mejorar la experiencia de usuario, relaciondos con
* el reconocimiento, sencillo log in, seguridad...
* el acceso
* la navegabilidad, encuentro lo que quiero cuando necesito
* consistencia, coherencia en estructuras al final jerárquicas, mantener aspectos, jugar con imágenes

* Universidad: social, colaboración entre estudiantes.
* Importa la apariencia.
* Accesibilidad a diferentes recursos: qué haremos en un aula, fuera de ella.
* All device friendly: hay que tenerlo en cuenta a la hora de diseñar cursos (evitar imágenes enormes, por ejemplo)
* Mobile App... Hay gente que tiene activados WS y notificacions push, ¿pero cuantos hacen difusión?
* La seguridad siempre presente.
* Importante implementar SIngle Sign ON (SSO) para reforzar experiencia coherente entre los distintos sistemas de la plataforma de aprendizaje.
* Navegación
** Consistente con el resto de plataformas del sistema
** Flexible y autodefinido, navegación intuitiva.
** Etiquetado facilita navegación.
** Navegación del usuario a través del sitio: flujo de información. Qué es importante o suplementario a simple vista.1
** En los nombres de las actividades, utilizar acciones, no el nombre del tipo de actividad.
* Imágenes de soporte que estén relacionadas con el texto
* Hay potencial en el consumo de las clases y sus materiales offline.
* Creación de apuntes colaborativos (como este devpad :-P )
* Comunicación. reparar en la comunicacion global que recibe el alumnado, notificando asuntos organizativos, dando un feedback apropiado y que permita conectarse con otros estudiantes. un feedback apropiado orientado al manejo de expectativas, acordar tiempos de respuesta, plazos, límites claros que son transparentes
* Otro aspecto importante que puede ayudar a mejorar la experiencia del usuario y del aprendizaje es el Reporting para el propio usuario: le puede orientar a saber dónde está respecto al resto de los usuarios, a qué nivel está respecto de sus compañeros, etc.
* Idea: en la lista de cursos mostrar el porcentaje de compleción (o calificación), para que no haga falta acceder al curso para consultar esta información.
* Competencias: dar feedback al estudiante de su nivel.

===Gestion de Moodle por años académicos===
Jordi Puyol-Ahullo (@jpahullo)

[http://2015.moodlemoot.net/course/view.php?id=35 Curso del SIG] - [http://2015.moodlemoot.net/mod/resource/view.php?id=180 Presentacion]

Para aligerar la creacion masiva de cursos no los crean a través de la API de Moodle sino directamente en la BBDD (replicando lo que hace la API)
Diferentes estrategias de cambio de año:
* Creacion masiva de cursos con restore on-demmand
* Creacion on-demmand con opcion de restore
* Creacion y restore masiva
Cuando ven los profesores y alumnos los cursos, distintas estrategias:
* El profesor decide cuando activar la sincronizacion (hasta entonces los alumnos no ven el curso)
* La matriculacion se hace "de saque" y desarrollo propio para que los alumnos vean en gris el curso aun cuando este oculto
* con UNIVERSITASXXI la mayoría usamos un desarrollo propio intermedio para la matriculacion, creación de cursos, etc
* Creacion de cursos con contenidos o vacios, Problemas con cambios de asignación de docencia.
Sincronizacion de datos de usuario y matriculaciones
* Problemas con la ventana nocturna para la actualizacion masiva
* Sincronizacion del perfil en el login
Una base de datos con todo o una por año académico?
* Con más de una como hacer el login (CAS, SSO,..)
* Con solo una problema de accesibilidad
Cuántos años académicos?
* Para acreditaciones a veces se piden 2, 3 y hasta 4 años (actual + 3 anteriores)

===DSpace como Repositorio de Objetos de Aprendizaje integrado===
David Paniagua (@panidvd) y Emilio Lorenzo

Toda la información y la presentación están colgadas en el [http://2015.moodlemoot.net/course/view.php?id=10 curso]
* Software libre, más de 2000 instalaciones en el mundo.
* Centrado como knowledge base científico y su difusión

* Se lleva bien con la indexiación de Google Scholar
* Se diferencia con S3 por la indexación
* Etiquetado Estándar de Objetos Digitales Educativos (ODE): http://educalab.es/recursos/lom-es
* Interfaces REST en DPace-Moodle
* CRUD (Create-Read-Update-Delete) - login, logout, search, items, bitstreams (depositar elementos de Moodle a DSpace).
* No se hablado de la instalacion/configuracion a Moodle

[[Category:MoodleMoot]]
[[Category:MoodleMoot2015]]

mod/assignment/type/rtcollaboration/text

2011-03-01T20:17:50Z

Jleyva: Redirigiendo a RTCollaboration

#REDIRECT [[RTCollaboration]]

blocks/configurable reports/

2010-10-13T19:35:06Z

Jleyva:

== Instalación ==

# Descargar el fichero de instalación del bloque "Configurable Report" y descomprimirlo en el directorio '''/blocks''' del directorio de instalación de Moodle.
# Iniciar sesión como administrador y pulsar en el enlace Notificaciones, dentro del bloque de administración del sitio.

Para más información véase [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Installing contributed modules or plugins] (en inglés)

== Resumen ==

Este bloque sirve para generar informes a medida de Moodle.

Ha sido diseñado de forma modular para permitir a los desarrolladores crear nuevos plugins en menos de una hora.

=== ¿Quién puede crear informes a medida? ===

Cualquier usuario que tenga los permisos '''block/custom_reports:managereports'', '''blocks/custom_reports:manageownreports''' o '''block/custom_report/managesqlreports''' asignados en un CURSO o en el SITIO (estos permisos se definen durante la instalación del bloque).

=== ¿Qué tipo de informes puedo crear? ===

* Informes de cursos, con informaciones relativas a los cursos.
* Informes de usarios, con informaciones relativas a los usuarios y su actividad en un curso.
* Informes SQL personalizados, consultas SQL personalizadas. Este bloque puede usar las mismas consultas SQL que el plugin [http://moodle.org/mod/data/view.php?d=13&rid=2884 de consultas SQL personalizadas de Tim Hunt].

Nota para los desarrolladores: se pueden crear sus propios tipos de informes.

=== ¿Quién puede ver los informes? ===

Cuando se crea un informe se puede elegir qué usuarios pueden verlo.

Los informes se muestra en un bloque del curso o en la portada del sitio.

== Cómo crear un informe ==

Este es un proceso muy sencillo. Si va a crear un informe para un curso, necesita añadir el bloque en el curso y pulsar sobre "Gestionar informes". Por su parte, para los informes del sitio, añada el bloque en la portada y pulse sobre el enlace "Gestionar informes".

Necesita introducir un nombre, una descripción (opcional) y tiene que elegir el tipo de informe, paginación y formatos de exportación.

Dependiendo del tipo de informe elegido habrá más o menos pestañas. Estas son las pestañas para los informes de cursos y usuarios:

* '''Columnas''': Aquí se puede elegir las diferentes columnas del informe, dependiendo del tipo de informe (Nombre del curso, Nombre de pila del usuarios, etc.)
* '''Condiciones''': Aquí se pueden definir las condiciones (p.ej., sólo cursos de esta categoría, sólo usuarios de España, etc.)
* '''Ordenación''': Aquí se puede elegir como ordenar el informe usando los campos y direcciones (ascendente, descendente).
* '''Filtros''': Aquí se puede elegir qué filtros se visualizarán.
* '''Plantilla''': Se puede modificar la disposición del informe creando una plantilla.
* '''Permisos''': Aquí se puede escoger quien puede ver el informe.
* '''Cálculos''': Aquí se pueden añadir cálculos para las columnas; p.ej., media del número de usuarios matriculados en los cursos.
* '''Gráficas''': Aquí se pueden añadir gráficas al informe basadas en las columnas del informe y los valores.
* '''Ver informes''': Auto explicativa

== Tutorial ==

=== Como crear un informe de usuario ===

Requisitos: ''Usuarios de España, pero no de Madrid, en este curso. Este informe se puede ver sólo por usuarios de España. Hay que visualizar un filtro basado en la ciudad del usuario. Se pide mostrar una gráfica de tarta con las ciudades de los usuarios. Se pide una tabla calculada que muestre el total de vistas de mensajes de foros El informe debe ordenarse por el apellido de los usuarios''.

¡Veamos qué fácil es!

# Primero de todo, instale el bloque.
# Vaya al curso donde se quiere crear el informe.
# Añada una instancia del bloque "Informes personalizados".
# Pulse en "Gestionar informes".
# Pulse en "Añadir informe".
# Introduzca un nombre, una descripción y elija "Informes de usuarios" como tipo de informe.
# Opcionalmente puede marcar las casillas "Exportar en formato ODS" y "Exportar en formato XLS" si desea poder exportar el informe en alguno de estos formatos.
# Pulse el botón "Agregar".
# Se guardará el informe y se le redirigirá a la pestaña denominada "Columnas".

==== Añadir columnas ====

Aquí se puede efinir las propiedades de la tabla del informe como anchura, alineación, relleno de las celdas, espaciados de las celdas, etc.

# Añada una columna de tipo "Campo del perfiel de usuario"
# Teclee un nombre para esta columna y en el desplegable llamado "Columna" elija el valor "firstname". Puede dejar en blanco el resto de elementos. Pulse sobre el botón "Agregar".
# Repita el proces para los campos "lastname" y "city".
# Añada una nueva columna de tipo "Acciones de usuario en el módulo".
# Teclee un nombre parae esta columna y elija un módulo de la lista, en nuestro caso, el foro sobre el que queremos elaborar el informe. Pulse sobre el botón "Agregar".

==== Añadir condiciones ====

# Pulse en la pestaña "Condiciones".
# Añada una condición del tipo "Condición sobre campo de perfil del usuario".
# Escoga la columna "country" de la lista desplegable, el operador "=" e introduzca el valor "ES" (este es el código internacional para España tal y como lo almancena Moodle internamente). Pulse el botón "Agregar".
# Añada una nueva condición del tipo "Condición sobre campo de perfil del usuario".
# Escoja la columna "city", el operador "<>" e introduzca el valor "Madrid". Pulse el botón "Agregar".
# Añada una condición del tipo "Usuarios en el curso donde se ha creado el informe" y escoja el valor "Student". Pulse el botón "Agregar".

Estas son las condiciones principales del informe. Note que en la parte inferior hay una caja de texto llamada "Condición lógica" con el texto:

c2 and c1 and c3

Aquí se puede definir una condición lógica cualquiera. En este caso no necesitamos editar esta condición, pero puede crear expresiones complejas como:

(c1 and c2) or (c4 and c3)

==== Añadir ordenación ====

# Pulse en la pestaña "Ordenación".
# Añada una ordenación del tipo "Ordenación por campo de usuario".
# Escoja la columna "lastname" y la ordenación "ASC" (ascendente). Pulse "Agregar".

==== Añadir filtros ====

# Pulse en la pestaña "Filtros".
# Añáda un filtro del tipo "Filtro sobre campo del perfil del usuario".
# Escoja el campo "city". Pulse "Agregar".

==== Añadir permisos ====

# Pulse en la pestaña "Permisos".
# Añada un permiso del tipo "Valor en el perfil del usuario".
# Escoja la columna "country" e introduzca el valor "ES". Pulse el botón "Agregar".

Aquí puede añadir más tipos de permisos y la condición lógica que debe cumplirse en caso de tener más un tipo de permiso.

==== Añadir cálculos ====

# Pulse en la pestaña "Cálculos".
# Añada un cálculo de tipo "Suma".
# Escoja la columna que representa la acción del usuario en el módulo (en nuestro caso el foro).

==== Añadir gráficas ====

# Pulse en la pestaña "Gráficas".
# Elija el tipo de gráfico "Tarta".
# Escoja la columna "city" tanto para la opción "Nombre" como para la opción "Valor". Pulse el botón "Agregar".

Por último, añada unos cuantos usuarios en Moodle con el país "España" y diferentes ciudades: Madrid, Barcelona, Sevilla, etc. y pruebe a visualizar el informe pulsando en la pestaña "Ver informe".

Si ha habilitado las opciones de exportar el informe en alguno de los formatos , podrá descargarlo pulsando sobre los enlaces que aparecen en la parte inferior del informe.

[[#Informe_de_usuarios | Ver pantalla mostrando el informe]]

=== Crear un informe SQL ===

Puede encontrar un montón de informes SQL aquí: [https://docs.moodle.org/en/ad-hoc_contributed_reports ad-hoc contributed reports]

Puesto que este bloque puede utilizar los informes de consultas SQL personalizadas de Tim Hunt, puede utilizar cualquier consulta.

Recuerde añadir un filtro de tipo "Filtro de fechas" si va a usar informes con valores temporales.

Para crear un informe de este tipo:

# Pulse en el enlace "Gestionar informes" del bloque de informes personalizados
# Pulse en "Añadir informe".
# Introduzca un nombre y una descripción para el informe y seleccione "Informe SQL" como el tipo del informe.
# Opcionalmente puede marcar las casillas "Exportar en formato ODS" y "Exportar en formato XLS" si desea poder exportar el informe en alguno de estos formatos.
# Pulse el botón "Agregar".
# Se guardará el informe y se le redirigirá a la pestaña denominada "Sentencia SQL".
# Añada esta consulta (''Actividad de los cursos''):
<code sql>
SELECT COUNT(l.id) AS hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
GROUP BY courseId
ORDER BY hits DESC
</code>
y pulse el botón "Guardar cambios".
# Vaya a la pestaña "Cálculos".
# Añada un cálculo de tipo "Suma" y escoja la columna "hits". Pulse el botón "Agregar".
# Vaya a la pestaña "Gráficas".
# Elija el tipo de gráfico "Tarta".
# Escoja la columna "hits" tanto para la opción "Nombre" como para la opción "Valor". Pulse el botón "Agregar".
# Pruebe a visualizar el informe pulsando en la pestaña "Ver informe".

Ahí lo tiene, un informe con una gráfica y cálculos basados en una consulta SQL.

Puede añadir un filtro de cursos, es muy sencillo:

# Vaya a la pestaña "Filtros" y añada un filtro de tipo "Cursos".
# Edite la consulta SQL y ponga lo siguiente:
<code sql>
SELECT COUNT(l.id) AS hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
%%FILTER_COURSES:l.course%%
GROUP BY courseId
ORDER BY hits DESC
</code>
Observe que estamos añadiendo un token llamado %%FILTER_COURSES:l.courseid%%
# Vaya a la pestaña "Ver informe" y verá un filtro de cursos. Elija un curso y pulse en "Añadir" para ver el informe filtrado por ese curso.

También puede añadir un filtro de tipo "Filtro de fechas" para filtrar por fecha de inicio y fin:

# Vaya a la pestaña "Filtros" y añada un filtro de tipo "Filtro de fechas".
# Edite la consulta SQL y ponga lo siguiente:
<code sql>
SELECT COUNT(l.id) AS hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
%%FILTER_COURSES:l.course%%
%%FILTER_STARTTIME:l.time:>%% %%FILTER_ENDTIME:l.time:<%%
GROUP BY courseId
ORDER BY hits DESC
</code>
Observe que estamos añadiendo un token llamado %%FILTER_STARTTIME:l.time:>%% %%FILTER_ENDTIME:l.time:<%%
# Vaya a la pestaña "Ver informe" y verá también un filtro para indicar la fecha de inicio y fin a usar para el informe.

[[#Informe_SQL | Ver pantalla mostrando el informe]]

== Opciones avanzadas ==
=== Plantillas ===

Se puede personalizar el informe usando una plantilla. Sólo hace falta ir a la pestaña llamada "Plantilla" y habilitarla, y a continuación rellenar cada una de las partes de la plantilla (cabecera, plantilla para un registro y pie)

Este es un ejemplo de código HTML para visualizar una lista de usuarios:

Cabecera:

<code html4strict>
<p align="center"><b>##reportname##</b></p>
<table width="60%" align="center">
<tr>
<td>
</code>

Plantilla para un registro:

<code html4strict>
<table width="100%">
<tr>
<td><img src="http://tu.sitio.moodle.es/user/pix.php/[[id]]/f1.jpg"></td>
<td><h2>[[firstname]] [[lastname]]</h2>
Ciudad: [[city]]
</td>
</tr>
</table>
<br>
</code>

Pie:

<code html4strict>
</td>
<td valign="top">
##graphs##
<br /><br />
##exportoptions##
</td>
</table>
</code>

=== Informes incrustados ===
Un informe incrustado consiste en un juego de columnas de un informe que están incrustadas entro.

Por ejemplo, puede incrustar un informe de usuario en un informe de curso. En este caso, las filas resultantes del curso se expandirán duplicando cada fila para cada usuario.

Para incrustar un informe, simplemente añada una nueva columna de tipo "Columna de otro informe". Aparecerá una lista de informes existentes. Una vez seleccionado uno aparecerá la lista de columnas de dicho informe para que podamos escoger la deseada.

Dentro de un informe de curso se puede incrustar un informe de usuario y viceversa. No es posible sin embargo incrustar informes de curso dentro de informes de curso, o informes de usuario dentro de informes de usuario.

== Documentación para desarrolladores ==

Es muy fácil crear nuevos tipos de informes, componentes y plugins.

'''Informe''': Un informe es un directorio ubicado dentro de /reports (con respecto al directorio de instalación del bloque). Este directorio contiene un fichero llamado report.class.php con la definición de la clase hija que extiende de report_base.

Sólo necesita modificar unos pocos métodos para añadir un nuevo tipo de informe. Por favor, eche una ojeada a cualquiera de los informes existentes. El informe SQL es un ejemplo de un informe no típico, mientras que los informes de usuarios y cursos son informes estándar.

La mejor manera de crear un nuevo informe es duplicando uno existente.

'''Componente''': Un componente es parte de un informe, y puede ser usado por más de un informe. Además es un directorio ubicado dentro de /components (con respecto al directorio de instalación del bloque). Este directorio contiene un fichero llamado component.class.php con la definición de la clase hija que extiende de component_base.

El componente princial es el componente llamado "columns", que se usa para añadir las columnas de un informe. Otros componentes son los filtros, permisos, gráficas, cálculos, etc.

La mejor manera de crear un nuevo componente es duplicando uno existente.

'''Plugin''': Un plugin es un módulo de un componente. Además es un directorio ubicado dentro de /components/nombre-del-componente/. Este directorio contiene un fichero llamado plugin.class.php con la definición de la clase hija que extiende de plugin_base.

Por ejemplo, el componente columna tiene unos pocos plugins (coursefield, userfield, etc..).

Un plugin funciona normalmente para un único tipo de informe, pero existen plugins que funcionan para más de un tipo de informe.

La mejor manera de crear un nuevo plugin es duplicando uno existente.

== Créditos ==
Juan Leyva [http://moodle.org/user/view.php?id=49568&course=1 Perfil de Moodle]

[http://twitter.com/jleyvadelgado Sígueme en Twitter]
[[Category:Contributed code]]

== Pantallazos ==
=== Informe de usuarios ===
[[Image:block_custom_reports_sample_user_report.png|600px]]

=== Informe SQL ===
[[Image:block_custom_reports_sample_sql_report.png|600px]]

[[en:blocks/configurable_reports/]]

blocks/configurable reports/

2010-10-13T19:34:36Z

Jleyva:

== Instalación ==

# Descargar el fichero de instalación del bloque "Custom Report" y descomprimirlo en el directorio '''/blocks''' del directorio de instalación de Moodle.
# Iniciar sesión como administrador y pulsar en el enlace Notificaciones, dentro del bloque de administración del sitio.

Para más información véase [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Installing contributed modules or plugins] (en inglés)

== Resumen ==

Este bloque sirve para generar informes a medida de Moodle.

Ha sido diseñado de forma modular para permitir a los desarrolladores crear nuevos plugins en menos de una hora.

=== ¿Quién puede crear informes a medida? ===

Cualquier usuario que tenga los permisos '''block/custom_reports:managereports'', '''blocks/custom_reports:manageownreports''' o '''block/custom_report/managesqlreports''' asignados en un CURSO o en el SITIO (estos permisos se definen durante la instalación del bloque).

=== ¿Qué tipo de informes puedo crear? ===

* Informes de cursos, con informaciones relativas a los cursos.
* Informes de usarios, con informaciones relativas a los usuarios y su actividad en un curso.
* Informes SQL personalizados, consultas SQL personalizadas. Este bloque puede usar las mismas consultas SQL que el plugin [http://moodle.org/mod/data/view.php?d=13&rid=2884 de consultas SQL personalizadas de Tim Hunt].

Nota para los desarrolladores: se pueden crear sus propios tipos de informes.

=== ¿Quién puede ver los informes? ===

Cuando se crea un informe se puede elegir qué usuarios pueden verlo.

Los informes se muestra en un bloque del curso o en la portada del sitio.

== Cómo crear un informe ==

Este es un proceso muy sencillo. Si va a crear un informe para un curso, necesita añadir el bloque en el curso y pulsar sobre "Gestionar informes". Por su parte, para los informes del sitio, añada el bloque en la portada y pulse sobre el enlace "Gestionar informes".

Necesita introducir un nombre, una descripción (opcional) y tiene que elegir el tipo de informe, paginación y formatos de exportación.

Dependiendo del tipo de informe elegido habrá más o menos pestañas. Estas son las pestañas para los informes de cursos y usuarios:

* '''Columnas''': Aquí se puede elegir las diferentes columnas del informe, dependiendo del tipo de informe (Nombre del curso, Nombre de pila del usuarios, etc.)
* '''Condiciones''': Aquí se pueden definir las condiciones (p.ej., sólo cursos de esta categoría, sólo usuarios de España, etc.)
* '''Ordenación''': Aquí se puede elegir como ordenar el informe usando los campos y direcciones (ascendente, descendente).
* '''Filtros''': Aquí se puede elegir qué filtros se visualizarán.
* '''Plantilla''': Se puede modificar la disposición del informe creando una plantilla.
* '''Permisos''': Aquí se puede escoger quien puede ver el informe.
* '''Cálculos''': Aquí se pueden añadir cálculos para las columnas; p.ej., media del número de usuarios matriculados en los cursos.
* '''Gráficas''': Aquí se pueden añadir gráficas al informe basadas en las columnas del informe y los valores.
* '''Ver informes''': Auto explicativa

== Tutorial ==

=== Como crear un informe de usuario ===

Requisitos: ''Usuarios de España, pero no de Madrid, en este curso. Este informe se puede ver sólo por usuarios de España. Hay que visualizar un filtro basado en la ciudad del usuario. Se pide mostrar una gráfica de tarta con las ciudades de los usuarios. Se pide una tabla calculada que muestre el total de vistas de mensajes de foros El informe debe ordenarse por el apellido de los usuarios''.

¡Veamos qué fácil es!

# Primero de todo, instale el bloque.
# Vaya al curso donde se quiere crear el informe.
# Añada una instancia del bloque "Informes personalizados".
# Pulse en "Gestionar informes".
# Pulse en "Añadir informe".
# Introduzca un nombre, una descripción y elija "Informes de usuarios" como tipo de informe.
# Opcionalmente puede marcar las casillas "Exportar en formato ODS" y "Exportar en formato XLS" si desea poder exportar el informe en alguno de estos formatos.
# Pulse el botón "Agregar".
# Se guardará el informe y se le redirigirá a la pestaña denominada "Columnas".

==== Añadir columnas ====

Aquí se puede efinir las propiedades de la tabla del informe como anchura, alineación, relleno de las celdas, espaciados de las celdas, etc.

# Añada una columna de tipo "Campo del perfiel de usuario"
# Teclee un nombre para esta columna y en el desplegable llamado "Columna" elija el valor "firstname". Puede dejar en blanco el resto de elementos. Pulse sobre el botón "Agregar".
# Repita el proces para los campos "lastname" y "city".
# Añada una nueva columna de tipo "Acciones de usuario en el módulo".
# Teclee un nombre parae esta columna y elija un módulo de la lista, en nuestro caso, el foro sobre el que queremos elaborar el informe. Pulse sobre el botón "Agregar".

==== Añadir condiciones ====

# Pulse en la pestaña "Condiciones".
# Añada una condición del tipo "Condición sobre campo de perfil del usuario".
# Escoga la columna "country" de la lista desplegable, el operador "=" e introduzca el valor "ES" (este es el código internacional para España tal y como lo almancena Moodle internamente). Pulse el botón "Agregar".
# Añada una nueva condición del tipo "Condición sobre campo de perfil del usuario".
# Escoja la columna "city", el operador "<>" e introduzca el valor "Madrid". Pulse el botón "Agregar".
# Añada una condición del tipo "Usuarios en el curso donde se ha creado el informe" y escoja el valor "Student". Pulse el botón "Agregar".

Estas son las condiciones principales del informe. Note que en la parte inferior hay una caja de texto llamada "Condición lógica" con el texto:

c2 and c1 and c3

Aquí se puede definir una condición lógica cualquiera. En este caso no necesitamos editar esta condición, pero puede crear expresiones complejas como:

(c1 and c2) or (c4 and c3)

==== Añadir ordenación ====

# Pulse en la pestaña "Ordenación".
# Añada una ordenación del tipo "Ordenación por campo de usuario".
# Escoja la columna "lastname" y la ordenación "ASC" (ascendente). Pulse "Agregar".

==== Añadir filtros ====

# Pulse en la pestaña "Filtros".
# Añáda un filtro del tipo "Filtro sobre campo del perfil del usuario".
# Escoja el campo "city". Pulse "Agregar".

==== Añadir permisos ====

# Pulse en la pestaña "Permisos".
# Añada un permiso del tipo "Valor en el perfil del usuario".
# Escoja la columna "country" e introduzca el valor "ES". Pulse el botón "Agregar".

Aquí puede añadir más tipos de permisos y la condición lógica que debe cumplirse en caso de tener más un tipo de permiso.

==== Añadir cálculos ====

# Pulse en la pestaña "Cálculos".
# Añada un cálculo de tipo "Suma".
# Escoja la columna que representa la acción del usuario en el módulo (en nuestro caso el foro).

==== Añadir gráficas ====

# Pulse en la pestaña "Gráficas".
# Elija el tipo de gráfico "Tarta".
# Escoja la columna "city" tanto para la opción "Nombre" como para la opción "Valor". Pulse el botón "Agregar".

Por último, añada unos cuantos usuarios en Moodle con el país "España" y diferentes ciudades: Madrid, Barcelona, Sevilla, etc. y pruebe a visualizar el informe pulsando en la pestaña "Ver informe".

Si ha habilitado las opciones de exportar el informe en alguno de los formatos , podrá descargarlo pulsando sobre los enlaces que aparecen en la parte inferior del informe.

[[#Informe_de_usuarios | Ver pantalla mostrando el informe]]

=== Crear un informe SQL ===

Puede encontrar un montón de informes SQL aquí: [https://docs.moodle.org/en/ad-hoc_contributed_reports ad-hoc contributed reports]

Puesto que este bloque puede utilizar los informes de consultas SQL personalizadas de Tim Hunt, puede utilizar cualquier consulta.

Recuerde añadir un filtro de tipo "Filtro de fechas" si va a usar informes con valores temporales.

Para crear un informe de este tipo:

# Pulse en el enlace "Gestionar informes" del bloque de informes personalizados
# Pulse en "Añadir informe".
# Introduzca un nombre y una descripción para el informe y seleccione "Informe SQL" como el tipo del informe.
# Opcionalmente puede marcar las casillas "Exportar en formato ODS" y "Exportar en formato XLS" si desea poder exportar el informe en alguno de estos formatos.
# Pulse el botón "Agregar".
# Se guardará el informe y se le redirigirá a la pestaña denominada "Sentencia SQL".
# Añada esta consulta (''Actividad de los cursos''):
<code sql>
SELECT COUNT(l.id) AS hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
GROUP BY courseId
ORDER BY hits DESC
</code>
y pulse el botón "Guardar cambios".
# Vaya a la pestaña "Cálculos".
# Añada un cálculo de tipo "Suma" y escoja la columna "hits". Pulse el botón "Agregar".
# Vaya a la pestaña "Gráficas".
# Elija el tipo de gráfico "Tarta".
# Escoja la columna "hits" tanto para la opción "Nombre" como para la opción "Valor". Pulse el botón "Agregar".
# Pruebe a visualizar el informe pulsando en la pestaña "Ver informe".

Ahí lo tiene, un informe con una gráfica y cálculos basados en una consulta SQL.

Puede añadir un filtro de cursos, es muy sencillo:

# Vaya a la pestaña "Filtros" y añada un filtro de tipo "Cursos".
# Edite la consulta SQL y ponga lo siguiente:
<code sql>
SELECT COUNT(l.id) AS hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
%%FILTER_COURSES:l.course%%
GROUP BY courseId
ORDER BY hits DESC
</code>
Observe que estamos añadiendo un token llamado %%FILTER_COURSES:l.courseid%%
# Vaya a la pestaña "Ver informe" y verá un filtro de cursos. Elija un curso y pulse en "Añadir" para ver el informe filtrado por ese curso.

También puede añadir un filtro de tipo "Filtro de fechas" para filtrar por fecha de inicio y fin:

# Vaya a la pestaña "Filtros" y añada un filtro de tipo "Filtro de fechas".
# Edite la consulta SQL y ponga lo siguiente:
<code sql>
SELECT COUNT(l.id) AS hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
%%FILTER_COURSES:l.course%%
%%FILTER_STARTTIME:l.time:>%% %%FILTER_ENDTIME:l.time:<%%
GROUP BY courseId
ORDER BY hits DESC
</code>
Observe que estamos añadiendo un token llamado %%FILTER_STARTTIME:l.time:>%% %%FILTER_ENDTIME:l.time:<%%
# Vaya a la pestaña "Ver informe" y verá también un filtro para indicar la fecha de inicio y fin a usar para el informe.

[[#Informe_SQL | Ver pantalla mostrando el informe]]

== Opciones avanzadas ==
=== Plantillas ===

Se puede personalizar el informe usando una plantilla. Sólo hace falta ir a la pestaña llamada "Plantilla" y habilitarla, y a continuación rellenar cada una de las partes de la plantilla (cabecera, plantilla para un registro y pie)

Este es un ejemplo de código HTML para visualizar una lista de usuarios:

Cabecera:

<code html4strict>
<p align="center"><b>##reportname##</b></p>
<table width="60%" align="center">
<tr>
<td>
</code>

Plantilla para un registro:

<code html4strict>
<table width="100%">
<tr>
<td><img src="http://tu.sitio.moodle.es/user/pix.php/[[id]]/f1.jpg"></td>
<td><h2>[[firstname]] [[lastname]]</h2>
Ciudad: [[city]]
</td>
</tr>
</table>
<br>
</code>

Pie:

<code html4strict>
</td>
<td valign="top">
##graphs##
<br /><br />
##exportoptions##
</td>
</table>
</code>

=== Informes incrustados ===
Un informe incrustado consiste en un juego de columnas de un informe que están incrustadas entro.

Por ejemplo, puede incrustar un informe de usuario en un informe de curso. En este caso, las filas resultantes del curso se expandirán duplicando cada fila para cada usuario.

Para incrustar un informe, simplemente añada una nueva columna de tipo "Columna de otro informe". Aparecerá una lista de informes existentes. Una vez seleccionado uno aparecerá la lista de columnas de dicho informe para que podamos escoger la deseada.

Dentro de un informe de curso se puede incrustar un informe de usuario y viceversa. No es posible sin embargo incrustar informes de curso dentro de informes de curso, o informes de usuario dentro de informes de usuario.

== Documentación para desarrolladores ==

Es muy fácil crear nuevos tipos de informes, componentes y plugins.

'''Informe''': Un informe es un directorio ubicado dentro de /reports (con respecto al directorio de instalación del bloque). Este directorio contiene un fichero llamado report.class.php con la definición de la clase hija que extiende de report_base.

Sólo necesita modificar unos pocos métodos para añadir un nuevo tipo de informe. Por favor, eche una ojeada a cualquiera de los informes existentes. El informe SQL es un ejemplo de un informe no típico, mientras que los informes de usuarios y cursos son informes estándar.

La mejor manera de crear un nuevo informe es duplicando uno existente.

'''Componente''': Un componente es parte de un informe, y puede ser usado por más de un informe. Además es un directorio ubicado dentro de /components (con respecto al directorio de instalación del bloque). Este directorio contiene un fichero llamado component.class.php con la definición de la clase hija que extiende de component_base.

El componente princial es el componente llamado "columns", que se usa para añadir las columnas de un informe. Otros componentes son los filtros, permisos, gráficas, cálculos, etc.

La mejor manera de crear un nuevo componente es duplicando uno existente.

'''Plugin''': Un plugin es un módulo de un componente. Además es un directorio ubicado dentro de /components/nombre-del-componente/. Este directorio contiene un fichero llamado plugin.class.php con la definición de la clase hija que extiende de plugin_base.

Por ejemplo, el componente columna tiene unos pocos plugins (coursefield, userfield, etc..).

Un plugin funciona normalmente para un único tipo de informe, pero existen plugins que funcionan para más de un tipo de informe.

La mejor manera de crear un nuevo plugin es duplicando uno existente.

== Créditos ==
Juan Leyva [http://moodle.org/user/view.php?id=49568&course=1 Perfil de Moodle]

[http://twitter.com/jleyvadelgado Sígueme en Twitter]
[[Category:Contributed code]]

== Pantallazos ==
=== Informe de usuarios ===
[[Image:block_custom_reports_sample_user_report.png|600px]]

=== Informe SQL ===
[[Image:block_custom_reports_sample_sql_report.png|600px]]

[[en:blocks/configurable_reports/]]

blocks/configurable reports/

2010-10-13T19:34:01Z

Jleyva: Página creada con '== Instalación == # Descargar el fichero de instalación del bloque "Custom Report" y descomprimirlo en el directorio '''/blocks''' del directorio de instalación de Moodle. #...'