If I want to add a new tab in the user profile page, let's say /user/%user/resume, should I create a new node type and render it in this tab, or should I declare a table describing a résumé per user, develop add/edit/delete forms and render them in this tab ?

For now, I implemented the second options and I am wondering if it would be easier to do it with the Field API by mapping my SQL table to an entity so that I don't need to create all those add/edit/delete forms. So I have a page callback for /user/%user/resume selecting everything necessary in the resume table and rendering the selected informations with a template.

The sub-question would be : should I always map my SQL tables to entities to benefit the Field API functionalities ?

Thank you,


with Drupal you should never have to deal directly with tables and add/edit/delete forms again - Drupal does it all for you. In your case you could either extend the user profile and add a "resume" field or you could add a "resume" content type and use the reference module to reference it to the user.

  • The first sentence is just not true. If you create your own entity types (not a content type), there is absolutely nothing in Drupal which provides you with forms or table creation for that entity. There are a some contrib modules which help with it, but these are far from being complete. – Berdir Nov 6 '11 at 21:41
  • oic, I was referring to content types. The Entity API promises to provide CRUD for entities, right? – uwe Nov 6 '11 at 22:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.