Module development and code questions

Hi.

I have come across something very odd. I have a callback function which is set in the hook_menu function for my module. In the callback, I change the breadcrumb like this:

$breadcrumb = array();
$breadcrumb[] = array('path' => 'competitions', 'title' => t('competitions'));
$breadcrumb[] = array('path' => 'node/'.$node->nid, 'title' => $title);
$breadcrumb[] = array('path' => 'node/'.$node->nid.'/competition/mosaic', 'title' => t('Mosaic'));
menu_set_location($breadcrumb);

Just throwing out a teaser, an Invision Power Board integration module will be released soon. Just getting the "underwritting" working correct. I'd like to get a feel for interest as I'd like to get some voluteers for bug-shaking and watch the queue for it closley.

The module is more than meets the eye. It's a faily complex syncing module that also show's the Invision system "inline" as content when you're viewing the forum (as an iFrame). However, Drupal is "King". All authentication is handled by drupal. Invision looks to drupal for authentication, and all registration is handled through Drupal.

The module uses cURL, and cURL must be enabled.

The module also handles the following situations.
Problem Sets:

Problem: User is in the Invision system, but not the drupal system.
Solution: When the user try's to login into the Invision system, they are redirected to the drupal /user page for login.

Problem: User is in the Drupal system but not the Invision system.
Solution: The module comes with a setting called "auth-regsiter" that you can check. When checked, if a user is authenticated in the D (Drupal) system, but not IV (Invision), they are automatically registered into the IV system, and the D system continues on un-beknown to the user.

Problem:User is in neither system

Hi,

I'm trying to figure out the recommended way of implementing a module that has two new node types in a child parent relationship. I recognize that I can define multiple nodes like:

function qdrupal_node_info() {
  return array(
    'qcodo_application' => array(
      'name' => t('Qcodo Application'),
      'module' => 'qcodo_application',
      'description' => t('Create a new Qcodo Application'),
      'title_label' => t('Qcodo app'),
      'body_label' => t('Create an application'),
    ),
    'qcodo_page' => array(
      'name' => t('Qcodo Page'),
      'module' => 'qcodo_page',
      'description' => t('Add a new Qcodo page to an application'),
      'title_label' => t('Qcodo page'),
      'body_label' => t('Create an application page'),

    ),
  );
}

A qcodo_application can have multiple qcodo_pages, and qcodo_pages can only have one qcodo_application.
Then I can use qcodo_page_insert, and qcodo_application_insert (and the rest of the node hooks) respectively. But then I hit a stumbling block.

I looked at other modules for a child/parent example (blog, forum and book) which all seem to be candidates for child-parent relationships, but all three of them define only one node type. They each seem to handle the parent relationship differently and I'm not clear as to how, or what the recommended approach should be.

I'm making a nod modifying the book module, only i've not edited the TAXONOMY or NODE modules and when i try to view the content i created i get this error.

warning: Attempt to assign property of non-object in C:\wamp\www\modules\node\node.module on line 675.
warning: Attempt to assign property of non-object in C:\wamp\www\modules\node\node.module on line 691.
warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in C:\wamp\www\modules\taxonomy\taxonomy.module on line 31.

Hi all,

I've readen I have to put my own modules in /sites/all/modules... but I have a question, where have I to put my downloads modules but not development by myself?

I hope you understand me.

Thanks for Drupal

Just installed tinyMCE module (java WYSIWYG editor). All seemed OK, configuration correct, plugins and options seen in the control panel, editable. Correctly configured default format, users aso.