Closed (works as designed)
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
7.x-1.7
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Mar 2012 at 12:19 UTC
Updated:
5 Apr 2012 at 11:52 UTC
Comments
Comment #1
mkesicki commentedJust to be sure . You don't see CKEditor in comments form ?
Comment #2
Drunoober commentedyes that is correct no ckeditor in the comments form for any of the content types.
thank you for taking a interest. cheers
Comment #3
mkesicki commentedDo you see any errors in Firebug or similar tool ?
Can you check if all request are correct (Firebug net tab) ?
Does your comments fields use text filter where CKEditor is used ?
Comment #4
Drunoober commentedok something strange just happened.... I will illustrate step by step what happened
Yesterday: The comment form would not show the ckeditor
This Morning: I get a message the the ckeditor has a security update that needs installing (7.x-1.6 to 7.x-1.7)
I then write this post to the site asking for help about the issue
I go to lunch about 1 hr later I come back.
and answer your post... #2
and I look at the site again and BAN! everything work!!! LOL
What I think has happened is the following...
Installing the security updated fixed something which needed to wait for a cron run to make it take effect. since I have cron run every 3 hr it did not happen right away. This update broke my skinr module 7.x-2.0-alpha1 to fix it I just uninstalled it and re-installed it. Everything is Good now!! I will let you know if the update "Broke" anything else but for now everything seems fine.
I hope this helps you in the development of your integration module. (I switched it to bug report... hope you don't mind)
cheers. :D
Comment #5
wwalc commentedGreat to hear that CKEditor started working :-)
Looks like a caching issue. Next time try the following: clear cache in Drupal administration section and then clear cache in a browser.
Comment #6
Drunoober commentedThanks... yea its great
Not sure but I don't think it was a cache issue after all I did clear the cache frequently yesterday without change what I did not do is run cron right away after I installed the update just did not think about it XD.
I just would like to inform future viewers that have my same problem that if they update the module to 1.7 from1.6 and run cron they will also have the comments issues fixed in addition to fixing any intended security hole that the upgrade fixes.
Once again thank you all for the support which makes Drupal ROCK! :D
cheers.
Comment #7
Drunoober commentedSorry guys... having another problem with rendering the Editor.
I am trying to insert text with a href link under views 7.33 given my previous case of the editor not showing I don't know if this is a ckeditor issue of a views one. So if I don't get a solution from you ckeditor experts I will ask at the views guys for a hand in the matter.
Specifically, under the section behavior of views with no content (sorry don't know the english wording since I am using a translated version) I add a global text area and the input box gives me the options for different input filters but non of them work they can get selected but that is all it does the input box stays as plain text. So no formatting of html tags.
hope I was clear... can it be fixed buy you or is it a views issue? or is it by design?
Comment #8
mkesicki commented@Drunoober
in Views for Drupal 7 CKEditor or any other WYSIWYG editor is turn off by Views developers.
In Views code
#wysiwygattribute for textarea is set toFALSE, so Views developers don't want wysiwyg editor for this fields.Comment #9
dczepierga commented