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.Using latest dev and ckeditor 4.1.2 full. Neither setting it to "Hide" or "Top" does what is expected - the path is always visible and at the bottom of the editor.
Comments
Comment #1
TwoDThat's because there is no such setting in CKEditor.
The shown settings widgets date back to when Wysiwyg only supported TinyMCE 2, and it now uses the same form for all editors.
I've been working on cleaning up the settings form and adapting it to suit more recent versions of several editors, but the patches have grown so large I needed to split them up into smaller chunks. I have not created issues for all parts yet, but they'll hopefully be done before my vacation ends within a few weeks. By then you won't see the "Path location" setting for CKEditor anymore.
If you need to move that part of CKEditor somewhere else, I think you'll have to create a new theme for the editor, but I've never tried that myself. You can then select that theme by implementing hook_wysiwyg_editor_settings_alter().
Comment #2
klonosThanx for taking the time to reply.
I don't want it moved. I need it removed/hidden, so I tried setting .cke_path and #cke_1_bottom to
display: none, but it doesn't seem to work.Comment #3
TwoDJust
.cke_bottom {display: none;}somewhere in your theme stylesheets should work.Comment #4
klonosWell the element is rendered as
<span id="cke_1_bottom" class="cke_bottom" ...>. So, I tried setting both the class and the id to{display: none;}and I also tried putting the code to a generic theme css file as well as in the ckeditor specific css file (the one you define from the Editor CSS setting in the CSS tab under /admin/config/content/wysiwyg/profile/{text_format}/edit). None worked though.What finally did the trick was using the class (the id wouldn't work) in a theme css file (putting the code in the editor specific css file wouldn't work either) and adding
!importantto the css rule:Comment #5
TwoDThe id should be different for each field or the editor would confuse them, hence why you need the class. The element is not inside the editing iframe, which is why you need to have it in the Drupal theme.
I injected the style rule using the Developer tools, which I suppose placed it last in the override queue. When it was actually in the stylesheet from the start, using
!importantwould be necessary unless using a more specific selector than the one used by CKEditor itself to set the style.I'm glad it worked out for you. :)
Since there isn't a setting in CKEditor which we could toggle using that checkbox, and it's going away as part of a different issue anyway, I'll close this issue.
Comment #6
klonosYep. I merely posted my comment back in #5 in order to have it in the queue as a solution for others that might face the same issue in the future. Perhaps there'll be less "bug reports" about issues like this when the respective non-relevant settings are gone in a per-editor basis. Then people will know that they have to do it in the theme level ;)
Thanx for your time.
Comment #7
TwoDYes, that's exactly what I'm hoping for. I'm also going to try to add more information about which widgets operate which editor settings internally which I hope also helps.
Comment #8
TwoDFIY, one of the issues I mentioned above is here: #2018439: Move editor-specific options out of the default profile UI.
Comment #9
klonosThanx. I'll follow.