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:
- Issue 17 fixed. http://bit.ly/b8AMUQ
- Issue 6 fixed. http://bit.ly/cFV9bi
- Issue 10 fixed. http://bit.ly/alvcS6
- Issue 12 fixed. http://bit.ly/atiK2v
- Issue 29 fixed. http://bit.ly/9RKJeW
- Issue 31 fixed. http://bit.ly/bjYrWn
- Issue 32 fixed. http://bit.ly/cIpJno
- Issue 35 fixed. http://bit.ly/9gifQ1
- Fixed some issues related with permissions
- New custom field for images (this custom field use the media library of wordpress)
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
Will the changes that often get posted on response to a bug get put on a plugin update soon?
hey guys, have been able to do some fantastic stuff with this plugin for my authors! i’m having an issue with the latest version, though: whenever i try to upload using media.php (within wordpress under add new media), the upload fails to show me the url path, instead giving an error: “Warning: Invalid argument supplied for foreach() in /xx/xx/xx.com/wp-admin/includes/media.php on line 1205″
disabling the plugin solves this issue. rolling back a version solves this issue. but the upgrade had a lot of stuff i liked! hoping yo ucan help! will donate if this is resolved
Hi
It seems this version hide “Description” field in the media editor (for images) ??? It’s really a problem for my current project
Agreed Cedric, there is an issue with image uploads and this new version. It also renders the title attribute and other image meta unusable.
Big problem.. but I am sure it can be fixed
Yeah, Cedric. I have the same problem too. I wonder when we’ll have the a release version with fixes.
Hi Cedric an Sudirman apply this changes http://bit.ly/dAv5Jm
It works !!!
Thanks a lot
Hi Guys
Do you recommend applying all the changes on here since 1.4.5? Or are you best applying bits as needed?
Are you likely to release a 1.4.6 with all the changes in soon?
Again thanks for the hard work on this!
Thanks
Lee
I’m wondering if Magic Fields stopped supporting get_post_meta for data retrieval with this version? I used to use that sometimes because it tended to return “cleaner data”. Now, it doesn’t work anymore. I can only use get and that sometimes adds stuff that messes up my code.
Would love some feedback.
Eivind
I have Magic Fields 1.4.5 installed on a WP 3.0.1 installation. Since I’ve updated Magic Fields, the default Pages write panel has disappeared, and I don’t have the option selected to hide the Pages or Posts write panels. It’s just gone. If I deactivate MF, it comes back. Any help you can provide is greatly appreciated.
can u please check your spam because it seems my mails are not getting through, i wrote you about get_image/gen_image() problems
If you have problems with line breaks disappearing from custom fields with visual editor (TinyMCE), add
convert_newlines_to_brs:”1″
to magic-fields/js/custom_fields/editor_validate.js
Just solved this problem, and haven’t seen any other solution anywhere.
Michał
amazing work on the latest release guys! the new interface work is outstanding!!!
Group editing doesn’t work properly.
can you be a little more descriptive? exactly what doesn’t work?
This version ruins sorting of media items. Is there a solution for that?
Eivind
You could try and be a little more supportive chaps, the guys are working for nothing here!
If you are going to report a bug at least give them something to work on
Lee
I still cannot comprehend how the image resizing is supposed to work. I’m not talking about front-end resizing, I mean resizing on upload so that a gigantic image (like 4000px by 4000px with 6mb) would be resized to a smaller size before saving on the server.
And why doesn’t delete work on the server side? Shouldn’t the user be able to delete the actual physical file and the database entry at the same time?!
Any help on these matters!?
Other than those problems I’m loving this plugin! Keep it up!
Hi.
For now you can’t resize a image before to be saves into the server, by default magic fields always save the original image.
Ahh actually when you edit a post with a image field and delete the image and save the post the image is deleted in the server side