Magic Fields 1.3 was released

Magic Fields 1.3 is out, and come with a good number of new features and less bugs.

I’m going to speak a little about the new features.

New Features:

New type of Custom field called “Related Type”.

In Magic Fields 1.3 exists a new custom field type called “Related Type” with this type of field we can make relation between write panels. For example if we are working in our portfolio and we has a write panel called “clients” and a write panel called “services” we can now related some client with many posts “services”, this new field open a new field of ideas and possibilities.

Adding multimedia buttons to the multiline custom field.

Now is more easy add images and files in the multiline custom field, was added more buttons for doing this more easily.

Adding a new engine for make the validations.

this is the most exciting new feature of this release, was rewrote the “engine” for make validations in the custom fields, now Magic Fields use this jquery library for make the validations, with this in the next version will be add a new rules of validations for the custom fields!

Finish the support for the i18n.

Soon we will explain how translate Magic Fields to your language.

Removing obsolete Code.

One of the things to we personally enjoy is make Magic Fields more lighter, We continue removing and refactoring the code for make the footprint of Magic Fields more smaller. In this release was removed a repeated libraries of jquery.js and ui.jquery.js.

This project is made it in our free time and not has any company behind his development for that we are very grateful with the people to encourage us making donations for continue the development.

Thanks to:

  • Jens Wedin
  • Jan Ramroth
  • Eivind  Skjellum
  • Albert Ariza

And also we want say thanks to all the people to are helping us doing another kind of donations, like making patches for Magic Fields, reporting bugs and helping us giving support for others users and in general all who gave us any kind of feed back for this plugin.

And just for finish, you can found the documentation of Magic Fields here:
http://wiki.magicfields.org/
for now only in spanish, if you has a little free time help us translating the documentation from spanish to your language.

[UPDATE] Was reported a critical bug when is created a new page in a write panel,  we are going to release a new  tag with this fixed (version 1.3.1)  thanks for the report!
2_256x256
Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • BarraPunto
  • LinkedIn
  • Meneame
  • Reddit
  • Slashdot
  • Tumblr

86 Responses to “Magic Fields 1.3 was released”

  1. terryteo says:

    heya
    i have a feature request:
    if possible, could you create an option to have a layer of security for files uploaded through magic fields.

    this could probably be as easy as having a checkbox next to the upload button, which if ticked sends the file to a separate folder. then users could add a level of security to that folder.

    what do you think?

    thanks!

  2. Hendrik says:

    Hello,
    thank you for this awesome plugin!
    But i have error message on my backend -.-
    “Warning: Cannot modify header information – headers already sent by (output started at XXXX\wp-content\plugins\magic-fields\RCCWP_WritePostPage.php:2) in XXXXX\wordpress\wp-includes\classes.php on line 1586″

    I can’t delete or publish posts. Whats wrong? Please help!

    Greetz and thanks!
    Hendrik

  3. Rob says:

    Hi Guys i’m having some strange issues with with magic fields and wp 2.9.1

  4. shawn says:

    for image/audio/video uploads would it be possible to call the wp-gallery function for storing images instead of using the separate uploader?

    The reason I ask, is doing it this way, if a user wants to use the same image in many places, they have to upload multiple copies of it. Where if we used the wp-gallery function, then the user would have an interface they are used to using, and could select images or files already uploaded to their server.

    This also would really help those of us using wordpress mu, as the users upload directory is sorted out really nice, and allows me to separate the directories onto separate servers without issues.

  5. shawn says:

    tried installing 1.3 onto my wordpress-mu 2.8.5 site just now.

    I keep getting error:
    Magic Fields is not ready yet. must create the following folders (and must chmod 777):
    wp-content/plugins/magic-fields/blogs.dir/5/files_mf/phpthumbcache/
    wp-content/plugins/magic-fields/blogs.dir/5/files_mf/

    I can say without any doubt that I have set the blogs.dir to -R 777
    drwxrwxrwx 2 httpd httpd 4096 Jan 11 16:42 phpthumbcache
    drwxrwxrwx 3 httpd httpd 4096 Jan 11 16:42 files_mf

    No matter what I tried I could not get magic-fields to create those folders, so I did it manually and then did the chmod to 777 on both directories.

    I think something is wrong here, but not sure what to try next.

  6. shawn says:

    I figured out the problem but am unsure of what file to edit in order to fix the issue.

    The problem is that magicfields is creating the upload directory in the absolute wrong place.

    example:
    /wp-content/plugins/magic-fields/blogs.dir/5/files_mf/phpthumbcache/

    It should be:
    /wp-content/blogs.dir/5/files_mf/phpthumbcache/

    I hope that makes sense. There is no way you would ever want to store the data in the plugins directory for magicfields when wordpress already creates the storage directories in the ‘right’ place when using wordpress-mu.

    I will manually create those folders for now, so that I can further test magicfields with wordpress-mu, but I do NOT want to keep the uploads directory there.

    hope it helps someone

  7. shawn says:

    well I created the directories as specified, and the error went away. However the plugin does nothing. When I go in to create a new panel, it does not give me a type of input box, nor does it save the panel.

    Honestly as it is, magicfields does not seem to work at all for me in wpmu.
    (I am willing to send you login info if you want to see the issues)

  8. Gnuget says:

    Hi shawn,

    For use magic fields in wordpress MU you need install magic fields as a wordpress mu plugin more info here

    http://groups.google.com/group/magic-fields/browse_thread/thread/3c4371a78d661e05/aaf286105da18d54?lnk=gst&q=wordpress+mu#aaf286105da18d54

    David.

  9. Trey says:

    Is there a fix for the multiline text box line breaks being removed when using this custom field? I have the option selected to hide the multiline formatting buttons and just want a basic text box but the text doesn’t format correctly…it just keeps running into my right sidebar widgets.

  10. cyberdelic says:

    What is the proper usage for the Related Type. When attempting to display the content of that field using . It is returning a numeric value. What would be the proper way to display the associated text value? Thanks for your help and Magic Fields Rocks!!

  11. hunk says:

    Hi cyberdelik the custom field Related type, could you do that is related to the current post, something like this http://gist.github.com/276844

  12. Brandon Dove says:

    @trey try using this:

    $meta_values = get_post_custom($post->ID);
    $post_content = apply_filters('the_content', $meta_values['insert_custom_field_name_here'][0]);

    That should add line breaks to the multiline output.

  13. Trey says:

    Brandon,

    Can you give a little more explanation on where that snippet should be entered…I’m assuming it goes near line 404 in get-custom.php…please help…thanks!

    Trey

  14. Brandon Dove says:

    @trey – you would put that inside the loop before you want to display the text in the multiline textbox. I didn’t mention this before, but in order to output the formatted content, you’d need to append the following to my previous code snippit:

    echo $post_content;
  15. Trey says:

    Brandon,

    I implemented the code as you suggested but it still does not format correctly(it does display, so at least I know the code works)…same issue…problem with my theme?

    Trey

  16. Brandon Dove says:

    @trey – I’ll be happy to look at it if you’d like. Drop me a line over at http://www.think-press.com with some details and I’ll check it out.

  17. Peter says:

    Hi there,

    I’ve installed MagicFields in my WordPress and I’m giving it a go. Created what I think to be a group and called it book. Under book there are several fields. With this configuration I created a new post book. On my theme I added inside a loop this code:

    $elementos = get_group (“book”);
    foreach($elementos as $elemento){
    echo pr($elemento);
    print_r($elemento);
    }

    Unfortunately it gives me a php error:
    Warning: Invalid argument supplied for foreach() in …/wp-content/themes/default/single.php on line 34

    I can call all fields independently and use other methods that don’t give me error. This one seems to have a problem.

    Any ideas?
    Regards

  18. Peter says:

    Hi there,

    I’ve just realized that the group must be several fields created inside a specific group (+ Create a Group button). I thought get_group would just provide me all fields grouped.

    regards

  19. leland says:

    whats coming up for magicfields?

  20. demetrius says:

    has anyone gotten magic fields to work on wordpress mu 2.9.1.1 (to be specific) along side buddypress?

Leave a Reply

Stop SOPA