Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Not sure what the 'theme' type in this piece of code supposed to convey, but there is no such type documented for Drupal 7, so it will just fall back to the default:
drupal_add_css($editor['library path'] . '/markitup/skins/' . $theme . '/style.css', 'theme');
The theme type meant a distinct thing in Drupal 6, not anymore in Drupal 7.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | wysiwyg-HEAD.markitup-css.3.patch | 1.14 KB | sun |
| #2 | wysiwyg-HEAD-markitup-css.975546.2.patch | 843 bytes | TwoD |
Comments
Comment #1
TwoDLooks like something we overlooked when porting to D7, don't remember if that had already changed back then. We've recently gotten a few other issues related to D7 API changes but I've been too busy to look at them yet. :(
Comment #2
TwoDD7 API changed since Wysiwyg was ported to it. We'll need to pass an array with a 'group' key with the value CSS_THEME instead. While we're tinkering with this, we might as well go all the way and use the 'basename' key to keep MarkItUp's style.css files from overriding Seven's style.css. That override makes the Seven theme look horrible so I'll bump this to major.
This patch should do the trick.
Comment #3
sunThanks for reporting, reviewing, and testing! Committed to attached patch to HEAD.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.