Closed (fixed)
Project:
Wysiwyg
Version:
7.x-2.1
Component:
Editor - TinyMCE
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
6 Mar 2012 at 01:36 UTC
Updated:
4 Jul 2012 at 00:48 UTC
Jump to comment: Most recent file
Comments
Comment #1
twodIt seems Wysiwyg thinks it has attached the editor(s), as the 'Disable rich-text' link is visible.
Which browsers have you tested with?
Are there any JavaScript errors in the browser's console?
Have you tried with Wysiwyg 7.x-2.1?
Which editor versions did you test with?
Comment #2
obatard commentedI have the same issue with the following parameters :
- I' using Wysiwyg 7.x-2.1
- I'm using Tinymce 3.5
- I tried with Chrome, safari, IE9 and firefox
- In the console I have the following errors :
- property box-sizing unknown declaration dropped. And many like that
I can't display tinymce like in the screenshots above
Any ideas ?
Comment #3
twod@obatard, it looks like you haven't enabled any buttons for the editor attached to the Filtered HTML format on admin/config/content/wysiwyg.
Comment #4
joshbgosh10592 commentedHello all, Sorry about the late response, I've been moving this week and just now had time to get working again.
I've tested it with Chrome, Safari, and FireFox. All having the same results. Although, I now have a body text box that I can type in (picture in attachment)
I do not have any errors anywhere..
Sorry, I am running it in Wysiwyg 7.x-2.1.
I have tried it with TinyMCE 3.4.9 (Current) and CKEditor 3.6.2.7275 (which completely removes the body text box..
Comment #5
twodIt still looks like Wysiwyg itself works as it should so far, since the "Disable rich-text" link is there.
Are you sure there are no errors at all in the browser's JavaScript console?
I'm not sure about Mac browsers, but others show the console and other debug tools if you hit Ctr+Shift+J or Ctrl+Shift+I or F12 (IE8+). Then clear the cache and refresh the page to see any errors thrown during page load, as well as the loaded files in the Net tab (not in IE). If any of the files show up in red with an HTTP code 404 or 403, they could not be fetched from the server and you'll need to check that the full editor packages have been extracted in the correct places and they're publicly accessible.
Comment #6
joshbgosh10592 commentedOh, Browser console.. oops lol sorry! this is what the console displays. btw just for future viewers, for Chrome running on a Mac, its Option+Command+J
18event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
GET http://www.jeburger.com/sites/all/libraries/ckeditor/skins/default/skin.... 404 (Not Found)
ckeditor.js:23Uncaught TypeError: Cannot read property 'init' of undefined
a.skins.mckeditor.js:23
a.skins.loadckeditor.js:24
a.scriptLoader.load.tckeditor.js:22
a.scriptLoader.load.uckeditor.js:22
a.scriptLoader.load.vckeditor.js:22
a.scriptLoader.load.A.$.onerrorckeditor.js:22
I'm checking the path now.
EDIT. I'm ditching CKeditor and going with Tiny mce. the error I get is
Looking into that now.
Comment #7
joshbgosh10592 commentedSWEET! I have no idea why, but when I uploaded the libraries for TinyMCE, only one .js file went up.. I reuploaded everything, and no it all works! Thank you! I now just have one other question, using the "Insert/Edit Image" is there a way to upload from your computer into the Body? or just embed?
Comment #8
twodAh, that explains why the editors did not load.
No, most editors do not come with upload functionality as a standard feature as it requires serverside code.
There are "native" uploaders for several editors but we do not support them in the main Wysiwyg project as they don't integrate well with Drupal's way(s) of managing user uploaded files.
You can try some modules which provide Wysiwyg/editor plugins, like Media, WYSIWYG Image Upload, IMCE + IMCE Wysiwyg bridge, Insert, Image Assist and perhaps others found on the known Wysiwyg plugins list.
Comment #9
joshbgosh10592 commentedYea, oops lol
I see.. It would be an awesome feature to add in though. Maybe upload all images into something like /sites/files/wysiwygphotos or something.
I just tried Insert, and it seems to work perfectly, until I publish it.. then where the image should be, I get... [[{"type":"media","view_mode":"media_large","fid":"22","attributes":{"class":"media-image","height":"480","typeof":"foaf:Image","width":"360"}}]]
Yea, that doesn't look like a frogsquirrel..
Do you know much about the other modules you mentioned?
Thank you very much for your help thus far!
Comment #10
twodLooks like you didn't enable Insert's text filter for the format you're using. Most of the modules insert "filtertags" like that to store more info about an image and things like captions/mouseovers/whatnot in the database than could be represented in easily parsable XHTML.
Then they use a text filter to parse the content, find those tags and generate the actual markup needed to render the images.
An added bonus is that if the image URL changes (say you move to a new domain), every place the image is embedded in gets updated when re-rendered without you having to manually find and edit every node/block where it's used.
Comment #11
joshbgosh10592 commentedThat should be under Home » Administration » Configuration » Content authoring » Wysiwyg profiles » List right? If so, I do not see it, nor in the modules page...
I think I understand how thats works. Kinda interesting lol. Sorry for being so lost..
Comment #12
twodNo, it's under Content authoring => Text formats, and is part of Drupal Core.
It's where you manage what. Drupal allows to be rendered, in form of tag whitelists etc.
Btw, I recommend disabling the default HTML filter as it always removes style attributes from all tags, and there's no way to add attributes to its tag whitelist, if you want to allow users to enter content formatted with editors (colors, fonts, text size, background or other styles). I suggest installing http://drupal.org/project/wysiwyg_filter instead. Its whitelist allows for much more complicated rules.
(Everything entered by the user will still be saved in the database, filters just control rendering when viewing content.)
Comment #13
joshbgosh10592 commentedAhh! ok this vvv
"Converts Media tags to Markup
This filter will convert [[{type:media... ]] tags into markup. This must be enabled for the WYSIWYG integration to work correctly with this text filter."
Enabled "Image" and "Advance Image" and works like a charm! The theme I use has dark colors as background, so the text is white, for some reason now it displays as black text in the Wysiwyg text profile. But I can deal with just changing the color when I make something.
You sir, are awesome. Thank you so much for all of your time, trouble, and headache of dealing with an amateur haha.
Comment #14
twodYeah, the editor doesn't use the same markup structure to wrap the content in the editing area so the theme styles might need tweaking to also work inside the editor. You could also use a different stylesheet inside the editor, check out #487704: Theme background shows in editor window and its crosslinked issues.
Comment #16
joshbgosh10592 commentedSorry to bump, but Just for the future, I had to install the following to get this to work...
WYSIWYG
File entity
IMCE
Media
TinyMCE (you can get directions to install in the WYSIWYG config)
Go back into the Configuration > the-format-you-chose Configure > Check "Convert Media tags to markup"
Configuration>>Content Authoring>>the input format you chose, "Edit"
Expand "Buttons and Plugins" and select At least "Media browser" save.
I just had to fight through this again on a different site :(