I keep running into an issue with the data saving in the wysiwyg editor. I’m running v1.2 with WP 4.1. The issue involves the plugin altering the inputted data by changing the parsing of the html.
Basically, when I put html into the visual editor, everything is fine. I can go back and forth between the text and visual editors and the content stays correct. However, when I save the page the content in the visual editor shows html tags, while the text editor shows the unicode entities for the “<” and “>”.
Example:
Visual: test <strong>content</strong>
Text: test <strong>content</strong>
(semi-colons removed so that this will display on this page)
The actual meta values (in the database) remain correct, it is only the admin that displays incorrectly. As such, the issues does not affect the front end output, but it makes editing the taxonomy meta quite annoying. Any suggestions on what to do here?
Thank you!
]]>Rilwis,
I am a big fan and user of the Meta Box plugin and for my current project need to add custom meta to the categories as well so was thrilled to find that you had written a plugin for this as well. Unfortunately I need some the great field types that you have in the Meta Box plugin in the taxonomy one as well. Specifically looking to use image_advanced and plupload_image. Is there any way that I can either:
1) Add these in?
2) Hook into the available fields from Meta Box (as this is installed on the same site)?
All the best,
Will
]]>I have this piece of code that displays some text conditional upon a term description. If the term doesn’t have a description then some alternate text is displayed
<?php $description = get_queried_object()->description; if ( ! empty( $description ) ) : ?>
<?php echo $description; ?>
<?php else: ?>
no term description
<?php endif; ?>I’d like to be able to do the same with this plugin. This is the code use to display my custom term meta
<?php $meta = get_option('suburbs1');
if (empty($meta)) $meta = array();
if (!is_array($meta)) $meta = (array) $meta;
$meta = isset($meta[get_queried_object_id()]) ? $meta[get_queried_object_id()] : array();
$value = $meta['postcode1'];
echo $value; ?>Thanks for your help
]]>For anyone trying to figure this out…
<?php $meta = get_option('meta_id');
if (empty($meta)) $meta = array();
if (!is_array($meta)) $meta = (array) $meta;
$meta = isset($meta[get_queried_object_id()]) ? $meta[get_queried_object_id()] : array();
$value = $meta['field_id'];
echo $value; // if you want to show ?>Hi,
Do you know how can I make the new taxonomy fields translateble using WPML?
thanx.
]]>Is there a way for me add an edit image link next to the uploaded image as seen in the metabox plugin ->
%s
I prolly could almost duplicate the select image field from the taxonomy-meta.php file, but maybe you know a better way.
thanks!
]]>I created a custom meta field of type checkbox and id: is_sticky, like this:
$meta_sections[] = array(
'title' => 'Sticky', // section title
'taxonomies' => array('tvr_amenity'), // list of taxonomies. Default is array('category', 'post_tag'). Optional
'id' => 'sticky', // ID of each section, will be the option name
'fields' => array( // List of meta fields
array(
'name' => 'Show in home filters',
'id' => 'sticky',
'type' => 'checkbox',
),
),
);Now I’m trying to get all the taxonomies that has this value checked, like this:
$types = $types = get_terms( 'tvr_amenity', array(
'parent' => '0',
'hide_empty' => 1,
'sticky' => 1
) );But the filter is ignored (all the parent taxonomies are shown), it returns the exact same than:
$types = $types = get_terms( 'tvr_amenity', array(
'parent' => '0',
'hide_empty' => 1
) );Any idea what I’m missing, here?
]]>After installing the Taxonomy Meta plugin, 2 functions are broken on all taxonomy admin pages:
– the admin dropdown menus (on the left)
– the Quick Edit function
Great plugin anyway. Thank you so much for developping it !
]]>PHP Notice: Undefined index: tag_ID
I get this notice come up whenever I visit the main taxonomy page. Doesn’t appear when I actually edit an existing term.
]]>Warning: Parameter 1 to RW_Taxonomy_Meta::save_field_wysiwyg() expected to be a reference, value given in …\wp-content\plugins\taxonomy-meta\taxonomy-meta.php on line 518
Warning: Parameter 1 to RW_Taxonomy_Meta::save_field_file() expected to be a reference, value given in …\wp-content\plugins\taxonomy-meta\taxonomy-meta.php on line 518
Warning: Cannot modify header information – headers already sent by (output started at …\wp-content\plugins\taxonomy-meta\taxonomy-meta.php:518) in …\wp-includes\pluggable.php on line 876
This messages appears, when i save category. Localhost.
]]>Hello,
I would like to ask where in database this plugin will store meta fields.
Does it create a new meta_taxonomies table?
It’s have a bug, that loads styles from theme) so my wordpress admins was #red(as it was in style.css from my theme). I commented 309 line wp_enqueue_scripts( 'jquery' ); to solve this.
I have some substantial criticism of the data retrieval API you provide. In fact, my point is that you provide none. For a piece of software claimed to be “written in OOP”, not only is there no OO data retrieval API provided, but there is not even any data abstraction. You just happily hand over the internal representation.
Firstly, in order to just find the value of this meta field for this term of this taxonomy, one has to retrieve the whole “database” for the <b>meta section</b> that contains the field. This is the first big problem: “meta sections” are just groupings of widgets in the data definition UI, and the programmer querying the data shouldn’t even have to remember which field belongs to which section. A good retrieval API would completely hide this.
Then one has to explicitly perform two sanity checks and normalization (the two if… lines in the examples). The result is then keyed with the term ID, and finally with the field ID, with necessary isset checks along the way. Nowhere does the taxonomy ID come into play, and the reason why it still works in spite of that is because term IDs are globally unique, so the term ID implies the taxonomy. This is however merely a side effect of how terms and taxonomies are represented, and the API should not expose this.
All in all, a simple data retrieval requries 5 lines of code for what should be just a single API call:
get_tax_meta($term_id,'my_field','my_taxonomy');
I’m confused about where I define the sections. I see the file [taxonomy-meta-usage.php]. Am I meant to edit that file directly?
]]>