Courier appending image size to image tag src attribute
Hello community!
I have a problem with a specific type of content deployment using Courier.
Setup: I'm running umbraco 4.11.8 with courier 2.7.8.15.v4. The sites, both source and destination, are running on IIS7, .net 4 on a windows 2008 R2 server.
Scenario: - I insert an image ("/media/en-gb/289645/koala.jpg") into a piece of rich text content and resize that image to differnet dimensions, using the RTE interface. - Save and publish the content - Courier the Node to the destination site - Check the destination site, the image appears broken in the RTE and inspecting the HTML I notice that the src attribute now contains the image dimensions appended to the image name ("/media/en-gb/289645/koala_500x375.jpg") - Removing the image dimensions from the src attribute restores the image on the destination site. The media file itself is transferred perfectly fine.
Courier appending image size to image tag src attribute
Hello community!
I have a problem with a specific type of content deployment using Courier.
Setup:
I'm running umbraco 4.11.8 with courier 2.7.8.15.v4.
The sites, both source and destination, are running on IIS7, .net 4 on a windows 2008 R2 server.
Scenario:
- I insert an image ("/media/en-gb/289645/koala.jpg") into a piece of rich text content and resize that image to differnet dimensions, using the RTE interface.
- Save and publish the content
- Courier the Node to the destination site
- Check the destination site, the image appears broken in the RTE and inspecting the HTML I notice that the src attribute now contains the image dimensions appended to the image name ("/media/en-gb/289645/koala_500x375.jpg")
- Removing the image dimensions from the src attribute restores the image on the destination site. The media file itself is transferred perfectly fine.
This appears to be related to the following issue: http://our.umbraco.org/forum/umbraco-pro/courier/14311-Images-in-Rich-Tex-Editor-don , but isn't exactly the same and it doesn't have any kind of resolution against it.
Anyone else had this problem and know of a work-around/solution?
Thanks,
R
is working on a reply...