Playing around with the media module and discovered a strange thing.
First I embedded an image using the CKEditor media browser as well as scaled it down a bit in the editor.
Later, as I was playing with adding the Multimedia asset field to the image type managed by media, I added the same image using the field type media to the same node.
The result is that that both images are then displayed in the same size, the size from the embedded image. If I edit the node and change the size of the embedded, then that will change the size of both when viewed to the new embedded size.
How to recreate:
- Add the multimedia browser to the WYSIWYG editor.
- Add a Multimedia asset field to the content type.
- Embed an image in the editor
- Select the same image for the Multimedia asset field
- Scale the embedded image and the other will change its view size as well.
This only happens when the same image are used in both places. Different images are viewed different.
Comments
Comment #1
JacobSingh CreditAttribution: JacobSingh commentedI think this is now resolved. At least with styles 2.x can you try that and re-open if still a problem?
Comment #2
tsvenson CreditAttribution: tsvenson commentedConfirmed, its fixed using the latest devs of Media and Styles.
Comment #3
tsvenson CreditAttribution: tsvenson commentedHm, have to reopen this issue since the problem is still there to some degree.
When saving a node the embedded and attached images (same image) correctly have different sizes, but when clearing the cache the attached image is getting the same size as the embedded.
So, the problem is sort of half solved...
Comment #4
JacobSingh CreditAttribution: JacobSingh commentedYeah, I see it too...
Ugh. It only lasts one page load after a cache clear... I'm guessing it is because the file which is inline gets cached, and because it is generated first, it caches the rendering for the entity.
After that happens, the other one gets affected. On the next page load, the content filter cache is done, and the entity works properly.
I don't know how we detect the case here and not disable caches where they shouldn't be.
Comment #5
JacobSingh CreditAttribution: JacobSingh commentedThis is probably the same issues as:
#721754: A node cannot be displayed in different view mode on its own page
:(
Comment #6
Dave ReidMarking this as a duplicate of a new #1984424: RFC: Disable caching for media filter