Breaks WYSIWYG/TinyMCE module
bigmack83 - January 16, 2009 - 11:33
| Project: | Filter by node type |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
It seems to be random, uninstalling and re-enabling module fixes it. But when i first enabled the module it broke my WYSIWYG.module with the tinymce addon. When going to a /node/add page it simply dissapeared. if i disabled this module it reappeared. enabled it, wysiwyg in the body field again dissapeared. When i uninstalled this module and re-enabled it, the wysiwyg module seems to stay for now. I will report back if i have the problem again. Looking in my log entries the only notice was:
Parsed JavaScript file sites/shamce.net/modules/wysiwyg/wysiwyg.jsSo i couldnt find any real errors. as it re-appeared im only marking it as a normal but and not critical. but i figured it is something that might need to be looked into. Or at least if anyone knows why it is happening they can let me know why
#1
Ok, so when i edit the node type and change what filter is available for that node type, the wysiwyg editor dissapears. the only log entries im getting are parsed a .js file. Uninstalling the module and re-enabling it restores the editor, and editing the content type again makes it dissapear.
#2
WYSIWYG is a complicated module that's still in active development, and fbtn is one bit hack. :-) Not knowing how wysiwyg works, I couldn't even begin to speculate.
This is also not critical as it's a module interaction question, not a core functionality bug of this module.
#3
Same problem here. I only can't get 'Filter by node Type' working at all. Can somebody describe exactly the steps for a workaround?
#4
I also posted it at #366018: Filter by Node Type module breaks WYSIWYG API
#5
I was adviced to go to a new module: #359727: Breaks WYSIWYG/TinyMCE module
This one is more sophisticated and it works perfectly with WYSIWYG/TinyMCE.
#6
hi, i am having the same problem on 5.x (with wysiwyg api).
the problem seems to be related to whether the default format is allowed too or not (if i allow it, tiny is there)