Publisher v2.8 (November 2014)

Known Issues

When using the Safari browser (for Mac operating systems), the zip file is automatically unzipped after the course snapshot is downloaded, which prevents you from being able to browse to the zip file location to restore the course.
Workaround: To prevent zip files from being automatically unzipped, go to the General options page for the browser, and deselect the Open "safe" files after downloading check box.
When using Chrome with the malware and phishing detection browser setting enabled, the message "<File.zip> is not commonly downloaded and could be dangerous" displays when you download a course snapshot. You can ignore this message and continue with the course download. (CR 168309)
Custom course updates made via Publisher against Skillport 8 may not display in Skillport for up to 30 minutes. This is expected synchronization behavior in Skillport.
When a course restore fails, the status is incorrectly displayed as "New Course" in the Publish Operation field on the Course Details page. The status of the course should be "Restore". (CR 170715)
After a restore function has been completed for a course, the retired.html file is still cached in Skillport and continues to be launched even when the course status has been re-activated. You may potentially see this retired.html file in course launches up to 24 hours after a restore has been successfully completed.

The Players Upgrade page in Skillport Publisher Administration no longer incorrectly displays KC-only sites. (CR 160064)
PDF files containing an apostrophe in the file name that are uploaded as passive content are now launching correctly. (CR 164164)
When editing the course metadata by selecting the tablet option, the B-page variable (isMobileCCA or isTabletCCA) is now correctly updated. (CR 164807)
An issue where uploaded courses were not launching due to missing values for the new B-page template variables has been resolved. (CR 165443)
SkillStudio courses are no longer being installed in the incorrect location on the content server and failing to publish. (CR 165828)
The abbreviation for megabytes now displays correctly as MB in the Detailed Report. (CR 167193)