Module development and code questions

I'm in the process of creating an interest match module. It currently allows administrators to configure subjects the user may rate their interest in, and allows users to search for similar users by calculating the total difference between users ratings and order by that value (current source: http://www.mypastebin.com/?code=1880021952). I would like to get some response on a good implementation of this. A was thinking about a couple of things.

This is in some respects similar to the profile module and how it is used for instance on drupal.org, but I think it sufficiently different in nature to require it's own module. However, integration could be fine by integrating it into a user category through the user hook. Not sure where that'll place the search though. Making a search for other fields of the profile.module would be problematic.

I was also thinking it could be nice to integrate it into the taxonomy system, which would make it quite different. The admin could connect the module to one or more categories. Interest subjects would be tied to categories. This would allow users to rate their interest in different categories as they browse the site or at a central page. It would also allow for instance a category sensitive block showing users interested in the current category, which could also be useful for administrators by being kind of a survey of site interest. It would be more like a category rating system, closely tied to users. This approach would also allow users to show a page with entries (nodes) of interest, which perhaps moves away a matchmaking type module.

Hi,
I added a menu and now i want to remove that menu. To remove that when i went to admin / menus i saw that it is displaying as "locked" under operations. So how do i remove this menu ? Pls help me out to solve this proble.

Thanking You

ezynes

Hi,

I'm creating a custom module for a new node type and want to be able to have an alias for all those nodes. Such as:

/newnodetype/232

i.e. each node would be at /newnodetype/[id] rather than /node/[id]

But I only want this to work for my own node type, not for all nodes.

Which hook should I be looking at, and can anyone provide code for an implementation of this?

Jake.

It doesn't work as-is and I don't see an update. I read the page on converting 4.5 modules to 4.6, and I think I know what the problem is, considering my error.

The functions node_access_join_sql() and node_access_where_sql() should not be used any more but the SELECT-queries should be wrapped in a db_rewrite_sql() call.

Well, this module is using node_access_join_sql(). Problem is, I'm a PHP n00b, and don't know how to make the change. Has anyone else done this?

Any prefered way to create/manage a node without connection to SQL. We'd like to use the node model but have links go external (or perhaps via another module for rendering) and not expect them to be in the local system-- in our case they are not. We can manage in the module the links but the theme rendering will add a bogus link (in for example the headline).

Has anyone messed with this? I noticed this post: http://drupal.org/node/12289, but can only assume nobody has touched it since then. I'm guessing that it'd have to be either just patched onto the comment system or a module would have to be added that facilitated handling of attachments that weren't nodes. Because you can only attach stuff to nodes, which is faily limiting (of course...