- 🇺🇸United States bluegeek9
Thank you for your contributions to this issue. As Drupal 7 has reached its End of Life and is no longer supported, we are closing this issue. We encourage you to upgrade to a supported version of Drupal.
There are some efforts ( #1043570: Floating images left and right → and #1094016: Allow Wysiwyg styles → ) to improve the WYSIWYG functionalities in Media and Styles modules.
I have been analyzing both module's code, and I think that styles does not handle correctly the integration in that case.
Media filter adds the possibility to insert media fields (with its own syntax) embebed in any text input. The most common usecase of this is in node's body fields combined with WYSIWYG.
When a node is saved (node_save) the textinput filled by the user is processed by all the input filters and results in two different values: value (as it's been introduced) and safe_value (as it's been processed by the filters configured). Nodes afterwords, to improve perfomance, are cached internally so safe_value is no longer generated till the next time node is being rendered and caches have been cleared previously.
The problem is that when media processes the raw value it uses styles module styles_field_formatter_view function to render the information, which uses itself a call to a theme function that could be overwritten by any theme.
This has no sense, because it is processed just a time and in most cases by the administrator which has a different theme than the rest of the users. So when the node is rendered with an anononymous user who has a different theme, the field will be rendered with the template (sytles.tpl.php) of the administration theme.
There are two different solutions:
I would have liked to attach a patch, but my knowledge of styles module architecture is not good enough.
Closed: outdated
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thank you for your contributions to this issue. As Drupal 7 has reached its End of Life and is no longer supported, we are closing this issue. We encourage you to upgrade to a supported version of Drupal.