Magic Fields 1.2 was released

Magic Fields logo

Magic Fields logo

Magic fields 1.2 is out and this is our first release with new features.

In this entry we will speak a little about to what is new in this version, we  hope to you enjoy  this new release :)

New Features.

Condense Menu mode.

In our first release a lot of people ask us for add the “condense” feature made by Doc4 (http://bit.ly/8Gy9q) and now this feature is part of the Magic Fields.

condense-1

And we added a little improvement for this new mode, when the user  see the “edit” page while has the “condense menu”  mode active  will be appear a new column with the name of which write panel belongs the post.

new_column

New Functions for get data in the frontend.

One of the weak points of the last version was the performance. For get the values of a Duplicate group was neccesary did a bunch of calls of the “get” function. So in this new version was added new ways to get the data.

get_field_duplicate: When we has a duplicate field with many values now we can get the data in this way:

In this image we has a duplicate field with some values:

duplicate_custom_field

And in the theme we can get this values using this:
And we will get this result: list get_group: In a duplicate group with many fields like this: groups_duplicates And in the theme we can get this values using this:

And we will get this result:

colors

gen_image: Now  is possible create new thumbs of our images dynamically   for example if we has a image custom field.

gen_image

We can do something like this:

gen_image1

Using this code:

Add a new option for hide non-standart content in Post panel.

normally  in the edit page in the Post panel appears all the posts created with and without writepanels, with this option we can only display the posts created without write panels.

Tooltip feature.

Sometimes can be confused for the clients knows  for what is each custom field in the write panel now we can add a message and this will be appear as a tooltip in our custom field page.

tooltip_1

tooltip


We want say thanks.

In this last month many people help us to improve   Magic Fields and we want say thanks to them :)

  • Jeff Minard: Helped us adding new features and fixing bugs.
  • Michael Bayard: For the Magics Field Logo.
  • Carlos Mendoza: For the new help text feature.
  • Doc4: For the Condense Menu mode.
  • Sascha Schwartz:  Donation
  • Dan Armstrong: Donation

Giving Support to WordPress MU.

In this  release we wanted add support to WordPress MU unfortunately we can’t finish to test in deep the support for WordPress Mu, but we has a beta version, if you has time to help us, please download this package and test it :)

Any  bug to you found it let us know in the  support group.

You can download the beta version here: Magicfields-wpmu-beta

Be Sociable, Share!

29 responses to “Magic Fields 1.2 was released”

  1. terryteo says:

    hi there, noticed a small bug with the date functions.
    line 108 of RCCWP_CustomFieldPage.php

    option value=”Y-d-m”

    should be:

    option value=”Y-m-d”

  2. Gnuget says:

    Hi terryteo.

    I will add this fix in the next release.

    Thanks

  3. terryteo says:

    awesome. if it is possible for the date select to be improved to include a time selector, that would be a huge bonus. also, it would be good to have the option to store the date and time as ISO 8601 which (only works in php5 though). ISO date has the format character of “c”.
    thanks again!

  4. acebone says:

    Hi! Looks great!

    One question though – I have created a page-write panel called Curriculum Vitae.

    It holds a group cvEntry (duplicatable)

    cvEntry has two fields: cvEntryYear (custom dropdown) and cvEntryText (multi-line text), both are non-duplicatable

    When I try to get the values in my template – i use this code:

    $fields = get_group(‘cvEntry’);

    foreach($fields as $field){
    echo $field[‘field1’][1].” —-> “.$field[‘field2’][1].””;
    }

    I get “Warning: Invalid argument supplied for foreach() etc…”

    When I try to echo or print_r $fields, it seems that $fields is empty.

    I am certain that it is not an issue with capitalization – I doublechecked that.

    I am using MF 1.3.1 downloaded from within the WordPress plug-in manager. and WordPress 2.9.1

    Any ideas?

  5. acebone says:

    Well – there is nothing wrong with the get_group function.

    When I created the writepanel, I started of with it being of type ‘post’, and it should have been a page, so I corrected it.

    After that some weird things happened with the ‘slug’ – it kept adding 1 (curriculum-vitae-1,curriculum-vitae-2,curriculum-vitae-3 etc…)

    The reason that get_group didn’t work is that while the writepanel was attached to post->id 12, all slugs pointed to post->id 6. No wonder get_group couldn’t find any panels/fields in 6, when they were all in 12.

    I am sorry that I cannot reproduce the exact steps to trigger this behaviour. I made a dump of the DB, that I’d be happy to send to you if it would be any help.

  6. Offminded says:

    Hey great plugin,

    It was really useful so far, but there’s this problem I’ve been trying to find a workaround. Is there a way to use get_field_duplicate function with “Related Type” dropdown fields?

    I am using some “related type” fields which can be duplicated, and they are duplicated in editor, and I want to use them in an Array but it doesn’t seem to return an array. I’m using code below to test it:

    $related_entry = get_field_duplicate(‘related_fields’);
    if (is_array($related_entry)){
    echo ‘it is array’;
    } else {
    echo ‘it is not array’;
    }

    Any ideas?

  7. Julie says:

    Hey great plugin,

    It was really useful so far, but there’s this problem I’ve been trying to find a workaround. Is there a way to use get_field_duplicate function with “Related Type” dropdown fields?

    I am using some “related type” fields which can be duplicated, and they are duplicated in editor, and I want to use them in an Array but it doesn’t seem to return an array. I’m using code below to test it:

    $related_entry = get_field_duplicate(‘related_fields’);
    if (is_array($related_entry)){
    echo ‘it is array’;
    } else {
    echo ‘it is not array’;
    }

    Any ideas?

  8. Troy says:

    Can you put a duplicate field inside a duplicate group. If so what would the code look like?