By rinogo on

There it is. Fairly self-explanatory. What's the advantage to using Computed Fields when hook_nodeapi() can be used to populate any CCK field of a node on $op=='submit' or 'save'?

The first obvious answer is that theming with a Computed Field is slightly easier. However, what if you're coding your own theme for the node type from scratch? Are there still advantages beyond theming?

Looking forward to some interesting discussion, :)
-Rich

⋅ Categories: Drupal 5.x

Comments

rinogo’s picture

rinogo commented

no comments?
bump.

rinogo’s picture

rinogo commented

Is this issue really so trivial that no one is bothering to respond? Or was I unclear in my question? Please help. :)

entrigan’s picture

entrigan commented

I do not think it is trivial, and I have the same question. I imagine the whole benefit of custom field is that you do not need 1) access to the drupal install (although hopefully anyone with php permissions does have said access) 2) do not need to understand hook_nodeapi and node_save or SQL

But that said I am curious, is there any tangible benefit to computed field for someone who is ok with 1) and 2)?