I've been searching but could not find a solution. Updating from Wysiwyg 7.2.1 to 7.2.2 breaks all paths for the editor. Means images are not found and CSS-Styles either. Define-CSS-paths remained unchanged. Using the dev-Version didn't help either. Switching back to 7.2.1 brings everything back. What did you change inbetween?

Nice module otherwise.
Thanks,

upunkt

Files: 
CommentFileSizeAuthor
#2 wysiwyg-ckeditor-baseHref.1861174.2.patch474 bytesTwoD

Comments

Not much, but we did change the baseHref setting as part of introducing support for AJAXy lazy-loading, which I suppose could affect that. Strange though since it should default to the correct path.

Could you try creating a simple module like this and see if it helps:
sites/default/modules/custom/custom.info

name = Custom
description = Custom tweaks for this site
core = 7.x

sites/default/modules/custom/custom.module

<?php
/**
* Implements hook_wysiwyg_editor_settings_alter().
*/
function custom_wysiwyg_editor_settings_alter(&$settings, $context) {
  if (
$context['profile']->editor == 'ckeditor') {
   
$settings['baseHref'] = $GLOBALS['base_url'] . '/';
  }
}
?>

I just remembered someone else having this issue, maybe it was a bad idea to fall back to the default value of that setting.
Are you running your Drupal site in a subfolder or is it directly on the domain?

Assigned:Unassigned» sun
Status:Active» Needs review
StatusFileSize
new474 bytes

This patch simply puts back the baseHref setting removed in #356480: Lazy-load editors, with an additional comment on why it's there.
Just want sun to see this before committing it.

Assigned:sun» TwoD
Status:Needs review» Reviewed & tested by the community

Thanks, let's do this.

Status:Reviewed & tested by the community» Fixed

Committed #2 to 7.x-2.x and just the comment to 6.x-2.x and 5.x-2.x to keep things in sync.

Thanks for reporting, testing and reviewing. The dev snapshots will be updated within 12 hours and this fix will be part of the next official release.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.