I installed Name module to a clean D7 built on 2009-Nov-03. I added a name field "Name: John Doe" to a new content type. However,　"Add new content" page does not show the form for entering Name. It just shows a blank space. Could you please check the module on the latest version of D7?

Comments

mcload’s picture

mcload commented

Add new page is giving the following warning, so they may be related:

Notice: Undefined index: render element in theme() (line 803 of /home/d7/public_html/includes/theme.inc).
Notice: Undefined index: #children in theme_form_element() (line 2771 of /home/d7/public_html/includes/form.inc).

alan d.’s picture

alan d. commented

Sorry, I didn't realise that the dev snapshot was exposed. It was based on a Drupal version from early October. I'm majorly refactoring it before creating an "official" dev release, hopefully in about two weeks or so.

There have been some big general changes in the Drupal API, so some errors are likely in this version. I will close this issue when the release is released properly as a warning for others.

mcload’s picture

mcload commented

Is there any updates on the new version?

alan d.’s picture

alan d. commented

It looks like profile hasn't made it, so my personal interest in this has dropped accordingly. With a likely release date for Drupal early next year (March?), I'll update this then. We threw the standard Drupal profile module about 2 months back and are using a fully customizable hacked version. The simple field definitions / implementations are a dream and we'll probably use this on all of our sites untill Drupal 8 now.

FYI, I've let the guys running the Drupal 5 cck name field that they can have the namespace if they like, but considering that they haven't ported to Drupal 6 yet, I don't think that this will happen.

alan d.’s picture

alan d. commented
Title: Cannot input name on the "Add new content" page » Drupal 7 port
Category: bug » task

Last time I checked, dynamic columns were still very unstable. Cleaned up the module and backported to Drupal 6. Time permitting, I re-investigate after each major D7 release (alpha-2, beta-1, etc).

If by rc-1 the column structure is unstable, I may have to resort to having columns varchar(255) for all columns, both inactive and active components. That's a lot of potential NULL fields, but the overhead is fairly minor (4 char + any index related stuff)

alan d.’s picture

alan d. commented

Road map / progress report for porting name.

Installation & schema
completed 30 Sep, 2010
Settings page
completed 30 Sep, 2010
List formats page
completed 30 Sep, 2010
Edit / add / delete formats pages
completed 30 Sep, 2010
Test name_format() functionality
completed 30 Sep, 2010
Element
completed 1 Oct, 2010
Field
completed 1 Oct, 2010
Widget
completed 1 Oct, 2010
Formatters
completed 1 Oct, 2010
Custom field admin theming (if applicable)
completed 2 Oct, 2010
Free text field and autocomplete options
completed 2011
Upgrade path
todo
Names Database
To support the auto-complete option, a data source for the names was required. This was the result. The module will ship with nearly 50,000 family names, 90,000 given names and 50 titles.
completed 8 Oct, 2010
More tests
todo

Tests and issues resolution

  • name_format - 2 Oct, 2010
  • installation & settings - 3 Oct, 2010
  • Custom formats - list, add, edit, delete - 7 Oct, 2010
  • Field creation settings
  • Multi-value fields
  • Schema changes
  • String overides
  • Names Database Submodule
alan d.’s picture

alan d. commented
Title: Drupal 7 port » Finishing Drupal 7 tasks - I18n issues and tests
Component: User interface » Testing
Assigned: Unassigned » alan d.

Needs a follow up on the widget validation, this appears to have changed slightly, and also see if there is a way to resolve the core Drupal issue #1200910: user_profile_form_validate() is always called, even when $category != 'account'.

alan d.’s picture

alan d. commented
Title: Finishing Drupal 7 tasks - I18n issues and tests » Finishing Drupal 7 tasks
Status: Active » Closed (fixed)

I18n issue can be tracked here: #1788156: Name components title are not translated - simple name only use case patch using t($user_data); which is not the right direction to take, but may work.