9

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.


9

The problem is that many developers don't know how to write compliant SQL statements - they're software developers who find themselves also filling the role of database developers. This problem crops up in many addons and was recently fixed in EE core code. For Assets v2.6 Change line 615 of ft.assets.php FROM: $sql = "SELECT DISTINCT a.source_type, a....


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


7

Here's how to upgrade an existing EE install with P&T fieldtypes. After upgrading EE you'll get this error when visiting the modules section: Fatal error: Class PT_Fieldtype contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (EE_Fieldtype::display_field) in /third_party/pt_field_pack/pt_fieldtype.php ...


5

That’s an error in the documentation, and we’ll get that fixed. :child_ids only supports filtering entries with the following parameters: var_id var element_id field_id field col_id col row_id child_id parent_id If you need anything else, and you should just use a tag pair: {event_related_media limit="2" status="Archived" channel="video" ...


5

Unfortunately, there wasn't a good answer in getting this to work with Matrix. Everything I tried still resulted in a page load time of 14.6 - 17.2 seconds. I worked with EllisLab all day Friday from like 2-9. We spent the day debugging templates, analyzing output, checking for red flags, etc.. I completely rebuilt the template using the native Grid field ...


5

So far I've discovered and fixed one case and will add more here if discovered. File: mod.playa.php Line: 550 FROM $sql = 'SELECT DISTINCT(rel.child_entry_id) AS entry_id TO $sql = 'SELECT DISTINCT rel.child_entry_id AS entry_id, rel.parent_entry_id, rel.parent_field_id, rel.parent_row_id, rel.parent_col_id, rel.parent_var_id, rel.rel_order


4

P&T switch has moved into a new bundle of old dive bar addons called Field Pack as of August 2013. You should update to that and everything will be working fine. Updating is simple, but do read the docs. http://docs.pixelandtonic.com/fieldpack/installation.html#updating-from-the-old-dive-bar-fieldtypes


4

You can use Matrix's search parameter to return only the rows of interest: {report_articles search:report_type="=Land"} Show the Land data {/report_articles}


3

Looks like a variable name conflict. You can use "var_prefix" when this happens. Try something like this: {exp:playa:children channel="recipe" entry_id="{entry_id}" field="similar_recipes" var_prefix="related" } {related:title} {/exp:playa:children} http://docs.pixelandtonic.com/playa/templating/module/children.html


3

I believe to do so, you would need to create a Custom Style Set for Wygwam. See the Wygwam Docs over a Pixel & Tonic. Though, I recommend creating a class instead of an id. Since someone will most likely add more than one media embed sometime in the future. Additionally, this StackExchange post deals with editing the Wygwam .js for custom sets.


3

I removed the'&#' characters from the dropdown options 👀 : View has now become x1F440; : View and added those characters to my template output instead. &#{standard_icon} The field is storing the value as expected and the icon is being output fine in the template.


3

Looks like you need :selected tag For use in conditionals; returns whether or not a particular option is selected. {if '{my_checkboxes_field:selected option="kittens"}' == '0'} <p>No Kittens :'(</p> {/if}


3

I've done it before. Take a look at the display_field method of ft.wygwam.php. You'll see that it's fairly simple to instantiate a WYGWAM field. A few calls to the Wygwam_Helper class to load the JS/CSS. There are also some helpers for properly formatting the data. You'll need a textarea with an id, and also the ID number of a WYGWAM config. I don't want to ...


3

So, a bright (Latvian) mind was kind enough to look into this. It seems the problem lies with ExpressionEngine code on this one. Embeds or Stash will work just fine but you can also patch EE as follow: File: system/expressionengine/modules/channel/libraries/channel_form/Channel_form_lib.php Method: replace_tag Find this: ee()->api_channel_fields->...


3

Ugh, wasn't logged in properly.... They sent me this on email support: If you could just replace line 814 in Assets_lib.php file with if (!(count($full_folder_list) == 1 && reset($full_folder_list) == ":any:")) you should be fine :)


3

There is only one correct syntax style: {companies_type:label}. If it's not working you might have changed your options after saving an entry. So the stored value is not matching any options anymore and thus resulting an empty value for {companies_type:label} and {companies_type}.


3

This is due to a change in how EE validates Channel Form fields (not sure when this was implemented). When you upload a file via a file field, that field name isn't actually populated in the $_POST array, so EE doesn't know it's been submitted, and hence won't call the fieldtype which owns that field. It works around this issue for native File fields inside ...


3

Did you just upload the folders and have them over write the existing ones? If so, this doesn't always work well, especially with a large addon like WYGWAM. Try, deleting the folders on the server and uploading them fresh.


3

I think the best way achieve this is to do by adding CSS. For that you just need to create one class pipe containing the + sign (either with an image or with color). Then put that pipe class on respected rows in Matrix. This way you can manage it very easily. span.pipe:before {content:" + ";} span.pipe:first-child:before {display: none;}


2

It turns out that you must have at least one upload location (for that site, if MSM is enabled) present in order to set the upload location in Wygwam. For instance, I just performed a migration of Wygwam (2.7.1) data from using the native EE uploads to using Assets (2.2.2). Initially, I moved all of the images from the native upload location to an assets ...


2

See this post for info Matrix (2.5.8) update database error Sounds like it is the same or similar problem. I had this once and the info there was enough to go into the database and sort out the issue.


2

In Assets 2.2.2 you can't create folders that begin with an underscore. Until we release 2.2.3 it is possible to rename a folder to a name that begins with an underscore, but this is a bad idea, as you'll be unable to index these files. As for the reason why: 1) Since Assets now supports multiple source types, to eliminate the need for querying S3 and other ...


2

EDIT: Please see the accepted answer above from Dylan as an approach for handling this type of functionality. nonprofit_tech's suggestion to try using a custom style set does work, but it involves a two-step process: the content administrator must first add the custom wrapper from the style set dropdown, and then embed the media via the toolbar's media ...


2

I had this same problem and after some head scratching, found that for some reason the other member groups didn't have file upload priviledges. So, check: Content -> Files -> File Upload Preferences -> Edit (select at least one location) And check that at least one upload location allows the Member Groups to upload files.


2

Yeah, you've got a mess on your hands. Try this no add-on method. If it doesn't help you out, notacouch's suggestion to use IfElse should be helpful. {if entry_id == "20" && cf_product_options:total_rows > "0"} <hr class="soften"> <h2>Configuration Options</h2> <table class="table table-striped table-bordered ...


2

I believe any date field in EE should have the format parameter available. Correct syntax in this case would be something like {field:job_timings format="%d-%m-%Y"}.


2

We just released Wygwam 3.3 which fixes compatibility issues with Internet Explorer 11.


2

You need to use pair tag for this: {gallery_items var_prefix="file"} {exp:ce_img:pair src="{file:url}" max_width="1080" itemprop="image"} <img data-original="{made_url}" class="lazyload" alt="{file:alt_text}" width="{width}" height="{height}" /> {/exp:ce_img:pair} {/gallery_items}


2

The :all_options tag pair was actually removed removed two years ago, well before Field Pack 2.0 came out. We removed it because EE doesn’t parse tags for fields that don’t have any data; it just removes them. And 99% of the time, people used the :all_options tag pair in cases where they would expect the options to appear regardless of whether a checkbox ...


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