Hot answers tagged

19

You need to create a custom config file for CKEditor that redefines how HTML is generated for images. Create a JavaScript file called something like 'ckeditor_config.js' and then set Wygwam to use it. You can do this by adding an advanced setting to your Wygwam editor configuration. Add the 'customConfig' setting and enter the path to the JavaScript file you ...


15

Here’s an extension that should do the trick for you: Wygwam jQuery Spellchecker Enjoy!


14

There is a one year old thread on Pixel&Tonic’s support forum. To use Typekit with Wygwam/CKEditor you have to include two scripts in your <head>: <script type="text/javascript" src="//use.typekit.net/XXXXXXXX.js"></script> <script type="text/javascript">try{Typekit.load();}catch(e){}</script> Scott Wise figured out this ...


8

You can do this without editing the Wygwam source. First you need to create a custom config file for CKEditor. Create a JavaScript file called something like 'ckeditor_config.js' and then set Wygwam to use it. You can do this by adding an advanced setting to your Wygwam editor configuration. Add the 'customConfig' setting and enter the path to the JavaScript ...


8

Go to Add-ons > Modules > Wygwam > Editor Configurations and select the configuration you want to edit. Look for the Restrict allowed HTML? setting and make sure it is set to No.


7

In the Wygwam editor config, in advanced settings, add the 'autoGrow_maxHeight' setting and make it equal to the 'height' setting.


7

For any variable that needs extra processing, like the Wygwam variable type, use the tag syntax rather than the variable syntax: {exp:low_variables:single var="my_wygwam_var"} Note that having early parsing on or off is irrelevant for the tag syntax, so you can leave it off.


6

These tags are stripped out of the editor view because the "Restrict Allowed HTML" setting is set to YES for that field's WYGWAM configuration. Changing this setting to NO fixes the issue. Go to Add-Ons -> Modules -> Wygwam ->(your toolbar config) and set the "Restrict Allowed HTML" setting to 'no'.


5

I'm hoping I'm getting this right. I'm not a Wygwam/Assets expert, so... The way we have handled it is by setting our EE file upload preferences 'URL of Upload Directory' settings with the relative path from the web root. For example: '/images/article_images/' I believe Wygwam then uses the {fieldir_1} syntax when it saves the image path, so in the channel ...


5

The themes/third_party/wygwam/lib/ckeditor/config.js file actually comes with the code necessary to do this – you just need to uncomment it. Have you tried that?


5

You can also swap to the very similar addon Wyvern, by BoldMinded, which has Typekit and Google Fonts support built in via the settings screen.


5

Having recently upgraded an EE v1.6.8 site to v2.6.1, I had to re-save each of the Wygwam fields to fix the "defer" PHP notice. http://website.com/manage.php?D=cp&C=admin_content&M=field_group_management


5

I now have definitive answers. Basically neither works with autosave. EllisLab have noted that their Grid fieldtype doesn't work either. EllisLab https://support.ellislab.com/bugs/detail/19838 P&T Have responded with: Unfortunately, Wygwam currently doesn't have support for EE's auto-save functionality, but I've added to our list to look into for ...


5

I was able to fix this by adding back in the indent block plugin from CKEditor. The process of doing so is as follows... Download the CKEditor Indent Block Plugin. Make sure to download the version that matches the version of CKEditor being used by WYGWAM. Check the WYGWAM changelog if you're not sure. Unzip and install that folder to themes/third_party/...


4

Instead of modifying CK Editor files which would likely get nuked if you update the add on you are best to make a customConfig in the Editor Configurations. Change this and save this out to where you keep your front-end templates. var typkitID = 'XXXXXX'; CKEDITOR.on( 'instanceReady', function(ev) { var $script = document.createElement('script'...


4

This was fixed in Matrix 2.5.3. http://pixelandtonic.com/matrix/releasenotes


4

We just released Wygwam 3.1.2 which brought back the text alignment buttons.


4

To make sure extra processing is done before the var is put in the template, use the tag syntax rather than the variable syntax: {exp:low_variables:single var="my_wygwam_var"}


4

You can disable CKEditor’s content filtering functionality by going to Add-Ons > Modules > Wygwam > [your config name], and changing the “Restrict allowed HTML?” setting to “No”. That’s a new setting as of Wygwam 3.1, so you may have to update Wygwam first.


4

CKEditor (which is the editor used by Wygwam) has a feature called Templates that you can use for this. With CKEditor content writers can select a template from a list by clicking the Templates button in the toolbar. A template is a predefined piece of HTML that is inserted into a document. Using this feature, the user does not need to start ...


4

I figured it out. I needed to set Restrict allowed HTML? to 'No' in the Wygwam configuration settings. This is located on the WYGWAM Module settings page. Works as expected now.


4

I found the answer. Devotee has a list here.


3

If the reason is appearance, you can remove any margin/padding formatting with css, like: table p {padding:0; margin:0} Or you can add specific classes to the styling menu of wygwam for tables, for a more fine grained control over styling tables.


3

No, you will not lose any existing data. Additionally, Wygwam gives you an option to "convert previous entries" which is very handy if your textarea field formatting was set to "Auto <br />" or "XHTML"


3

fmz - there is not a way to use Wygwam with the forums; though since you have control over the forum themes you may be able to get a CKEditor directly in there.


3

I'm not sure how agressive you want to get with stripping inline styles or if there are certain instances where you'd need to allow them, but you could use some simple jQuery to strip them out. Something like has worked for me in the past: $('.wygwam p').removeAttr('style'); You could obviously modify this depending on the element(s) your client ...


3

This is a Chrome/Iframe/contentEditable bug that usually crops up when you set Wygwam to use your own CSS file. You should be able to fix it by adding a line-height to your CSS. (See https://getsatisfaction.com/pixelandtonic/topics/display_bug_showing_lines_across_editor_when_there_is_lots_of_content#reply_10264807)


3

I was able to fix a similar problem on a different site. First, make sure the thumbnail directory has write permissions. The command I used was something like "chmod -R 777 expressionengine/cache" Second, take a look at the Image Resizing Preferences in the admin: Go to Admin-> System Administration-> Image Resizing Preferences Set Image Resizing ...


3

NB This P&T support thread seems to suggest that CKEditor (which is the editor WYGWAM is based should automatically strip <script> tags, so might be worth checking your themes/third_party/wygwam/lib/ckeditor/config.js file and asking on their Get Satisfaction if that isn't the case for you. That aside. even if you can do this in CKEditor, my ...


3

You'll need to override the default CKEditor rules for processing P tags. Add this: this.dataProcessor.writer.setRules( 'p', { indent : false, breakBeforeOpen : true, breakAfterOpen : false, breakBeforeClose : false, breakAfterClose : true ...


Only top voted, non community-wiki answers of a minimum length are eligible