Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

dreamweaver 2017 & Saba LMS

Community Beginner ,
Nov 21, 2016 Nov 21, 2016

I have been using Dreamweaver to create courses for upload to Saba LMS.  After updating DW to 2017, I quickly discovered that all I had to do was open a site that was created in 2015 DW & it no longer worked correctly with Saba.  What is going on & how can I fix this?  I have no idea what Dreamweaver is changing & where to created this issue.  I tried many previously built courses as tests & once viewed in 2017 DW they were forever corrupted.

Any ideas?

684
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Nov 21, 2016 Nov 21, 2016

DW shouldn't affect anything unless you're opening and saving the files.

Even the known javascript html entity rewrite bug, the change isn't permanent unless the file is saved after reopening.

Dreamweaver Help | Known issues | Dreamweaver CC 2017

Perhaps a little more info about your workflow, the steps you're taking and what's actually happening (and where it's happening) may help someone work out a solution for you.

Personally, because of that rewrite bug, I have moved back to 2015: How to Find and Install Previous Version of Adobe Apps in CC 2015 | Adobe Customer Care Team

...
Translate
Community Expert ,
Nov 21, 2016 Nov 21, 2016

I'm sure we have no idea either.  You keep redundant backups of all your files, right?  My site folders are backed up nightly so if a corruption occurs (power surge/outage, computer shutting down prematurely, etc..), I can always get clean versions to revert back to.

Once your code is restored, the first thing you might want to check for is errors.

Code Validation Tools

------------------------------------

CSS - http://jigsaw.w3.org/css-validator/

HTML - http://validator.w3.org/

HTML5 - https://validator.w3.org/nu/

JavaScript - http://www.jslint.com/

PHP -  http://phpcodechecker.com/

Nancy O.

Nancy O'Shea— Product User, Community Expert & Moderator
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 21, 2016 Nov 21, 2016

DW shouldn't affect anything unless you're opening and saving the files.

Even the known javascript html entity rewrite bug, the change isn't permanent unless the file is saved after reopening.

Dreamweaver Help | Known issues | Dreamweaver CC 2017

Perhaps a little more info about your workflow, the steps you're taking and what's actually happening (and where it's happening) may help someone work out a solution for you.

Personally, because of that rewrite bug, I have moved back to 2015: How to Find and Install Previous Version of Adobe Apps in CC 2015 | Adobe Customer Care Team

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 09, 2016 Dec 09, 2016

I have many "courses" so it is NOT a corrupt file in my sources.  I have done tests & it is corrupted somehow when I open the "site" in DW.  I can see the result just by locally previewing the index.html.  Once opened in DW - it does not work correctly - even without saving.

I noticed that the LMS (SABA) . will show an error that includes "Dreamweaver" on occasion.  I know this sounds strange, but I have tested & compared many, many times.

I had to revert to DW2015

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 09, 2016 Dec 09, 2016
LATEST

Jon -

Thank you.  I'm sure the "known bug":

  • HTML entities in JavaScript and JSON files are overwritten with symbols on file reopen.

is the problem.  I'll stick with 2015 for now.

THANX!!!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines