6.x-1.26 Update Interferes With Custom Content Types Display
| Project: | Storm |
| Version: | 6.x-1.26 |
| Component: | Storm.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | fixed |
After the most recent upgrades to Storm, custom content fields in numerous non-storm related modules began to become unaligned. Node bodies would be pushed to the far left by fields arrayed above it, the links area at the bottom could likewise be kicked over, and custom fields became prone to random indentations (see accompanying pictures).
After much monkeying, I tracked the issues back to the core storm module. Deactivating it or replacing it with the older 6.x-1.24 version fixed the problem instantly (I did not try it with 1.25 as I fell back to the last known stable from my view, if you would like me to try 1.25 I will). It does seem that in some way it was effecting the spacing of elements in drupal. I tried numerous other methods in order to find a solution such as changing themes, running from MySQL backups, clearing cache, and inevitably nuked the modules on a test site and added them back one at a time until I got to Storm. Please advise if you need further details.
| Attachment | Size |
|---|---|
| IndentandBody.jpg | 16.62 KB |
| IndentedandLinks.jpg | 21.57 KB |
#1
There were some changes to the structure of the styles in #343818: title field gets displayed below body.
Do I understand that this is also affecting non Storm nodes?
#2
Correct. The affected nodes were all defined independent of Storm and contained no Storm elements. I inevitably found it by stripping out every module and inserting them one by one until the problem occurred. If I'm interpreting it correctly, custom cck fields are being treated as Storm entities and adopting the default Storm formatting. If you look at the indenting pattern it seems like the indenting of fields in a Storm ticket. In the inevitable errors created by stripping out all of the modules, most were predictable (imce, print, views) but what cued me in was an error call to Storm (see accompanying picture), an access call for Storm Tasks.
#3
I've changed the way that Storm includes the CSS. All CSS relating to the node view now is in a separate CSS file, which is included when Storm themes a node view. Therefore, it should fix the problem.
Please test the latest development release (from midnight).