COU-244 - Media referenced in a Grid Layout isnt transferred

Created by Mikkel Holck Madsen 12 Nov 2015, 21:52:47 Updated by Sebastiaan Janssen 20 Nov 2015, 10:47:32

Had a simple umbraco site, that contains of one tempalte. This template just has one property, that is of type Grid Layout.

  1. When i add a editor to a row, of type Image, and choose a image(its using a media picker), this image doesnt get transferred to the next environment.
  2. When i add a editor to a row, of type Rich Text, and inserts a image(using a media picker), this image doesnt get transferred to the next environment.

It seems that the deployment engine doesnt look for references in the grid, and just copies the raw json content in it. The thing that is transferred is referincing the image, but just showing the "not found" default browser image. If i manual transfer the image(chooses it in the media library), the data gets fixed, as it finds its image again.

This was done on a 7.3.0 site using a Nightly of Courier from 2015-11-11, called 2.51.3(but not the official release)

Comments

Shannon Deminick 19 Nov 2015, 10:24:18

This is working now. See PR: https://github.com/umbraco/UmbracoDeploy/pull/4

For testing:

  • Setup 2x environments configured for both normal courier + uaas deploy
  • On env #1: ** Create a doc type with 2x tabs: Grid + RTE ** Add the grid to the grid tab ** Add the rte to the rte tab ** Right click the doc type, use Courier menu item and send it to env #2 ** Create a content item of this type

Here's the steps that we'll repeat a few times:

  • Add an image cell to the grid - Create a folder in the media dialog and drag an image there, select it
  • Add an rte cell to the grid - add an image to the rte - Create a new folder in the media dialog, drag an image there and select it
  • In the normal rte, add an image there (same process as above)
  • Save/publish the item

Now we need to test the various ways to deploy:

  • Follow testing steps above, then use the normal courier context menu item and send it to env #2 - verify that everything is on env #2
  • Follow testing steps above, then use the uaas courier context menu to queue the sending, then use the uaas dashboard to send the data to env #2 - verify that everything is on env #2
  • Follow testing steps above, then use the uaas courier action menu on the content item (i.e. in the save publish drop down) to do the sending to env #2 - verify that everything is on env #2


Priority: Critical

Type: Bug

State: Fixed

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 2.51.3

Due in version: 2.51.3

Sprint:

Story Points:

Cycle: