Enabling Quicktags causes blank pages at 'node/add/*'
Maedi - December 23, 2007 - 15:34
| Project: | quicktags |
| Version: | 5.x-3.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | tcblack |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
Once I enable the Quicktags module, every content type creation page 'node/add/*' becomes a blank page with no source. Problem is fixed on disable. I am using Drupal 5.5.
#1
Is This related to http://drupal.org/node/198326? to check modify line 124 of quicktags.module to match the patchline mentioned there. if it works let me know here.
#2
#3
#4
I don't think its related, tcblack, as #198326 is 'fixed' in 5.x-3.x-dev... I'm having trouble with something timing out here today. Looking into it now.
#5
leafish_paul:
I'm curious if 5.x-3.1-dev has fixed this for you.
#6
Currently using 5.x-3.x-dev (2008-Jan-15) on the site in question without problems (I know there's an update, haven't got round to that yet).
#7
editing and adding -- this module causes white screen of death; when you try and edit or add a new node content type.
#8
is this related to http://drupal.org/node/235972 "Blank screen in Firefox with jQuery 1.2.3" ??
i have this problem when updating to jquery_update 2 and using jquery 1.2.6
quicktags seems not functional and return blank page
Rizqi
#9
I 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?
#10
Subscribing. I am experiencing the same problem.
Drupal 5.12
jQuery Update 5.x-2.0.
#11
Hi!
I had the same problem. I have like 20 content types, 4 of them had this behaviour. I also use "meta tags" and "meta tags node type". I figured out that in the content types section, disabling the "allow ot editing meta tags" in those 4 types solved the problem.
Not a fix, not a workaround but if you don't need to change the meta tags manually, it worths a try.