I recently created a very simple CRUD table in which the user stores some data. For data, I created a custom node. This functionality is great for creating, editing, and deleting data in a CRUD table using the basic node functionality (I am really amazed at how quickly and easily it was possible to program the main functions using the correct access controls using only a tiny bit of code) .. ..
Since the data should not be processed in the same way as "content", for example, a blog post (no name, no body, no commits, no changes, should not be displayed? Q = node page, without preview, without teasers, etc. .) ... I find that most of my time I spend "shutting down" and changing stuff that drupal does automatically for nodes.
I know this is a matter of taste, but where should I draw a line on what should be considered as a node and what should not? In other words, would it be better to program this stuff from scratch without using nodes?
source
share