Magic Fields 2.0 Beta 1 is released

We are working in the new version of magic fields since a few months ago and we was thinking in make a commercial plugin from mf2 in fact we asked in the support forum about if some one was interested in paid for magic fields (you can read the thread here).

But, we will not continue with this plan, this weekend we took the desicion to preserve free (libre y gratis) the new release of magic fields.

And as part of this decision we are glad to say to Magic Fields 2.0 is ready to be tested.

A few new features of Magic Fields are:

  • Was COMPLETELY rewritten, now is more small, clean, smart, and more extensible.
  • Has a native support for WordPress post types.
  • include a UI for create your own taxonomies
  • The custom fields are not part of the core anymore this means to in the future we will possible to create a third party custom fields.

A few things to you need take in account is:

  • Magic Fields 2.0 is not backward compatible with magic fields 1.x.
  • MF2 require php 5 or newer.

if you want help us to test magic fields 2 get a copy of the development version from here:

https://github.com/magic-fields-team/Magic-Fields-2

Report any bug or issue here:

https://github.com/magic-fields-team/Magic-Fields-2/issues

And you can found the documentation for this new release here:

http://wiki.magicfields.org/doku.php?id=magic_fields_v2.0

And just for finish, if you are a happy user of magic fields, please consider make a donation, with your support and donations we can continue working on this plugin.

Have fun.

PD. For whom want a special support or have projects where you need help from us, soon we will offer a commercial support for the plugin.


MF + WPML!

A few weeks ago we started working in a plugin that will enable Magic Fields to work sealessly with WPML, since this plugin needed version 1.5 and it has allready been released, we have the pleasure to make it available to everyone.

This new plugin fixes compatibility issues that existed between Magic Fields and WPML, it also enables you to choose which custom fields will stay sincronized between languages so you will only have to translate those contents which are really required.

Download this plugin here: http://wordpress.org/extend/plugins/mf-plus-wpml/

Any issue report it here: https://github.com/magic-fields-team/MF-Plus-WPML/issues


Magic Fields 1.5 Released!

After to  a month of testing we are proud of  launch magic fields V 1.5.

The most big feature on this release is without doubt the new UI, Thanks to  for this, but this is not the unique improvement  on this new release, Magic Fields 1.5 have a  plenty of new features and a few bugfixes if do you want to know which other improvements have this version you can check the change log of this release here:
We are pleased to annouce that after a month of testing we are ready to release Magic Fields v1.5!

This release has a fully reworked and new user interface designed by Travis Hensgen, also there are many new features and bug fixes, please read the changelog to see what new features are available and what bugs have been squashed!


Magic Fields 1.5 Release Candidate

A few weeks ago we released a beta version of the new Magic fields 1.5,  well, we give to this release a big space for be testing because this new version come with a lot of changes and improvements.

Now if all is works fine in  the next few days  we are going to release this version as stable.

Here the changelog:

GENERAL

  • Related Field Types: Extra selections are now available ‘All Posts AND Pages’ and ‘All Posts AND Pages with Write Panel’.
  • Added extra CSS class to Write Panel main menus, based on the sanitized write panel name. E.g. the Menu item for panel named ‘Home Page’ will get the
  • extra class ‘mf-menu-home-page’. Ths allows alternative menu images to be attached to the write panel. Currently this is only possible by having
  • an admin CSS file added through a WordPress ‘admin_head’ filter function in your functions.php, e.g.:
function my_admin_css() {

echo '';

}

if (is_admin()) {
add_filter('admin_head', 'my_admin_css');
}

This feature will be improved in a future version, support for custom post types is avaliable

  • New Hat and Wand Icon for the Magic Fields left menu item
  • Added caching feature to support mostly used functions like get() and get_group();
  • Count down feature for inputs and textareas showing characters left in twitter style.
  • Now displaying Categories in hierarchy in the Write Pannel.
  • Issue 34 fixed
  • Issue 53 Fixed
  • Issue 50 Fixed
  • New way to sort the order of the fields in the write panel

New Template API Functions

  • gen_image_for: Gets a generated image for a field value that’s already known, as is the case for values from the “get_group” function.
  • get_group_with_options: a function that allows certain options to be passed in to make front end code a bit cleaner. Refer to code comments for more details.
  • get_group_with_prefix, get_flat_group, get_flat_group_with_prefix: alias preset convenience functions for get_group_with_options.

View Write Panel:

  • Renamed ‘Name’ Header to ‘Label’ in the field list
  • Added ‘Name (order)’ column to the grid, which displays the code-friendly name of the field followed by the field order number in brackets

Write Panels Listing:

  • Added (Order) number display to the Write Panel Listing

Add / Edit Field:

  • Group name is now displayed in the header (if a parent group exists)
  • When CREATING a field, Magic Fields now suggests an appropriate name for the field after the label is entered or changes. This is based on removing all special characters, converting to lowercase, and converting spaces to underscores. Also, if the field is part of a group, the (singularized) group name is appended to the beginning, which ensures it is unique across the set of fields. For example, if we have a group named “Image Assets” and label a new field “File”, Magic Fields will suggest the field name should be “image_asset_file”.
  • When CHANGING a field, magic fields can suggest a field name based on the rules above by clicking the “suggest” button.
  • The label and field name have been flipped around to support the suggestion features listed above. (i.e. you now fill in the label FIRST) This is now also consistent with the list view.

Edit Page/Post:

  • Major overhaul to the Magic Fields UI with a collapsible panel interface for magic field groups.
  • Tidied up the user interface for (expanded) magic fields groups, which now includes nicer bevels for field groups, better spacing, and nicer icons from the Fugue collection by Yusuke Kamiyamane ( http://p.yusukekamiyamane.com/ )
  • The terminology for “Duplicating” magic fields groups has been changed to “Add Another [Item]”, or “Remove [Item]”.
  • Enhanced the toolbar at the bottom of groups, with a better numerical indicator, and a “grip handle” to indicate the movable section.
  • “Add Another [Item]” link is always moved to the bottom group as groups are added or removed
  • MAJOR FEATURE: Collapsible fields feature, where magic fields groups are collapsed down into a compact read-only group summary. Clicking group summaries will expand the group for editing. By default, any field groups and data that already exist will be loaded as a summary, meaning that pages and posts edit screens are generally MUCH shorter than before. This also makes it far easier to re-order items within each group, since the group summaries are always only about 150 pixels high.
  • Group summaries make use of the jScrollPane plug-in from Kevin Luck ( http://jscrollpane.kelvinluck.com/ ) to provide a much neater horizontal scrollbar for long group summaries. These are much smaller and tidier than the native OS widgets.
  • MAJOR FEATURE: A new “Magic Fields” attributes panel is now available that allows you to change the write panel for a given page/post.
  • MAJOR FEATURE: Added an alternative AJAX file uploader that supports drag and drop, adds an ajax progress spinner, and provides a more consistent file upload UI across all browsers based on Valum’s AJAX uploader ( http://valums.com/ajax-upload/ ). This uploader also improves performance DRAMATICALLY for large numbers of fields, since it does not use an iframe for every file-based field.
  • AJAX Uploader no longer adds a timestamp prefix to uploaded files, instead saving the file to the server as a lowercase sanitized version of the original file name.
  • Enhanced the layout of file upload controls, audio controls, image controls for the new uploader.
  • TinyMCE initilisation has been deferred until the user expands a group summary, to improve load performance.
  • Enhanced the form validation routines to be more robust, and work correctly with the group summaries. Any fields with errors will have their group summary expanded automatically so that the user can see the errors. Also added a little warning box inside the “Publish” panel when there are validation errors so that it’s easier to see that fields are missing (since they might be scrolled out of view at the bottom).
  • Added a save warning for when any field is changed within a magic fields
  • group, which reminds the user that they must publish or update before changes will be saved.
  • Added a much improved color picker by Stefan Petre ( http://www.eyecon.ro/colorpicker/ ) which uses a Photoshop-style color picker allowing you to select many more colors than before. This has been slightly customised to work better in the context of magic fields.
  • Added a “loading data” spinner for the initial load of a group summary.

You can test this Release candidate here:

Download Magic Fields 1.5-RC

A TON of thanks to Traversal without him this  release  couldn’t be possible


Magic Fields 1.5-Beta

Help us testing magic fields 1.5, you can download the beta version here:

Download Magic Fields 1.5-Beta


Preview of the new Magic Fields UI

In the next version of Magic Fields  come with a new UI.

We are very happy with this, all the new skin  was made by Travis Hensgen (@_traversal)

And below  i put a couple of pictures about how looks magic fields nowdays and how will look in the next release.

NOW:

In the next release:


Thanks Travis :)


Magic Fields 1.4.5 Released

We wanted to our next release  be with custom post types support but   unfortunately the lack of time and a few bugs with the wp30 compatibility made us take the choose to  release another  version into the 1.4.x branch for fix these issues and  start to be focus in finish the post type feature for Magic Fields.

Changelog:

And  Thanks for all these people who help us to  have avalaible magic fields in many different languages :)  the list of languages can be found it here: http://wiki.magicfields.org/doku.php?id=translating_magic_fields


Magic Fields 1.4 was released

A long time has passed  from our last release and this new release come with a lot of new stuff for the plugin.  check below the list of new things for this version of Magic Fields:
  • Magic Fields works fine with  the next release of WordPress (v3.0)
  • removed phpthumb, and was added a specific functions for make the same things to phpthumb would  do, this means to magic fields is now 7000 lines more lightweight
  • added a new type of field (markdown text field)
  • Prototype framework is not used anymore, now magic fields only use  jquery
  • Implemented new shortcodes for use the content of the magic fields inside of a post
  • Magic Fields now is avalaible in spanish and was added the .po and .mo files for translate MF in more languages.
  • integrated the changes made by the “living stories” team  for magic fields works well with  “living stories project
  • added a new option for delete the cache of the images  (for avoid overweight in the cache folder)
  • added a new function called get_clean this function doesn’t apply any filter of “the content” onto  the multiline field.
  • removed Edit in place feature,  this feature cause more troubles than benefits
  • Adding a new boton “html” in the multiline custom field.
  • new engine for remove  the physical files when a file is removed in a write panel
And These bugs was fixed:
  • magic fields don’t send anymore trash to the wordpress multimedia content http://bit.ly/av88h5
  • Now the order in the  groups works well, http://bit.ly/9tqH59
  • new way to assign categories onto the write panels (for wordpress 3.0 compatibility)  http://bit.ly/blTAZB
  • now magic fields works well when the wp-config.php file is located outside (up one level) from the wordpress root directory http://bit.ly/9NAxdI
  • Little fixes in the  in the export write panel function
  • Now the button “add new” inside of the manage page into a write panel point into the correct place (before the reference of the write panel was lost)

[UPDATE] Someone reports a bug related with the images and how are resized with the new functions of magic fields, and Edgar just fix it, if do you has the same issue for fix it you just needs replace the function called  aux_image for this one http://gist.github.com/421939  (the  function is in the file called  get-custom.php on the line 366)  and now all should be work smoothly.

The version 1.4.1  was released and fixed this issue. :)


And in another hand, someone  missed  phpthumb in magic fields for that  was added a little article in our wiki for  know how  restore phpthumb in this version of magic fields (for now the article is only in spanish, we hope to someone help us to translate the article to english)  the article is here


Magic Fields 1.4-beta was released

This Version come with a lot of new features, bugfixes and improvements, for that we want have a bigger time for make tests for be sure to this version come as free of bugs as possible

some of the new things to you are going to see be:

  • This version of Magic Fields was tested with the beta of wordpress 3.0 after to fix some issues this version will be works fine with the new version of wordpress (we don’t have time to implement the “post types” in this release but nexts releases we are sure to this will be a feature)
  • We remove Phpthumb we are convinced to phpthumbs make our lives more complicated instead of a more easier, Phpthumbs is a excellent tool but needs be configurated in function of who will use it and magic fields only needs a few functions of phpthumb. So we wrote a couple a functions for use the native functions of WordPress, with this change Magic Fields has 7,000 lines less of code
  • The phpthumbcache folder is now obsolete, now will be used a new folder called cache
  • Was added a new custom field type called Markdown Texto (thanks for who  made the code and who share it with us)
  • Prototype is officialy deprecated, :)  now Magic Fields only use jquery.
  • Was created shortcodes for display the content of the magic field in the  post (more info of this featured soon)
  • Magic Fields is ready for be translated in differents languages  now you will can found the mo and the po files in the languages folder.
  • Was cleaned the code and remove pretty muchs warnings messages when wp_debug is turned on
  • This bug http://bit.ly/9tqH59 is fixed.

If do you want help us to testing this new version you   can download here  Magic Fields 1.4-beta

Now the second Beta.

some of the new things to you are going to see be:

  • The Empty images be save correctly now.
  • add features for living stories plugin/theme
  • remove EIP
  • Fix delete image and remove add image in WP media
  • add function remove file after upload image
  • add option clear cache in magic fields menu
  • add option in field (multiline) for hide visual editor
  • Add front-end function get_clean only for multile field (this function not apply the filter “the content”), fix un phpthumb and fix for multiline field

If do you want help us to testing this new version you   can download here  Magic Fields 1.4-beta2


Issues, wish list and more.

This year started with many changes in our personal lives in consecuence of this the development of magic fields has been very slow until now

But we don’t leave the development we are still working in the next version (1.4) and actually with this release all the things to we want to fix from the original project will be finish.

For that for the future releases we want to know all the suggestions from you and start to add the more popular requested features in Magic Fields. for that in the wiki of the project  was created a page called “wish list” where if you want to see a particular feature in magic fields fell free to add that feature in the wish list and we will start to evaluate which features will be added in the future..

In another hand, this last two months with no much movement in the development we see a lot of comments and possible bugs in the comments of the blog or as a messages in the mailing list.

Well, we think to is a good moment to start to manage the bugs in a better way, if you found a bug and in the mailling list don’t be able to get a answer of your problem or if someone else has the same bug and is something to you can replicate without problems feel free to open a issue here:

http://github.com/hunk/Magic-Fields/issues

Just leave a little description of the bug and leave a little list of the step to you follow to replicate the bug and which operative system are installed in the server where you are using magic Fields and in which browser are you use for see the issue, with this information we can start to fix any bug.

just for finish, this version of Magic Fields come with a bunch of features and optimizations for that the time for test this version will be bigger the next version of magic fields will be launched the 21 of march.