We’ve been having an issue with some of our media items
which is affecting one of our major clients. We’ve been talking with the HQ
about this but not had much success finding a solution so thought I’d throw it
out to the community as I know you’re pretty damn good J
Essentially what is happening is this:
Sometimes our media items will basically reorder the values
of the xml returned while using umbraco.library:GetMedia() switching around the
url stored in umbracoFile for say the image width or image’s byte size. So this
causes images to then show a broken image.
This seems to happen at random, in that we haven’t found the
trigger, and not just one but multiple images around the site all break at the
same time.
The solution for the moment is to find the image in the
media library and re-save it. This is ok to patch it for now but we really need
to find out the cause to fix it forever!
If you look in the database the media has saved correctly in
the cmsPropertyData table in that broken image are working images all share the
same order and propertytypeid as each other.
It’s when you look in the cmsContentXml table for the same
images when you see that it’s all been save weirdly - this seems to be what is outputted when using GetMedia()
As you can see we have 2 umbracoFile nodes in the first
example and neither showing the path to the image. Infact it seems like they’ve
shifted along 1 place when being generated.
And with this we’re stumped.
We are using umbraco v4.7.1.1 which was upgraded from v4.7.
It’s running on a dedicated server which is the same setup as all our other one
and no other site has this problem.
We have the following packages installed
FALM Housekeeping
FamFamFam Icon Package
Relation Types
XSLTouch
UComment
ImageGen
Umbraco Contour
Umbraco Courier
Cmsimport
If anyone’s got any ideas for further investigation or have
seen this issue before please let us know we would be most grateful.
I've once had a situation where nodes got corrupted in a similar way. It was because multiple people were working on the same content node and saved it at the same time. The solution was the same so by saving the corrupted node again it was fixed. Could that be the trigger?
Issue with GetMedia() xml being outputted
Hi guys,
We’ve been having an issue with some of our media items which is affecting one of our major clients. We’ve been talking with the HQ about this but not had much success finding a solution so thought I’d throw it out to the community as I know you’re pretty damn good J
Essentially what is happening is this:
Sometimes our media items will basically reorder the values of the xml returned while using umbraco.library:GetMedia() switching around the url stored in umbracoFile for say the image width or image’s byte size. So this causes images to then show a broken image.
This seems to happen at random, in that we haven’t found the trigger, and not just one but multiple images around the site all break at the same time.
The solution for the moment is to find the image in the media library and re-save it. This is ok to patch it for now but we really need to find out the cause to fix it forever!
If you look in the database the media has saved correctly in the cmsPropertyData table in that broken image are working images all share the same order and propertytypeid as each other.
It’s when you look in the cmsContentXml table for the same images when you see that it’s all been save weirdly - this seems to be what is outputted when using GetMedia()
Broken image:
Working image:
As you can see we have 2 umbracoFile nodes in the first example and neither showing the path to the image. Infact it seems like they’ve shifted along 1 place when being generated.
And with this we’re stumped.
We are using umbraco v4.7.1.1 which was upgraded from v4.7. It’s running on a dedicated server which is the same setup as all our other one and no other site has this problem.
We have the following packages installed
If anyone’s got any ideas for further investigation or have seen this issue before please let us know we would be most grateful.
Cheers.
I've once had a situation where nodes got corrupted in a similar way. It was because multiple people were working on the same content node and saved it at the same time. The solution was the same so by saving the corrupted node again it was fixed. Could that be the trigger?
Jeroen
is working on a reply...