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.
Also, would be great to have a tutorial on how to create custom fields. My company would love to contribute with a few new fields which we think would be useful.
Looking forward to hear from you!
Regards,
R
Great! looking forward to it.
Keep up the good work.
Thanks for providing the ability to easily submit feature requests. I have just added six requests on the wish list. The ones which were already there were very good too.
Eivind
Hi!
I just discovered ‘Flutter’ – and looking around I found ‘Magic Fields’.
I’d like to know why you forked Flutter, and why you think I should perhaps go with Magic Fields rather than Flutter.
Since I don’t know either of the plug-ins very well, it is hard for me to know which one to choose. May you should have an ‘About’ page, telling us why you thought it necessary to do a fork, and why Magic Fields might be chosen over Flutter?
Regards
Acebone
hi Acebone.
This is a title personal.
After working on the development of flutter for about 8 months, I did not like many things about develop, I dont really felt no development plan, Flutter is a plugin of freshout, I could not add or remove any of the functions that did not seem to me to be necessary, To add or to remove functions tape-worm that to make a seríe of steps which me heran too tired and very longs, had not a much of time of testing and develop (had other activities inside freshout that it had to do), For my part I decided to initiate MF with david aka gnuget (another ex-devel of flutter) because that wanted to add/remove all those functionalities that I could never in flutter, have tried to do a development plan for MF, gradually improve the functioning of MF, In MF not only David and I take the decisions, There is a series of persons whom we ask for opinion and We take in it counts the users.
I believe very much in this project and am treating that it performs the better code for MF.
how is better, this is a question that alone your you can answer, the best for you is that allows you to do more easily and rapidly your work.
sorry for my bad english.
Regards.
Hunk
When will you release the new version?
Hi Mediengestalter
expect to have the beta this weekend and the new release in late March
there is any way I can get specific posts by using get_posts and query for a specific value for example. I have a write panel with a field start_date. I want to “get_posts” all the post with a value equal with start_date. Is this possible?
Hi Chris, check query_posts section Custom Field Parameters.
http://codex.wordpress.org/Template_Tags/query_posts
Yeah, the custom fields of Magic fields are custom fields of wordpress, so you can do something like this:
query_posts(‘meta_key=&meta_compare=>&meta_value=‘);
more examples about how use query_posts here:
http://codex.wordpress.org/Template_Tags/query_posts
ok…I did that…and it didn’t work, but now I know why… how do I compare meta_value with date field.
‘meta_key=start_date&meta_key=<=&meta_value='.date("Y-m-d")..but it doesn't work. can you tell me how is the correct way to do it? Thank you!
hi Cristian.
check this code http://gist.github.com/323514
Thank you very much for your answer, but I know where my problem was… I had multiple meta_key. How can I use query_posts so I can query for two or there meta_keys. Do I need to use WP_Query?
Cool. Cant wait for 1.4! Really great work you are doing guys!
//Johan
With wp 2.9 having post_types and 3.0 finally having the UI for post_types, I would love to see mf have the capability of creating groups of mf tied to a specific post_type.
That way if I create the post_type ‘music’ I could have a special mf area with ‘music’ specific fields like artist/year/cover-art/genre/etc…
Would go a very long way towards helping wp become more of a true cms then, and would make my life much easier when building client sites with specific post_types.
[...] See the article here: Issues, wish list and more. | Magic Fields [...]
I tried to activate mf in my wpmu 2.9.2 setup and got the following errors
/wp-content/plugins/Magic-Fields/blogs.dir/1/files_mf/phpthumbcache/ /wp-content/plugins/Magic-Fields/blogs.dir/1/files_mf/
It should not have the path /plugins/Magic-Fields/ in there…
What file do I need to modify so that it will try to create the dirs in the proper location?
(by removing /plugins/Magic-Fields/ part then it’s correct)
Hi, I’m using magic fields right now for a new project.
I just want to know if you are going to implement the custom post types the way it’s implemented in wp3 so a Post Type don’t need to be tied to a category (like it does right now on magic fields).
Actually, in wp3 I can create custom post types and different types of taxonomy items for each post type (hierarchical or not).
Take a look at this plugins:
http://wordpress.org/extend/plugins/cms-press/
http://wordpress.org/extend/plugins/custom-post-type-ui/
Maybe you don’t need to implement this stuff on magic fields, just use magic fields to create the custom fields for each post type. You could also remove the ability to create custom write panels since it won’t be needed anymore, making magic fields lighter.
Just some thoughts…
I really like magic fields, and I just tried all custom fields plugins out there: more fields, flutter, supple forms, custom field template, ES Custom Fields Interface, Verve Meta Boxes…
But magic fields is the best right now.
I know this isn’t up to 2.9 yet, but for my purposes, it still works well. However, I was wondering about one thing in regards to the edit in place feature.
Does it have to be a text field only? The edit in place functionality doesn’t work for a drop down and I was just wondering if that’s by design or not.
Thanks for the plugin! It has certainly helped my project.
In hindsight, I probably shouldn’t have installed this version with 2.9.2. For me, it forced the attributes of the write panel I created onto every page. Since I had stripped down the write panel to just the custom fields and content box, this was a real problem. Updating the write panel didn’t change anything and I eventually reinstalled WordPress to fix the problem.
Still looking forward to your next version. I like the plugin.