I am faced with an odd-ball issue and I was hoping someone could give me some insight. Within the last three days I noticed that cck content fields (both Node module form and custom) have become completely out of whack in regards to rendering. Inline fields automatically kick out several spaces to the left or go out of alignment. Body fields lurch over far to the left. Links area elements in certain cases will also join body elements to the left, sometimes not (see attached pictures).

To resolve, I have:
- Tried different browsers (no effect)
- Changed themes (Garland, Zen, Newsflash all show the same problems)
- Restored to older SQL backups (no change)
- Rolled back all recent module upgrades (no change)
- Deactivated any module that I can without breaking base functionality (no change)
- Firebugged the site to see if something is messing with the css (nothing)

It seems to revolve around cck fields, so that if I move the body field to the top in Content Management > -type- > Manage Fields, for example, the body will align correctly, but the custom elements and links area gets knocked out of alignment. If anyone has a clue as to why this is happening or can push me in the right direction, I would be most grateful.

CommentFileSizeAuthor
IndentedandLinks.jpg21.57 KBTakaratiki
IndentandBody.jpg16.62 KBTakaratiki

Comments

markus_petrux’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

AFAICT, nothing has changed in CCK that may generate this kind of issues. There are a lot of things running behind the scenes on a Drupal site. It could be anything... though, you'll have to identify what in your content output is causing this unexepected layout, since when? is it because something in CCK output or stylesheets have changed? Is it related to the content of the body? Does your HTML validate? Is it broken by something else?

Takaratiki’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Thank you for the help. It diverted my thinking to other causes and I inevitably tracked the issue down to the newest revision of the Storm module, which I hadn't suspected before. I'm off to go bug them about it.