You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When teachers/admins create outging pulse messages with images, they are running into problems. If the image tag is using an SRC with a URL that is outside of the Moodle, it works fine. BUT, if the image is "uploaded" to the course, or if they try to use something ilke the course image, for example, it won't load the image. I believe this is because the pluginfile.php script won't serve up an image file if the user is not logged in. An example URL that doesn't work is
Digging into this a little more... perhaps the method to fix this is calling on webservice/pluginfile.php instead of the other edition of pluginfile.php. This will also require providing a token parameter in the URL and having the webservice enabled.
Thoughts?
-Tay
Thanks for reporting this issue. Yes, images (files in general) are currently not supported in notifications and would require additional development.
For the next version of Pulse, we're going to consider it as a potential improvement. No other customer so far has requested the feature (if any other customer is reading this, let us know in the comments if it is important for you)
Feel free to create a pull request if you want and we'll review it of course.
When teachers/admins create outging pulse messages with images, they are running into problems. If the image tag is using an SRC with a URL that is outside of the Moodle, it works fine. BUT, if the image is "uploaded" to the course, or if they try to use something ilke the course image, for example, it won't load the image. I believe this is because the pluginfile.php script won't serve up an image file if the user is not logged in. An example URL that doesn't work is
https://churchx.ca/pluginfile.php/46340/mod_pulse/pulse_content/0/UILX2010%20ChurchX_ModSquad%20Course.png
Is this a known issue? Is there a workaround?
-Tay Moss
https://churchx.ca
The text was updated successfully, but these errors were encountered: