Posted by zmove on August 28, 2007 at 7:39am
Jump to:
| Project: | Recipe |
| Version: | master |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | brdwor |
| Status: | closed (fixed) |
Issue Summary
Hi there,
I'm thinking about one idea that could be very cool for future orientations of the wonderfull Recipe module.
Is to considerate fields as CCK fields. It could be more easy to theme, to integrate with others module etc...
At the instance, all the content with the recipe module is putted in $node->content array, then, this is very hard to theme if you want to put the content of others modules in the middle of your recipe.
If the recipe fields where CCK fields, you could use all CCK feature to organize them, theme them and a lot of others module could be compatible.
Do you know what I mean ? If you have some questions, don't hesitate to ask me.
Comments
#1
I really like this idea. It would be great to see the recipe module more integrated into CCK and maybe even views to provide things like a recipe book view or various views of modules.
#2
This is a work in progress. I will post test code and upload to CVS HEAD when a minimum number of features are implemented. It will not be mainstream recipe.module until an data migration path is available.
#3
Thanks for the update brdwor, very thorough. It lets me know exactly what to expect. :-)
#4
I'm very excited about this module but was thinking the same thing about CCK integration. Another vote from this corner!
#5
I'm interested in also and I have a deadline. Maybe we can join forces closer. Feel free to make contact with me directly.
#6
Hi guys,
Did you get any further with the CCK enabling of the Recipe-module. I too am on a deadline with this need.
I hope to get better integration with views soon. What's the story?
Anyone?
Thanks
Morten
#7
I would like to do some testing if I can help with anything.
Just let me know.
Thanks
Morten
#8
Is there any news on this issue? Is brdwor still working on it, now that it's two years later? I'd be willing to help if needed.
#9
Most of it is done. Recipe now plays well with CCK, manage fields now works to order the edit screen, the recipe data is not packed as html anymore into the $content variable. Views2 support was added. It is all much more themeable and usable, and more importantly, most of the older cruft that was Drupal5ish have been converted to the Drupal6 APIs.
#10
Thanks for the fast reply! I found this old issue because I noticed that most of Recipe's fields aren't available for manipulation in CCK, such as ingredients, notes, source, etc. Is that still in the works, or am I just missing something? Thanks!
#11
Right now recipe's CCK strategy is to support it for adding new fields to recipes, and implementing the "manage fields" api
for field sorting on the edit screen. At this time we aren't converting recipe to only use CCK fields, but is has been talked about with all of
the good and the bad. But there is now nice support for recipe themeing using the standard Drupal theme api.
Which fields are you trying to modify? You can add css stuff in a style sheet, add css class names in the node-recipe.tpl.php file, etc...
Reorder and such.
#12
Oh my issue was minor. I had somehow managed to get the "title" field to display below all the other recipe fields in the Create Recipe form. I was hoping to use CCK to correct that when I noticed none of Recipe's fields showed up. I managed to fix it anyway, but I was still curious if there were plans for CCK fields. Thanks!
#13
Yep, field sorting is supported in the latest dev version using the "manage fields" cck functionality.
#14
The 2010-Jun-20 dev snapshot changes this again slightly. You may not need to change the template at all to show
cck fields for images or fivestar type modules.
#15
Ah, that would be why. I'm still on 6.x-1.2, haven't upgraded yet! Thanks!
#16
Automatically closed -- issue fixed for 2 weeks with no activity.