Hot answers tagged

3

I just found the answer. It is a bug: https://support.ellislab.com/bugs/detail/19732


3

If you are having issues with JS interactions in the control panel not working correctly after an EE upgrade, the first thing to try is to reupload your control panel theme folder.


3

Each entry in the fluid field stores the content of whatever fields are defined for that entry from the set of fields assigned to the fluid field. So for each entry in your channel you might have a different set of fields defined - unlike regular fields in EE, what fields appear within a fluid field for an entry are defined when the entry is created rather ...


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

Can you not just use the standard file field and set up a folder for backgrounds? Your client can then either select an already-uploaded image from the list of files, or upload a new one. You can restrict this field to one folder so there's no room for confusion and have it as a field in your pages channel. This way you don't have two separate strands to ...


2

Do you have 'Automatically turn URLs and email addresses into links?' set to 'no' in the channel's preferences?


2

You can try Allow EE Code {exp:channel:entries channel="my_channel"} {exp:allow_eecode} {my_field} {/exp:allow_eecode} {/exp:channel:entries}


2

Relationships are stored in exp_relationships - the exp_channel_data content for a relationship field is irrelevant. So your query would need to do a join between exp_channel_titles and exp_relationships.


2

There are are a number of options open to you: Edit the default member registration template in Design->Templates->Themes->Member Profile Templates Use an add-on like Freemember Create your own custom registration form


2

Finally managed to fix this issue. First of all, I suspected that the default field in the moblog config could be the culprit. So it became apparent that moblog only supports textarea and textfield by default. So the default field was empty in my moblog configuration. Editing the ExpressionEngine $default_config to include the following '...


2

This MySQL query should give you a list of fieldtypes which are not currently in use as Channel or Grid fields: SELECT name FROM exp_fieldtypes WHERE (SELECT COUNT(*) FROM exp_channel_fields WHERE field_type = name) = 0 AND (SELECT COUNT(*) FROM exp_grid_columns WHERE col_type = name) = 0


1

Yes. WB Category Select is a fieldtype that does just that. When you create a custom field of this type you can set the category group(s) and whether or not the user is allowed to select multiple categories. It's a very handy add-on and works great!


1

The Moblog module simply creates entries from emails. It is admittedly a bit finicky though. Can you verify that the entries are being created in your channel from the emails that you have sent? If so, then you simply output the entries using the {exp:channel:entries} tag pair, just like you would for any other channel entry.


1

Depends on your approach and what you want to display information wise. I built this map using Entry data which populates hidden DOM objects that are shown and hidden depending on the state clicked. The SVG maps are open source with each state marked with ID and classes, although I had to customise to fit Alaska and Islands. Easy enough to colourise and ...


1

No add-ons I'm aware of, as most deal with the initial display of categories and groups, rather than the editing page (e.g. Category Construct). But you could modify the language file for the admin interface and change the title: expressionengine/language/english/admin_content_lang.php line 604: 'category_image' => 'Category Image', '...


1

Needs to understand how flexible your solution should be, how often questions can change and how do you want to use answers in future. As you suggest, it can be just a fields: one question - one field. + it is fast to build and no additional costs - every time when you need to add/edit question - you need to create/edit EE field and edit template Create a ...


1

So there is no way to do this with the EE API. You need to use the Database class and use the insert function like so. ee()->db->insert( 'field_groups', array( 'site_id' => 1, 'group_name' => 'Group Name' ) ); $group_id = ee()->db->insert_id(); return $group_id;


1

Yes, it is possible. You just need to change field groups association in table exp_channel_fields. Make you db backup then run next code (u can even use SQL Manager from CP) UPDATE exp_channel_fields SET group_id = X WHERE group_id = Y After that you just need to update field group for second channel. You can do this manually or run next query UPDATE ...


1

You say you don't want to do this with a plugin but the fact is that it's the best way to do it. Not least because you can avoid the problem you have with Parse order. The plugin needs a single line of PHP In the constructor, and returns a number; public function __construct() { $this->EE =& get_instance(); return strlen($this->EE->...


1

You don't detail where you are trying to "push" the sender's name after you've pulled it. If you want to use it to set the entry Author, you can do that with the "User Authorization" override: http://ellislab.com/expressionengine/user-guide/add-ons/moblog/index.html#user-authorization Or you can push data into fields like this: http://ellislab.com/...


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

You need to prefix those IDs with field_id_, e.g., $old_field = 'field_id_51'; $new_field = 'field_id_217'; That should get the migration working. Note that you'll only need to load that code once in a single PHP-enabled template, and it should migrate all entries which have an image in the specified field (you mentioned "loading a few pages").


1

Matrix has a "row_count" variable you could use, something like this: {matrix_field} {if row_count == "1"} First row content {if:else} Remaining row content {/if} {/matrix_field}


1

Yes, you can do this using any FT which can retrieve data by query (for example SELECT+). But will be needed to save entry first after upload images to get it in select field. Other way is to create this field (simple select + little bit JS coding). But take attention on Penzizzle advice - way which you choose is looks little bit unusual.


1

Check the Channel Preferences for this Channel for the Automatically turn URLs and email addresses into links option. It sounds like you have it set to "Yes" and this is causing the malformed HTML. Control Panel Location: Admin > Channel Administration > Channels > Edit Preferences Documentation


1

It appears that logging off, clearing the cache and logging back in did the trick. I just needed to rebuild the publish layouts after that. I don't know what I did different this time, but it's working now.


1

First, just note that it's safe to assume that adding more memory / faster servers for both your EE/Apache and MySQL will make things work better. 100k+ entries is enough to require more horsepower than a smaller site, but that generally can be addressed through reasonable upgrades. That said, I was just working on a site with 75k+ entries--and we were ...


1

You will have to run a query to get the data. You should be able to run the following against the member_group field of the member. SELECT exp_channels.channel_title, exp_channel_fields.field_label, exp_channel_fields.field_name, exp_channel_fields.field_type, exp_channel_member_groups.channel_id FROM exp_channels, exp_channel_fields, ...


1

Your issue is you cant use php inside the query tag sql. If you dont believe me, look at the source code for query module. From memory its in system/module/query. Remove this: BASE64_DECODE(field_settings) 'field_settings', field_label Now this works: {exp:query sql="Select CONCAT('field_id_',field_id) 'field_id', field_name, c.channel_name {!--...


1

You can try like this code example: {custom_fields} {if relationship AND field_name == 'gender'} <select id="{field_name}" name="{field_name}[data][]"> {options} <option value="{option_value}"{selected}>{option_name}</option> {/options} </select> {/if} {/custom_fields} ...


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