Search Results

Your requirement seems pretty straight forward. If you want to save some time, I would suggest that you use the Field API. To make those fields non-editable by users and administrators, all you need t …

You can create your own menu callback using hook_menu (you need to do this from your custom module). Then from your custom callback you you can call whatever callback function is assigned to the diffe …

You could also do more complex things with Views, such as attaching a View to all the nodes of a particular content type when a user with a certain role is active, just to name an example. …

In this example Classroom is a content type (entity) with a field called field_students. field_students is a node reference field, and it references nodes (entities) of content type Student. // Get all …

You can easily hook into the validation process by implementing hook_form_alter(&$form, &$form_state, $form_id) or it's cousin hook_form_FORM_ID_alter(). There you can inspect the $form variable, find …

You can use hook_update_N() to update multiple nodes at once with a single run of update.php. … Inside it you can load all the nodes that you need to modify using node_load(), and after you are done changing the taxonomies programatically, call node_save(). …

Interesting. Initially it would appear that the "Pagetitle" is being stored in the Last Name field. However assuming that it's not, you can use the devel_themer module to find out what and where is th …

Create a product of type "computer". Then create a list field in "computer" called "computer type", where you can specify "desktop" or "laptop". You can have another list field named "brand" on the …

This should filter out nodes based on the current taxonomy found in the URL path. For safety, add a content type filter (regular, non-contextual), and specify "taxonomy term page". …