I'm having a problem with image field alignment when using the two-column stacked layouts. The strange thing is that it's only happening with one particular node. Other nodes are displayed just fine.

I have my content display set to include fields in the left column, right column, and footer. The image field is on the right. With the problem node the images are displayed centered and below the left-side fields even though the HTML source appears to include the proper multi-column layout with the image field on the right. The images associated with both nodes are the same width. Could someone please take a look at these two nodes and let me know if you see something that's obviously wrong?

This node is displayed properly. This node has the display problem.

Comments

Version:7.x-2.2» 7.x-2.3

This issue persists in the 7.x-2.3 release.

Status:Active» Closed (works as designed)

After doing some more digging I believe this is an issue with Ubercart and the way it displays product attributes. I've created a support request (#2006912: Attributes Affecting Multi-Column Display in Display Suite) in the Ubercart issue queue. Display Suite seems to be working as designed.

Status:Closed (works as designed)» Active

Reopening...

One of the Ubercart developers noticed that the issue is that the /sites/all/modules/ds/layouts/ds_2col_stacked_fluid/ds_2col_stacked_fluid.css file is not included on the page with the alignment problem. What would cause this file to be omitted on some pages and included on others?

For what it's worth I've temporarily copied the classes from the ds_2col_stacked_fluid.css file to a local.css that's associated with my theme to work-around whatever the problem might be. The example I noted above thus looks fine for now.

Version:7.x-2.3» 7.x-2.4

Still a problem in 2.4.

Status:Active» Closed (works as designed)

We can see the issue but we can't reproduce it locally. Some module or custom code must affect the css somehow. No clue what can cause this. Closing this for now as I don't think anyway will be able to help you in this queue without debugging everything on your side I'm afraid.