Closed (fixed)
Project:
Classified Ads
Version:
6.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Oct 2009 at 16:43 UTC
Updated:
25 Aug 2011 at 20:53 UTC
The text editor does not show. I'm not sure why this. I'd give more information but I haven't any. Does anybody have any ideas? My guess is that there is some class that triggers the text editor, but I don't know what it might be. It asks for input format.
Comments
Comment #1
protoplasm commentedThis is also an issue for me since switching to WYSIWYG Tinymce. According to a thread comment in WYSIWYG, the problem is related to "the key 'filter' for its input format selector, which means Wysiwyg module is unable to find it." WYSIWYG tells developers that they must use 'format'. See: http://drupal.org/node/358316. I hope a patch can be issued to address this problem.
Comment #2
Adam S commentedActually, the problem was with the aggregate css file created by Drupal when it's optimized. Rather it was to optimized for TinyMCE to work in IE under Admin -> Configure -> Proformance. I don't know if they have patched the problem yet.
Comment #3
protoplasm commentedNot the issue with me. No editor shows regardless of aggregate css enabled or not. Actually, IE doesn't even work for me if css isn't aggregated.
Comment #4
Adam S commentedOh, I wasn't paying attention. This is the ed classified issue queue. First, for the TinyMCE to work in IE with WYSIWYG mofule the css has to be aggregated unless they patched it.
Second, the Javascript used to count the character in the classified ad conflicts with the rich text editors so they just disabled it. There is no fix. I actaully made a sand box with only edclassified installed the maintainer of the WYSIWYG. There is no easy fix.
What editor were you using before that worked with ed-classified. I didn't have any luck with any of them.
Comment #5
protoplasm commentedIf I am remembering correctly,it was the non-wysiwyg-api fckeditor that I had working with ed classifieds.
Comment #6
fgmThis does not happen on 6.x-2.x-dev with current versions of WYSIWYG (6.2.4) and TinyMCE module (6.x-1.1-dev),
It /does/ happen on 6.x-2.x-dev, however, with WYSIWYG used directly with the TinyMCE plugin. But this is fixed in 6.x-3.x-beta1. Please upgrade.
Comment #8
fgmRewording to group with related issues.