David Scotson

Hi Rafael,

you could try

filter: brightness(1.5)

to make the gray icons whiter via CSS.

You might need to add -webkit-filter for support on some browser, and it won't work on IE11, but might be handy in some situations.

It's worth reporting these in the bug tracker when you spot them. I've reported a few and they've been fixed promptly. Boost is generally moving towards using less Moodle-specific CSS by using the standard Bootstrap HTML and CSS but when getting rid of the overcomplicated workarounds there may be places that don't yet have the right code in place.

I searched and couldn't find any existing bugs on this particular instance so filed one and attached your screenshot to MDL-57415,

So a final issue I've hit and can't figure out:

Error: [$sce:insecurl] Blocked loading resource from url not allowed by $sceDelegate policy.  URL: filesystem:http://localhost:8100/persistent/sites/05af9b4d326c0f5d15bcfd9a026aee74/filepool/remoteaddons/mod_hsuforum_mod_hsuforum/templates/discussionpost.html

The template url for a delegate is triggering a security exception when used as part of a remote addon, but the exact same code when used as a core addon works fine. I would have thought that something coming from within the app wouldn't trigger such a security issue, but then I guess when it's a remote addon then it's not technically part of the app since it's getting downloaded.

The docs only say that the same port, domain and protocol are required, which I think is the case here. But it also talks about whitelists and blacklists so perhaps this is hitting a blacklist?

I'm not really familiar enough with Ionic etc. to know how I should proceed here. Do you know if this is supported in remote addons, and what I would need to do to make this work if it is? 

Hi Juan, thanks for the help, after eliminating that possibility I think I got to the bottom of what was going wrong.

It seems like the  gulp remoteaddon bundling step might grab .js test files and concatenate them with the rest of the js in addon.js, it was then complaining about the 'describe' function used in the test file on load.

Not sure if that's a bug in the gulp step or I'm just doing something wrong, but for now deleting the file gets me to the point where the remote addon loads and works 99% and I can debug the rest.

edit: oh and when one addon errors, it stops installation of all of them it seems, so I needed to test the two remote addons seperately. When I did that the mod certificate one worked fine.

You might want to try upgrading to 3.0.6, the latest minor update to 3.0 first as it's a much smaller jump and gets you all the security fixes for version 3:

https://docs.moodle.org/dev/Moodle_3.0.6_release_notes

A full version jump might be worthwhile (depending on your aims) but I'd upgrade to 3.0.6 first and then think about if it's worth it to upgrade further.