Hi all,
I'm trying to develop of a remote addon using the new functionality in 3.1.
I've found one existing plugin that supports this, mod_certificate, though both it and my plugin seem to be hitting a similar issue, where the app downloads the addon (I can see a GET request for /mod/certificate/mobile/mod_certificate.zip) but nothing seems different in the app, and it still requires me to visit the website for certificates. I tried with both Android and iOS.
Could someone explain how you would debug this? Is there somewhere I can look within the app to see what errors may have been produced when it installed the addon etc.
David Scotson
由David Scotson發起的議題
I'm fairly sure Moodle user images used to be JPEGs, but now they seem to be PNGs. Does anyone know when and why this change happened?
Here on Moodle.org you can use the 3rd party service Gravatar which provides the user images as JPEGs. As a result some user's images from that service are 10x smaller than others provided by Moodle itself. (It also resizes the image as required, so when displayed at 60x60 it will provide a 60x60 image, not a larger one and then resize it in the browser).
Modern web design trends often emphasis the use of large user images to inspire users to interact with each other. Moodle seems to be anticipating this by introducing a new user icon size of f3 at 512x512px, but since these are PNGs, they are about 500K in size, which I think makes them basically unusable.
I think some users that have been around for a while and not changed their avatar still have JPEGs, in case that confuses anyone looking into this.
But has anyone else investigated this before? I'm thinking a shift back to JPEG would make a lot of sense, and allow us to use visually larger yet faster to download images but wanted to do some more research first to find out why the opposite switch was made in the past.
Here on Moodle.org you can use the 3rd party service Gravatar which provides the user images as JPEGs. As a result some user's images from that service are 10x smaller than others provided by Moodle itself. (It also resizes the image as required, so when displayed at 60x60 it will provide a 60x60 image, not a larger one and then resize it in the browser).
Modern web design trends often emphasis the use of large user images to inspire users to interact with each other. Moodle seems to be anticipating this by introducing a new user icon size of f3 at 512x512px, but since these are PNGs, they are about 500K in size, which I think makes them basically unusable.
I think some users that have been around for a while and not changed their avatar still have JPEGs, in case that confuses anyone looking into this.
But has anyone else investigated this before? I'm thinking a shift back to JPEG would make a lot of sense, and allow us to use visually larger yet faster to download images but wanted to do some more research first to find out why the opposite switch was made in the past.
When you create a theme setting you tell Moodle what the default value for that setting is.
However, I've noticed that a lot of code that fetches these settings first checks if the setting is actually there, and if not, it applies a default value (which may or may not be the same as the one you give when setting it up). However, when I look at my settings they're a) all there, and b) the ones I haven't set have the default value. Some other code uses !empty to check for a value, which kind of implies the value may not exist.
Is there some circumstance (maybe just after creation on update?) when you might try to access a theme setting and it won't exist at all, and these fallbacks are necessary? Or is it just extra caution or a historical thing?
However, I've noticed that a lot of code that fetches these settings first checks if the setting is actually there, and if not, it applies a default value (which may or may not be the same as the one you give when setting it up). However, when I look at my settings they're a) all there, and b) the ones I haven't set have the default value. Some other code uses !empty to check for a value, which kind of implies the value may not exist.
Is there some circumstance (maybe just after creation on update?) when you might try to access a theme setting and it won't exist at all, and these fallbacks are necessary? Or is it just extra caution or a historical thing?
Just thought I'd point to work going on to integrate LESS into Moodle so that it can be (re-) compiled on the fly.
https://tracker.moodle.org/browse/MDL-44357
It's got some interesting potential for themes.
I have to say though that I'm a bit ambivalent about this. I had hoped that LESS would become an option, rather than a requirement to style Moodle, and that constraining Moodle to work with upstream's vanilla Bootstrap CSS would help to tame some of the, err, exuberance and diversity, of Moodle's current front-end CSS/HTML/PHP.
Hopefully the work that would simplify and standardize the font-end will continue, even as the workaround becomes easier, and people writing CSS for modules and plugins use this new power responsibly rather than adding yet more complexity.
https://tracker.moodle.org/browse/MDL-44357
It's got some interesting potential for themes.
I have to say though that I'm a bit ambivalent about this. I had hoped that LESS would become an option, rather than a requirement to style Moodle, and that constraining Moodle to work with upstream's vanilla Bootstrap CSS would help to tame some of the, err, exuberance and diversity, of Moodle's current front-end CSS/HTML/PHP.
Hopefully the work that would simplify and standardize the font-end will continue, even as the workaround becomes easier, and people writing CSS for modules and plugins use this new power responsibly rather than adding yet more complexity.
Hi all,
I seem to recall that recently some work being done broke upgrade and install, and as a result now renderers get overidden in some special way during updates.
Does anyone know about this, or can point me to somewhere documenting this? I've tried Googling but I'm not finding anything relevant. Currently I seem to get upgrade screens that are half my theme, and half... something else.
I seem to recall that recently some work being done broke upgrade and install, and as a result now renderers get overidden in some special way during updates.
Does anyone know about this, or can point me to somewhere documenting this? I've tried Googling but I'm not finding anything relevant. Currently I seem to get upgrade screens that are half my theme, and half... something else.