When not to use a Drupal node?

Posted by stotastic on Stack Overflow See other posts from Stack Overflow or by stotastic
Published on 2010-06-17T14:04:36Z Indexed on 2010/06/17 22:53 UTC
Read the original article Hit count: 265

Filed under:
|

I've recently created a very simple CRUD table where the user stores some data. For the data, I created a custom node. The functionality works great for creating, editing, and deleting data in the CRUD table using the basic node functionality (I'm actually amazed how fast and easy it was to program the basic functionality with proper access controls using only a tiny bit of code)....

Since the data isn't meant to be treated the same way as 'content' such as a blog post (no title, no body, no commments, no revisions, shouldn't show up on ?q=node page, no previews, no teasers, etc)... I find that I'm spending most of my time 'turning off' and modifying the stuff that drupal does automatically for nodes.

I know its a matter of taste, but where should one draw the line on what should be treated as a node and what shouldn't? In other words, would it be better to program this stuff from scratch without using nodes?

© Stack Overflow or respective owner

Related posts about drupal

Related posts about drupal-6