Module development and code questions

Once somebody creates a node with a unique path alias is it possible to lock that alias so they can never change it again?

I want them to be able to choose what they use when the create the node, and I want them to be able to go back and edit the content. I don't want them to be able to change the path alias once it is created though.

Any ideas?

Thank you!

I've perused the forums and am still not totally sure about how to install Gallery2.1 to work correctly with a multi(3)-site installation of drupal....that is 1 installation with three data tables. Do I have to install a multi-site installation of Gallery2.1 to go along with my multi-site drupal installation (if so, can you tell me explicitly what directory to install gallery2.1 into)? - Do you think this is overkill if all I want to do is allow users to post pictures of books up to a "trading post" part of the site - like a book swap?

Is it possible to make it so when you add somebody as a buddy that user has the then confirm to have you as a buddy? I would pretty much want it to work like myspace where you can't just add anyone as a friend. That person has to actually confirm it. Is this possible?

Thanks!

I am wanting to include Go Module (don't know where it has gone, but i've still got it was in CVS - works 'ok' for me) into my module.

So that I can create an external link (go module) from the same form as my module.

How do I do this OR how do I submit to two tables with my module's form?

The Category module has received much praise, and there may be a tendency to replace Drupal's taxonomy with Category. On the surface, it doesn't seem to hurt, because the Category module seems to be a generalization of the taxonomy module. That is, if you don't want the additional features provided by Category simply disable them.

I've followed discussions (example: this thread) related to taxonomy and Category for a while now. Last night I installed the Category module and played around with it. Everything went well. It's an impressive module and I admired the author for taking on this task. But ..... if people want to replace Drupal's taxonomy with Category, I think it'd be a mistake. The current taxonomy module needs much improvement to take it to the next level, but ... replacing it with category is not the right thing to do.

I'm writing not to criticize Category but to hope people will improve the current taxonomy and take it to the next level.

Essentially, we are talking about three main things: static content (e.g. book pages, "about us" type of pages), dynamic content (stories, forum topics,) and taxonomy.

Taxonomy is not exactly static or dynamic content and it would be a mistake to generalize these three things and give users the option not to use them. 99% of C++ programmers do not know the existence of the "throw clause". Why? it's optional, and nobody uses it. Java requires the "throws" clause and it is a great thing. Making things optional can be very dangerous. Taxonomy terms don't really need all the types of treatment that a node/content needs. For example, "comments", etc. I feel that in a long run these things can create loopholes and artifacts on taxonomy that are not pleasant at all.

While i was browsing a german seo forum, i saw an interesting thing.

There is a user (jojo), who has a image in his signature, with the latest 3 article-headlines of his blog!

You can see it here http://www.abakus-internet-marketing.de/foren/viewtopic/t-25617.html#211562

The image autotmaticaly will updated, if a new article is written! i love this.

Can somebody do this for drupal, i know thats less code, only some lines.