12

Sounds like the field's settings have gotten mixed up at some point. I'd try switching the field to "XHTML" formatting, and select the option to "Update all existing channel entries with your new formatting choice?". Once that's done, then switch back to "None" formatting and update all existing again. Hopefully that will resolve for you.


5

Use the session cache: if (ee()->session->cache(__CLASS__, __FUNCTION__) === FALSE) { ee()->cp->add_to_head('/path/to/foo.css'); ee()->session->set_cache(__CLASS__, __FUNCTION__, TRUE); } Your code will only run once per page load.


5

For times where the Channel module is overkill, or the random bits of editable content don't really fit the Channel mould, Low Variables is really great. It has a lot of added features beyond just making global variables easily (and safely) editable by end users. Some of the big benefits are text formatting options, custom content types for the global ...


5

You are hitting the limits of InnoDB. It might work to change your table to the MyISAM engine (backup before changing this), as the limits of MyISAM are larger compared to InnoDB. Note that this can cause an performance hit as table locking acts different on MyISAM. You can also replace all VARCHAR fields (with more than 10 characters) with a TEXT field. ...


5

This was driving me insane but I've figured it out. You need to edit the $entry object (1st parameter of the function) in order for this to work. You can, however, use the 2nd parameter, $values, for easy reading of the data. public function before_channel_entry_save( $entry, $values ) { // Set value for specific field name $entry->setProperty( '...


4

You should not lose any data which already exists in your fields when changing field types - but if you have anything but a UNIX timestamp stored in the existing text field, the Date fieldtype won't know what to do with the data. UPDATE: To update your existing fields from your current format (5/14/2013) to a timestamp for use with the Date fieldtype, put ...


4

There are a couple of bugs with publish layouts that have popped up in 2.7.1. Here's a link to one that sounds like it might be related and contains a fix file to download and apply: https://support.ellislab.com/bugs/detail/19738 Let us know if that fix works for your issue as well.


4

Any time i've used it P&T fields so far i've gone with this syntax: {field:preferred_position} I haven't specifically used checkboxes, but I think its worth a shot.


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

you can open file expressionengine/modules/channel/mod.channel.php and check function entries() you can use Channel-Data lib from Justin Kimbrell to simplify access to channel data. example $entries = $this->EE->channel_data->get_channel_entries($channel_id, array( 'select' => array('*'), 'where' => array('...


4

If you need to do this from the template you could use a plugin like this one: http://devot-ee.com/add-ons/create-url-title If you need to do it directly to the DB please update us so we can give you that solution as well. Note: CE String also has a custom method called url_title which will do the same thing but, it's not a free add-on.


3

Not natively but you could throw a little JS into the field instructions as per this question. <script> $(function(){ if (document.location.href.indexOf("entry_id") == -1) { // if it's a new entry var field = $("#field_id_15"); if (field.val() == "") { field.val("Sydney"); } } }); </script> Obviously just replace that ...


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

The first thing I would ask is do you really need a fieldgroup for each product channel? Multiple channels can share the same fieldgroup and you can use publish layouts to hide the fields that are not relevant to a particular product. Using the same fieldgroup will also force you to generalise the fields you use which can be a good thing for rationalising ...


3

Go to this field via Admin > Channel Administration > Channel Fields > Group > Field and switch the formatting back to XHTML confirm and then back again to none. When switching EE should show a checkbox before confirming asking if you want existing fields to be reformatted. Check this. Alternatively keep as XHTML in EE and use a plugin to alter the rendered ...


3

As folks mention above, no custom development is needed here. Just use the native Grid fieldtype with two columns - one using the File fieldtype (called, say, file), and the other using the Text fieldtype (called, say, url). Then, in your template: {my_grid_field} {if my_grid_field:file}<a href="{my_grid_field:file}">Download this file</a>{/...


3

This is what the var_prefix="" parameter is for. Update your code like this. {exp:channel:entries set="prod" dynamic="no" disable="pagination"} ... {exp:playa:parents channel="api" field="cf_apis_related_product" var_prefix="api"} <ul class="dropdown"> <li><a href="{path='{PROD_CHANNEL_url_title}/docs/{api:url_title}'}">{...


3

Yes, all custom fields for each entry you call via channel:entries are loaded by the template engine and ready to be parsed, so your latter idea is a good one.


3

The shortcut tags provide a quick and easy way to add the field to the page but by default this will output as an input field. You do however have full control over the HTML elements and an output any form component you wish to use by simply ensuring the name attribute matches the name of the field. For example: <div class="control-group {if error:...


3

For my specific case, it appears to be addons such as Matrix and Assets by Pixel & Tonic that are causing this. By uninstalling the addons I was able to get rid of this error.


3

The error has been confirmed as a bug in EE 2.8. Bug tracker: https://support.ellislab.com/bugs/detail/20165 The issue will be fixed in the next release, and a patch has been posted to the bug tracker for any who need it.


3

Unfortunately, it's not currently possible (as of Content Elements 1.6.10) to rename a Content Element. The only workaround is to delete an element and create a new one. I've made a feature request for this to be added though.


3

Easy, I'd create a grid field with Date | Time | Location | Price. For ease of management I'd create a separate channel for locations (manage all locations separately to stop typos and misspellings etc) and have them as relationships in the grids 'location' column. This will allow you to have detailed info for locations if required. Looping through grid ...


3

You are using this inside a channel entry loop, correct? If not, you need to be. And you might also try using the other field segements: {exp:channel:entries channel="my_channel_with_select_field" limit="1" dynamic="no" entry_id="the_entry_id_of_the_entry_i_want_to_output"} {select_field_name} Field value : {select_field_name:value}...


3

You may be using the incorrect field name. You can't access it via its short name, it has to be by it's field_id. Here is an example of how I do something like this: // these are usually set at the top of my add-on, function, whatever, // for reference through out this PHP file, and also in case different site // instances (staging, dev, whatever) happen ...


2

If you are manually editing the options of the custom field, why not replace <p>Description One.</p> etc with low variables? (Separate text fields, not a matrix field) {if custom_field =="Option One"}{lv_description_one}{/if}


2

You can use put the code for fetching member data within embedded template and can pass member id as embed variable like: {embed="temp_grp/temp_name" member_id="{member_id}"} Within the template "temp_grp/temp_name" put the tag of custom profile data: like: {exp:member:custom_profile_data member_id="{embed:member_id}"}{member_code}{/exp:member:...


2

It seems that no member group is selected as "Include Members in PUBLISH page multi-author list?". Go to Control Panel -> Members -> Member Groups. Click on "Edit Group" next to Super Admin. Now make sure the "Include Members in PUBLISH page multi-author list?" is "Yes".


2

MX Select Plus is a great fieldtype–you can choose either to populate the menu with plain text or write a SQL query. It's pretty slick!


2

If I add a new field, will it be available for all entries in this channel (new and existing) and can users update their entry accordingly Yes, any new custom fields added to that channel will show up for new & existing entries. Your members will be able to update fine. If you change a existing field to a new fieldtype (ie. text input ==> Matrix), ...


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