Port Node form columns to drupal 7

subscribing...

We're most likely going to do a D7 port - but I've no idea of when. There's a lot of modules that needs porting - it's all about priority and opportunity :)

I've done an initial straight port from D6 to D7 here:

http://github.com/yhahn/nodeformcols

Pull request sent to hugo : )

yhahn's port has been commited to cvs and a dev-build will soon appear.

I think I will keep this issue open until we have a stable release though - if some people could test it on their setups and look for errors then that would be great.

With everything being entities right now, why not make this module more abstract? I'm doing a port right now for Display Suite and am hooking onto all the 'Manage display' screens via hook_form_field_ui_display_overview_form_alter - same hook (change display with fields) is available to hook into the manage fields screen. With hook_field_attach_form() you can then alter the output of a form - for every entity out there without having to write a lot of code.

I could theoretically do this with Display Suite since I'm adding an option to have x regions per display, but I don't want to duplicate efforts of course :)

Field group port to D7 is using the same technique for forms - see http://drupalcode.org/viewvc/drupal/contributions/modules/cck/modules/fi...

Let me know what you guys think!

@swentel: I think yhahn had some thoughts in this direction. Seems like a great idea!

@all If you need inspiration, currently me and Stalski have taken over the port of the CCK fieldgroup module (http://drupal.org/project/field_group). It has become a very powerfull module so far with a very important formatter called 'Region'. The Display Suite module (http://drupal.org/project/ds) is taking advantage of of this formatter and is now able to create n* regions for any form and display for any entity out there. In short, any form for node, user, term etc is now able to be formatted like the way nodeformcols does. It's not our intention to take over this module, but just letting you guys know what the possibilities are :)

edit

We're not aiming to override the form anymore with DS!

subscribing

@7 - I am not sure what you mean by the edit. Does this mean that this is not possible any longer?

I've tested an early release of the d7 version of this module and had some issues with it. I've now updated to the latest git version and it is looking fine on my setup.

+1 for a first stable release

edit: i can't hide form elements, that's the only problem i've found so far

d.o. now uses git. Is there really any reason for hosting the code over on github?

@klonos: I think the code is identical on drupal.org and on GitHub - we just haven't merged the repos since no commits has been made since drupal.org switched to git.

ok, thanx for taking the time to explain Pelle.

+1

swentel, please reconsider regarding your edit on #7!

(Instead of +1:ing, subscribing and stuff - test the dev-release and report issues so people can fix them. If you find no issues then report that and we can go ahead and make a release. I myself haven't got much time for working on this module right now - unsure about the other maintainers - so any help would be great)

@voxpelli - I'm currently starting a new site and trying to decide if switch to D7 or ditch Drupal all together and switch to WordPress, so I can't afford to test all modules I need.

re #16, I've been running dev, issue free. It's great, thank you.

Tested nfc in a d7 install.
extras modules: views, entity, field_collection

Here are the results:

1. There is not a manage forms tab in the manage fields page.
2. On the actual node edit/create page, nfc is not showing.

Issue: nfc is not working.

Re-installed instead through drush did it through gui and ran cron and removed cache.. working now.

Ugly though on an overlay. oh well.

We've been using Node Form Columns for a while now in a D7 distro. No problems to report. It would be great to get an alpha or even beta release up to get more testing of the edge cases (and it would help make our builds more reliable too!).

Just exactly what I wanted. D7 version works great. Coder module has a few issues, none critical, mostly syntax of "Implements" on comment lines, and all files need a first line of // $Id$. The patch implements all those changes. There was one suggestion I did not implement, involving changing the substr() to drupal_substr(). Other than that, I can't see any barriers to a D7 version. I haven't done too much D7 coding, and I did not try the Captcha or Biblio modules. However, it seems to me that with the number of people who have reported using this, at least a beta release would be warranted; is there anything else we can help with so that the maintainers would be comfortable with that?

Hi, I'll be glad if anyone can make a patch (or help me to do one..) that give the ability for 3 culomns and no fust two and a footer

itai_biren, seems like you should create a new issue for that - feature request, normal priority. this thread will probably only be seen by people interested in the d7 port.

D7 dev paired with Rubik. Issue free.
+1 for a beta release.

We already have an initial 7.x dev for some time now and this issue here was exactly for that. Please open new issues from now on in order to address various problems separately. Once the most serious of them are fixed, then we can have a stable(ish) release for those that don't trust dev.

itai_biren: this does sound like a new feature request. File it separately as David suggests in #23.