Hot answers tagged

20

DevDemon's Editor add-on does this. Editor on devot:ee.


9

Ok, this is something it looks like Ellis is not ready to really let people do even though it's in documentation, except perhaps developers who would provide via a full add-on installer and handling. However, it is possible. a. First, there is an EE interface to install new button features, but it is not called anywhere, Addons_installer:install_rte_tool. ...


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.


7

Try my answer on this question - works for me on a single template: EE Code within channel entries {exp:stash:set name="shortcode_inside_field" type="snippet"} <p>Hi there! It's important to set type="snippet" so that {shortcode_inside_field} will get automatically replaced with this sentence by the stash:parse tag later on.</p> ... now ...


6

As far as I'm aware there isn't a free plugin available currently that allows for this feature and it's not catered for out-of-the-box. However it would be possible for a tool to be developed and added to the tool library - I've just taken a quick look though the link plugin - this could easily be adapted to work for YouTube / Vimeo links if you feel so ...


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?


4

In your templates you can wrap any custom fields that might contain a non-https embed code with Low Replace, finding and replacing any non-https embed sources. For example: {exp:low_replace find="http://www.youtube.com/embed" replace="https://www.youtube.com/embed" } {your_custom_field} {/exp:low_replace} Low Replace will allow you to ...


4

I haven't seen this before, but we've never had anyone create an upload directory of /. before. My thoughts are you can do a FIND and REPLACE on template to correct, FIND <{filedir_15} and REPLACE with </ that should take care of all the closing tags, but I'm not certain if there maybe other '/' that might get skipped. I included the < so that you ...


4

The 'kludgy' technique you describe is exactly what we use on several major publishing websites. It's good to abstract your content images from the actual Wysiwyg field - it gives you much finer grained control and the ability to present images in different formats (slideshow for example). Our content teams love it. Then you use an {image_1} token to ...


3

Couple of suggestions: have you looked into using Textile or Markdown for your textarea? use a div.summary instead of a p CE String has methods to strip out tags from html, check remove_tags or remove_tags_except (I use this a lot personally - lots of other useful methods too in this plugin) Wygwam has a text-only mode that can be useful.


3

I think this may be somewhat more simple. Can you go to your Wygwam editor configuration, under Advanced Settings, in the drop-down, choose Skin and follow those instructions. Let's see if that helps? If that doesn't work, please check your dev console for any JS errors and report them here. Thank you! Edit to add: this is quite an old post, but you ...


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 ...


3

This can be done with any CKEditor-based WYSIWIG using the templates button, but beware as support for HTML5 (specifically figcaption) is spotty. I've personally worked around this by using a div.figcaption until CKEditor supports more tags.


3

I've been meaning to try Entry Widgets: https://github.com/iainurquhart/entry_widgets It's currently in beta though, could be a great fit for what you are trying to accomplish assuming it's far enough along at this point. It's a tiny bit different from WP though, I think it gives you the dev and your clients more control at the end of the day for setting ...


3

I would use jQuery to apply the caption using something similar to the code below: <script type="text/javascript"> jQuery(function($){ $('#content img').each(function(index) { $this = $(this).wrap('<div class="img-caption" />'); $('<p class="caption">' + $this.attr("alt") + '</p>').insertAfter($this); }); }); </script&...


3

Chrome's Inspector should be your best-friend. Inspect the element (right-click on it and click "Inspect Element"), go to "Computed Style", find the height and toggle it down to see the source-file.


3

There's an add-on called wygwam entries http://devot-ee.com/add-ons/wygwam-entries for P&T's wygwam which does exactly that. On github you'll find another wygwam one that can link to structure pages: https://github.com/pixelandtonic/wygwam_structure_pages


2

First step would be to make sure your browser isn't zoomed in on the text by resetting the zoom level. Here are FireFox instructions: http://support.mozilla.org/en-US/kb/font-size-and-zoom-increase-size-of-web-pages If you want to inject custom CSS into the CP, you can use this CP CSS & JS extension to do so. Using your browser's inspect tool will help ...


2

Channel Videos is a great solution for simplifying the process of embedding videos for clients.It has a visual interface so that the client can see a thumbnail of the video prior to publishing. You can search videos by keyword from the CP or just add the Youtube url - which is a lot easier than customising the embed code and copy/pasting. Additionally you ...


2

Check out this article by @tyssen: http://www.tyssendesign.com.au/articles/cms/more-stash-examples/ The 'shortcodes with Stash' examples should get you there. There's also this thread on Devot-ee: http://devot-ee.com/add-ons/support/stash/viewthread/3013 which tries to solve a similar NSM transplant solution.


2

This sounds very similar to another post, Characters are being re-encoded in control panel. Check in your system/expressionengine/config/config.php file. Do you have $config['global_xss_filtering'] set to TRUE? It should look like this in your config file: /* |-------------------------------------------------------------------------- | Global XSS ...


2

This isn't a Wyvern thing at all, its CKeditor's behavior. Wyvern just wraps CKeditor and provides a few EE specific features. Any and all behavior inside of the editing region is all CKeditor's behavior. You'll have better luck at the CKeditor forums for something like this.


2

I used the hacksaw plugin: {exp:eehive_hacksaw cutoff="</p>"}{copy}{/exp:eehive_hacksaw}


1

You should add the icon Paste From Word into your WYGWAM settings it looks like this: That'll keep basic formatting intact for you. Paste from plain text doesn't keep basic formatting. Paste from Word is handy when you are pasting content from other websites thave inline styles implemented as it removes all of that too!


1

First thing’s first; check to make sure you have the themes/third_party/wygwam folder in its place. I can’t tell you how many times I’ve accidentally uploaded the system folder instead. After that, I would suggest you use your developer tools in your browser to see if JavaScript is failing to load, and if so, where it’s being requested from.


1

I know this seems completely elementary, but I have dealt with a lot of EE1 sites that give fits and find that sometimes, it's as simple as adding quote around the value you are comparing in your logic. So something like this might work in your case: {if "{description_{user_language}}" != ""} {description_{user_language}} {if:else} {description_en} {...


1

You could use the built-in html formatting buttons in EE, which can be enabled on a Textarea field. This would meet your requirement of no br or p tags without the need of a plugin to strip them out. When the user clicks a formatting button the correct html is applied automatically, but it does leave the tags exposed (not a wysiwyg).


1

I can think of one potential drawback when using a wysiwyg for all your textarea needs: There are times where even though you want the user to have bold, italics, or link buttons, you don't want them to be able to add multiple paragraphs! If you find yourself in that situation when replacing textareas with wysiwyg fields, one reliable way around that is ...


1

The only downside I've ever run across is the lag when loading Wygwam on the publish pages, especially if there are more than one on the page. Wygwam is still using CK Editor 3 so it's possible that when they eventually update this to CK Editor 4 (like Wyvern has) the performance issues will be reduced or eliminated altogether. The upside for me, however, ...


1

I usually install a very stripped down version of any WYSIWYG editor, Wygwam included. That's usually less confusing for the client than seeing the code produced by the Rich Text Formatting buttons. If all you need are basic tags, the source code formatting is not that bad Aside from the RTE shipping with ExpressionEngine, here are the popular solutions. ...


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