allow ppsx file?
Amy Wolfe writes:
I’m an OER Developer for Brooklyn College.
I’m using the Academic Commons to create an OER (open educational resource) for a faculty member at Brooklyn College for his Fall 2020 remote courses he is teaching.
He has created a PowerPoint slideshow with narration as his “Welcome Lecture”
We are wanting to upload the slideshow, which is in the file format “ppsx”.
When I try to upload this slideshow I get the following error message:
“SOCY2201-EnvSoc-PP-CourseIntro-compress-show.ppsx” has failed to upload. Sorry, this file type is not permitted for security reasons.”
The file is saved as a slideshow “ppsx” instead of as a presentation “pptx”, this is so the introduction slideshow with audio will start automatically for students, not requiring students to open and start the slideshow. This is something we want because the audio is not accessible unless the slideshow is playing. We don’t want students to think they only need to read the slides and not actually run the slideshow because they will then miss the professors entire lecture.
The file is compressed and under the file limit size.
Can you assist in fixing this error or is this some policy for CUNY?
Updated by Marilyn Weber over 3 years ago
Still no luck -
I tried today to upload a ppsx file (the professor’s week 2 file) and unfortunately I got the same error message.
“SOCY2201-Week2Video.ppsx” has failed to upload.
Sorry, this file type is not permitted for security reasons.”
I compressed the file and it is under the size limit.
Updated by Raymond Hoh over 3 years ago
- Category name set to WordPress - Media
- Status changed from Reporter Feedback to Staged for Production Release
- Target version changed from Not tracked to 1.17.3
We needed to register the .ppsx mime type with WordPress in order for the upload to work.
I've committed the fix here - https://github.com/cuny-academic-commons/cac/commit/7a112345ac4d955e8629cd5b78d1456532236d67.
Boone, I'm having trouble authenticating with SSH to the Commons today, so I cannot deploy this as a hotfix. If you want to deploy to production, can you cherry-pick the commit?