taxonomy should get a dropdown

I agree that it would be useful in some cases to have a dropdown instead of an autosuggest, but not in all cases.

Therefore, there needs to be a way for the user to choose which taxonomy should get a dropdown and which should get an autosuggest field.

The development version (2.0-alpha) of the plugin now uses a dropdown to edit terms in hierarchical taxonomies.

If your taxonomy is not hierarchical, you can force the dropdown with a few lines of code:

function fee_force_dropdown( $data ) {
  if ( isset( $data['taxonomy'] ) && 'taxonomy_name' == $data['taxonomy'] )
    $data['type'] = 'termselect';

  return $data;
}
add_filter( 'front_end_editor_wrap', 'fee_force_dropdown' );

Obviously, replace ‘taxonomy_name’ with your taxonomy.

Hello Scribu,
great, code working very fine. Thanks! Only a problem, custom taxonomy is popolated only from values that have associated post. In others words, values that are not actives (without post/posts) are not presents when I edit taxonomy. Is it possible populate with all values?

Done. You should see it if you re-download the development version in about 15 minutes.

Doesn’t work

Warning: require(…./wp-content/plugins/front-end-editor/scb/load.php) [function.require]: failed to open stream: No such file or directory in ,,,,/wp-content/plugins/front-end-editor/front-end-editor.php on line 30

Fatal error: require() [function.require]: Failed opening required ‘…./wp-content/plugins/front-end-editor/scb/load.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in …./wp-content/plugins/front-end-editor/front-end-editor.php on line 30

version 1.9.3

btw if you manage to make taxonomy terms editable as drop-down, then there are no categories needed ??

thanks 2046

Make sure you uploaded all the files.

Also, you won’t see the dropdowns in version 1.9.3, but in 2.0-alpha, linked before.

that’s awesome ??

great, thanks Scribu, now its very good.
Only a strange issues in page: check this screenshot, with ufficial version of this plugin, only elements are on same row, now in 3 different rows.
Check also this screenshot, text (word “appartamento”) has issues about align.

With version 1.9.3 there is this <span data-type=”textarea”, in version 2.0-alpha, <div data-type=”textarea”.

Yes, it’s a div, but it has the fee-inline class, which sets display:inline, so it should look the same.

its not look same. this is class attribute: screenshot. Which file contains setting about div or span?

I’ve reverted the dev version (2.0-alpha1) to spans for inline elements.

If you’re still having problems, please paste the entire span or div tag:

<span ...all the attributes... >

Im still having problems, this is code
<div data-type="textarea" data-post_id="264" data-key="richiesta_prezzo" data-values="[]" data-i="0" class="fee-field fee-filter-post_meta">800000</div>

Ah, I see. Version 1.9.3 actually had incorrect behaviour.

The thinking goes like this: If you need a textarea to edit that element, it’s probably a block element, so it should go in a div.

Replace:

<?php editable_post_meta( get_the_ID(), 'your_key', 'textarea' ); ?>

with

<?php editable_post_meta( get_the_ID(), 'your_key', 'input' ); ?>

and it should look alright.

I have done, but the issue is caused for div element:
<div data-type="input" data-post_id="264" data-key="spese_condominiali_annue" data-values="[]" data-i="0" class="fee-field fee-filter-post_meta fee-inline" style="display: block; ">1100</div>
To resolve, should be:
<span data-type="input" data-post_id="264" data-key="spese_condominiali_annue" data-values="[]" data-i="0" class="fee-field fee-filter-post_meta fee-inline" style="display: block; ">1100</div>
Is there a way to replace <div… with <span… ?