Hot answers tagged

4

unexplainedBacn is right. Or you can also use the XML Encode plugin for this. It's actually included with ExpressionEngine This plugin converts reserved XML characters to entities. It is used in the RSS templates. To use this plugin, wrap anything you want to be processed by it between these tag pairs: {exp:xml_encode} text you want ...


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.


1

First thing you need to do is upgrade EE, Wyvern, and CKeditor. Sounds like you're using really old versions, which I don't support.


1

As a workaround, you could wrap the offending content in <![CDATA[{content}]]> tags. Like so: <description> <![CDATA[ {body} ]]> </description> This won't actually escape the characters, but it will tell the validator to not worry about it.


1

Why not use a javascript solution like this - http://www.zazar.net/developers/jquery/zglossary/ Create a channel called "glossary" then create the json file from the channel? There are a ton of plugins out there with a few more features then the plugin above.


1

That should be possible by just adding a custom styleset. You can create a new .js file and then set the values in a Javascript array format: CKEDITOR.stylesSet.add( 'my_styles', [ { name: 'Abbreviation', element: 'abbr', attributes: { 'lang': 'en' } } ]); Full documentation is here. So if you're using Wygwam for instance then create a new folder in ...


1

Here's a trick: This allows the CMS to serve files over SSL or non-SSL, depending on whatever protocol is in use.


1

After much searching I found out this is not just Wyvern but an issue or design feature in EE3. Developers need to add what their fieldtype compatibility is but not all of them have. This post describes the same issue with wygwam. https://expressionengine.com/support/bugs/21302/field-type-not-changeable-after-creation You can follow the same instructions and ...


1

Changing the fieldtype won't strip out data. Internally Wyvern, Wygwam, or any WYSIWYG editor just saves the data to a normal text column in the database. Changing the type to textarea just ensures that it contains the same blob of text that contains html, but nothing enacts on it or tries to modify it. So in short, yes you are safe in doing this. Always ...


1

Wyvern has a similar config file, you can add this line to it: config.disallowedContent = 'img{width,height}';


1

Hrmm. I wouldn't recommend changing core files. :p I feel like being awful today. Here's a PHP solution (turn template on PHP output): <?php echo preg_replace("/height\=\\"(\d*)\\" width=\"(\d*)\\"/", 'style="height:$1px; width:$2px;"', '{wyvern_image_field}'); ?> This regex will turn <img src="blat.gif" height="200" width="200"> to <img ...


1

Stop the presses, I don't see in your question if you followed the documented process over at bold minded here : https://boldminded.com/add-ons/wyvern/documentation (all my quotes below are from this site) So Step one (which I assume you've done as you can see it in the field list) : Adding 3rd Party Plugins (after version 1.2.7) Place your ...


1

It seems that you may have renamed the /system directory and/or admin.php to something else (which is a great idea). If so, you need to change the $system_path variable to be updated in all three of these locations: /index.php /admin.php (or renamed version) /system/index.php (or renamed version) Example: If you renamed /system to /cantguessthis you would ...


1

Try just: <div class="form-element-wrapper" id="mission-container"> <label for="mission">Mission</label> {field:mission} </div> {field:mission} will render the textarea for you.


1

So, here's how this was fixed: {exp:channel:form channel="your_channel"} <div class="form-element-wrapper" id="custom-field-container"> <label for="custom_field">Custom Field Label</label> {field:custom_field} </div> etc etc {/exp:channel:form} :-)


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