Details

    • 11 status:
      Merge
    • Test Plan:
      Hide

      To test this you need to set
      samigo.publish.update.siteids=false

      It seems semi complex to test, but I think this is what you'd do.

      • You'd need to create a "repository site" with a public resources folder and public images.
      • Create question pool questions using images from this repository site
      • Go to another site, create an assessment pulling from this question pool.
      • Publish the assessment

      Expected - The urls are NOT updated. With this property set to true urls (including these) are updated.

      Show
      To test this you need to set samigo.publish.update.siteids=false It seems semi complex to test, but I think this is what you'd do. You'd need to create a "repository site" with a public resources folder and public images. Create question pool questions using images from this repository site Go to another site, create an assessment pulling from this question pool. Publish the assessment Expected - The urls are NOT updated. With this property set to true urls (including these) are updated.

      Description

      SAM-1596 added some new code to Samigo that replaces the site ids in an assessment when it's published. For some cases where resources are imported correctly to the destination this could be a good idea. But the problem with this is it doesn't do any checking if the destination exists and for sites that use a "repository site" it's replacing the ids with sites that have valid files to ones that have invalid files. Since it does this when it's published it's possible the "working copy" works, then the published copy doesn't.

      This changes the behavior (in a minor release) and has broken some of our instances and caused problems for the instructors who verify it was working and after publishing for the students is broken.

      The best solution seems like it would be one that checks to see if the resource exists or not before doing the replacement but this is more work that we currently have time for, so I'm just going to add a property to allow switching to the old behavior.

      This property is default to true becaues it looks like this is handled better in 11, to disable for 10 set.
      samigo.publish.update.siteids=false

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                drramsey Derek Ramsey
                Reporter:
                jonespm Matthew Jones
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: