what's the story?

I'm still test driving FCKeditor so I'm suprised to find incompitibilities between the code generated by fck and the drupal core html filters. What's the point of having all these fancy features if they get stripped on submit?

eg: why use STYLE tags for bold and italic when good old fashioned,lightweight, degradeable, eco-friendly html 1.0 would do? Why force admins to open the STYLE tag filter and open the gates to all kinds of junk formatting?

eg emoticon filepath doesn't work for both drupal and fckeditor: easiest workaround is to copy ( ie duplicate!) the images folder from drupal/modules/fckeditor/lib/filemanager/editor/images to drupal/images so that the icons show both within the fck edit/preview window and in the published drupal document.

eg using PRE tags when drupal works around CODE tags ... not just filter but good old drupal.css styling

eg special characters are escaped (?), so ¾ doesn't appear in drupalview as '3/4' but '¾'

Does anyone else have a problem with this? Is it just me?

is there already a way round this and I'm just being dumb?

does HTML filter (filter.module) need an overhaul, to include ways of maintaining the "-//W3C//DTD XHTML 1.0 Transitional//EN" code standard when 3rd-party code generators are incorporated ?

Comments

edg’s picture

edg commented
Priority: Critical » Normal

The FCKeditor strips out HTML code and links are replaced with the code:

modules/fckeditor/lib/editor

EDG

ontwerpwerk’s picture

ontwerpwerk commented
Status: Active » Closed (works as designed)

fckeditor writes html, drupal's core html filters strip html and that's the way the world works at the moment.

If you want to use fckeditor, you must set the full html filter as default if you want the features of fckeditor to be useful