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
I’ve looked around before for image delete scripts, but one tool i’ve seen, rather than delete related images when the post is deleted, scans the images folder, then checks each filename against the database, if it doesnt find a reference it then deletes the file. That might be an easier way to handle image cleanup?
Add it as another button similar to cache cleanup?
Perhaps another option would be to move the files to another folder temporarily which could then be cleared later? to act as a backup
Lee
oh one other thought on the above, that method would allow us to clean up existing MF installs, so if we knew it was in dev we could let clients upload in the knowledge we can clean up later on
Lee
After upgrading the the latest version, posts created with a write panel are not assigned to the proper category. From what I have seen, they are always given the category ID 1, or News in my implementation. Double checking the configuration, the proper categories are selected. Is there a fix for this?
Hi Mike check this http://bit.ly/9kQZkX
Hi Stew maybe you could add a filter to the the_content, and use gen_image or get_image
Hi lee here the changes for delete images when delete a post http://bit.ly/9NFlSg
I seem to have the same problem that Patrick, the order field is not working on the media library, also other fields like legend from images are also missing. When Magic Fields is deactivated everything works ok
Hi Hunk
Quick test that seems to be working perfectly!
This could make Magic Fields VERY useful for me, thank you so much. If I get this working how I need I’ll drop a donation in, thanks again
Lee
Hi, recently I’ve updated to 1.4.5, running WP 3.1 and odd things started to happen after updating post. Before updating the post, all things worked as expected. In the admin section everything looks ok, but in theme, a simple get() function can’t get some fields, some are working fine, don’t know why som are working, some don’t. They get lost somehow. Admin prints them all correctly. Any ideas?
Another thing: It happens sometimes, that duplicate fields don’t get saved. Could be some connection problem, maybe has nothing to do with MF. Don’t know if it has even something to do with the lost values mentioned earlier.
Any help appreciated. Thanks.
Where did the markdown option go? I know it wasn’t great but it was the best way to keep MF/WP from adding improper code to my fields.
Hi hunk,
> New custom field for images (this custom field use the media library of wordpress)
Could you please enlighten us a little on the practical consequences of this?
Hi Hunk,
I comment the line 196 in RCCWP_WritePostPage.php
// if (!current_user_can($requiredCap)) wp_die( __(‘You do not have
sufficient permissions to access this custom write panel.’,
$mf_domain) );
but this didnt solve the problem – I still get the message
Where is the Markdown Field? I used it very often, and now my WordPress MF is broken.
hi Webdesigner change this http://gist.github.com/546842
Great! Thanks. Was this a bug?
Hi again
I see a lot of people reporting bugs, are these down to general issues or changes in practice?
My basic question is, is MF working and safe to use on a real world project? From the very simple tests I’ve done it seems fine to me.
Are there core issues that will bite me on the ass later? Or are the issues people are posting due to specific coding, specific circumstances etc?
I’m hoping to dive into my projects soon and dont want to get screwed half way in
I would still like to offer my thanks to the guys developing this, and think that for the people with bugs, they have/are still doing some sterling work!!
It’s not a commercial product so work with the developers, I know form experience there is nothing more demoralising than users creating problems that aren’t really your fault!
Thanks again Hunk and Co
Lee
Hi Lee.
all projects after to a certain number of lines of code have bugs that is a fact, write thousand of lines and expecting no errors is not humanly possible.
Just talking about wordpress who have a good number of developers behind of his development http://core.trac.wordpress.org/report/1 have a bigger lists of tickets related with bugs.
Talking about to Magic Fields and if is ready for a production environment i think to is ready, we test MF the best as we can for avoid any serious bug for the users but is not possible to we can take in account all the possibles bugs and for that Hunk and me give support for try to fix any issue to be present in magic fields as soon as is possible.
if you think to MF is not ready for your projects i invite you to test it and if you found any bugs you can help us to fixed or at least open a issue into the github project for we can fix it.
And just for finish did you know to “living stories project” was made by people of google and they use magic fields?
i think to that is a big achievement for the project and talk good about if magic fields is ready for real world projects
more info here http://code.google.com/p/living-stories/
Hi guys,
Firstly, great plugin – glad to see Flutter’s beginnings moving forward.
Anyways, I’ve stumbled upon my first error and I was wondering if anyone could provide any insight.
Quick stats: Running WordPress Multisite 3.01 w/Buddypress and have Magic Fields 1.4.5
So, I have an image uploader and, while the image is uploading fine and is displaying when called, the thumbnail is not showing a missing image.
When checking the image’s source, I get “[my-website]/wp-content/plugins/magic-fields/thirdparty/phpthumb/phpThumb.php?src=[my-website]/wp-content/blogs.dir/2/files_mf/12829087005.jpg&w=150&h=120&zc=1″
(Apologies, need to keep the address hidden for the time being.)
I know that phpThumb was removed for 1.4.5, but even when recreating the field from scratch I get this error.
(I did add back the phpThumb code as suggested in an earlier comment but this didn’t change anything.)
So, given that it doesn’t seem like a permissions problem or an update issue, any idea where I should be turning my attention to?
Thanks so much in advance!
Hi Jeremy is not necessary to reinstall phpthumb
put these changes [http://bit.ly/cLueKk] or updates the file [http://bit.ly/96wTOW]
thirdparty/phpthumb/phpThumb.php
and try
@hunk
Thanks so much! After a rather long day, I must’ve completely misread your original post.
Keep up the great work, can’t wait to see where this goes next. (More donations on the way – you guys deserve it.)
Cheers,
Jeremy