Posted by suthy on October 24, 2008 at 2:47pm
6 followers
| Project: | Wysiwyg |
| Version: | 5.x-2.0-alpha1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
As titled, the WYSIWYG editor won't show for the body of content type blog. The blog entry content type comes from the blog module. It shows everywhere else, just not in the body field of blog entries. Kind of an urgent issue, any help is appreciated. Thanks.
Comments
#1
#2
The cause is that Blog module in Drupal 5.x is using a unusual (wrong) form element to hold the input format selector.
Not sure how to fix this, needs further analysis.
If you can upgrade to 6.x, that would be recommended. This has been fixed there.
#3
thanks for any help. we ended up just switching to the YUI editor
#4
Fortunately, this was easy to fix.
#5
Automatically closed -- issue fixed for two weeks with no activity.
#6
I've just encountered this problem - will this patch still work on 5.x-1.1?
#7
#8
This was fixed/committed a long time ago.
#9
I also encountered this problem with 5.x.1.1. It was because I'd made my own content type called "blog" instead of using the built-in Drupal Blog module (it seemed like a lot of extra code and I was already using CCK). Choices are to either rename the content type to something besides blog (probably a good idea in case you ever want to enable the blog module in the future) or to patch wysiwyg to check to see if blog is enabled before it goes unsetting and setting things in the form_alter.
#10
Committed without testing. Thanks.
Congrats to your first CHANGELOG.txt entry. :)
#11
I've just tried the latest update, 5.x-2.0-alpha1, and still don't get the TinyMCE WYSIWYG editor for the blog content type - it appears fine on all other content types, and I'm stumped.
I'm using the default blog content type and would really appreciate some tips on things to try!
#12
I had the same problem as wessex, with wysiwyg 5.x-2.0-alpha1 and TinyMCE 3.2.4.1 on a Drupal 5 site. After examining my debug output I could see why the patch code (which is now included in alpha1) does the workaround that it does for blogs, so it didn't make sense why it still wasn't working for blogs, but was fine for other content types.
In the end I resorted to hacking the offending line of blog.module (
$form['body_filter']['filter']... ) then commenting out the patch-code from wysiwyg.module, which took all of about 5 minutes and has been working perfectly since.Not the nice best-practice fix I wanted obviously, but for anyone reading this who is as frustrated as I was then you could try that to get you through, but remember it would be liable to being overwritten by future updates.
#13
I had same/similar problem and a lot of searching indicated Imagepicker was the problem. Either disable the whole module or uncheck (in the image picker options) the content types where the problem occurs. Dunno why but works for me.