I have BBCode and FCKEditor installed. After installing quicktags, I just get blank pages if I try to create content (create content->story for example. A blank white page show up immediately).
I have BBCode and FCKEditor installed. After installing quicktags, I just get blank pages if I try to create content (create content->story for example. A blank white page show up immediately).
Comments
Comment #1
vm commentedblank pages are apache errors, have you checked your apache/http logs on your server ? having the exact error message being thrown would help a great deal in figuring out what is happening.
Comment #2
softtouch commentedApache log:
PHP Fatal error: Call to undefined function theme_stylesheet_import() in C:\\apache\\htdocs\\blogger\\sites\\all\\modules\\quicktags\\quicktags.module on line 124, referer: http://www.bloggercebu.com/node/add
Comment #3
vm commentedthe 1/14 release of quicktags 3.x-dev was supposed to have fixed that bug, are you sure you are using the latest release of 3.x-dev ?
Comment #4
softtouch commentedI will download it again (I have deleted it already)... I will report back in a while.
Comment #5
softtouch commentedI downloaded the latest BBCode (there was an update I missed), and the latest Quicktags.
This time, I did not get a blank page, but something else is screwed up...
There where usually Body: is written (create content), is just B:, and where Log message: is written, is just L:
And functions below the body textbox (like "Insert image or link", from another module) vanished completely.
Comment #6
naudefj commentedThis is not a BBcode problem. To get rid of this problem, simply disable quicktags.
Comment #7
softtouch commentedI know its a quicktags problem, thats why I posted it here under the quicktags issues....
Comment #8
tcblack commentedThis should now be fixed under 5.x-3.x-dev Please double check. Note that 5.3 is not listed on the main quicktags page yet.
Comment #9
softtouch commentedI tried the 5.x-3.x-dev, but it did not display anything and firebug shows 4 errors, something like getelementbyname or similar.
Comment #10
tcblack commentedJust a thought but why are you trying to combine FCKEditor with quicktags at all? does not FCKEditor provide a more WYSIWYG formatting? I haven't checked yet but this seems to be the best location to look for the origin of the problem. You have two editor modifications vying for the same space.
Comment #11
softtouch commentedI forgot to mention that it is a clean fresh install, no fckeditor or any editor at all... but I had the same problem with the site before (my post Jan 27).
Comment #12
tcblack commentedcan you tell me what other modules are installed, particularly any which might effect editing?
Comment #13
softtouch commentedAt the time I tried the quicktags (yesterday), I had only views, image, og and cck installed, no editor or editor-enhancements like bbc etc., just plain.
Comment #14
Krummrey commentedI had the same problem with version 5.2 that's listed on the project page.
With 5.3 all works fine for me.
Just thought I'd let you know. Set the Issue to "fixed".
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #16
sourabh.iitm commentedHi,
I also have blank pages after installing this.
But the problem is only in those content types which are having cck fields.
Another interesting thing is this module is giving me problem during editing pages with more than 5-6 cck fields. If i have only 1 or 2 cck fields, than this is working fine.
I have tried this on 2 Open Suse & Debian OS.
Any info?
Comment #17
lincolndsp commentedI have the same problem, when I add or edit node in Firefox I get a blank screen constantly loading with just Quicktags buttons visible. It works oK in Opera. Quicktags works fine in all browsers for drigg posts, but in add or edit nodes it crashes everything.
Has anybody got a solution to the problem?
quicktags 5.3
Drupal 5
Comment #18
duaelfrThis version of quicktags is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.