How to load your custom module at last or how to know which module overriding my custom module

Yep, this has been a problem since Livelink 7.X and probably Odesta Desktops as well. If two modules both override the same object (i.e. a web node or a llNode or even a core request handler), it's a game of last man standing as to which one will persist (or perhaps last man loading).

As Hans stated, you should really look into the various callbacks to do your custom code as you're guaranteed not to collide with another vendor (or OpenText) when you do it that way.

If you could explain what your orphan/override does, we might be able to help you decide a better way to implement it.

-Hugh

Simple ways to get you going Node you probably know this is an object that is associated by subtype so all nodes of subtype 0 folder and subtype 144 are the same but they exhibit differences in functionality 144 is versionable but 0 is not . OT has for you listeners or callbacks on many node operations for e.g when a node is created , versioned , metadata updated , added and so on .i am not in front of cside but look at core and in that package search for callbacks . If you create a module now and orphan a create node callback and for eg specify that 144 or 0 is what you are listening and in that stub code write echo(‘Hello World’) when that event happens the logs will say that . I recently wrote a reply in this forum about trying to help a user called Franky Egan . I left a bunch of useful links in there that might help . Callbacks should be designed as judicious as possible and you should defer them when possible otherwise in a bulk operation all this extra code will fire and make the thread execute longer than they should.

The beauty of the callbacks is in my opinion like this
1. You have specific entry points that will fire when OT code is happening
2. It does not need to be in your own webnode
3. For e.g Open up CSIDE and basically orphan the NodeCreate Callback.
4. In that code that is now sitting in your module make a statement saying you want that firing for 144 or 0 (do you find these instructions easy or I can handhold you)
5. If you write debug lines you should see that when those events happen.
6. I hate to give you a module I developed because sometimes people forget the fact that the module is written to explain a point they will run with it and make it prod code and it may not be
7. Callback programming is not for the faintest of heart see a link by Ossie http://www.oscriptadventures.com/2013/03/observer-effect-quantum-physics-and.html
8. In your case, I am not sure how you are going to structure your code but again applying a Category to a Node while it is getting created is not that difficult. The difficulty is basically the attribute code because it is quite a complicated thing but there's a piece of code that is published by OT and it serves as the starting point or almost the "bible" of that.
9. Essentially forget that you need a callback you will get there I promise you but write some lines of code (a standard request handler is the easiest when you start programming) try finding a node, attach a category to it and change a few programmatically. In my personal workspace, the links you found are quite a few snippet code that may still work you are welcome to use it but I generally write disclaimers on most of them as they might be old, ancient...Unfortunately, there aren't a lot of oscripters outside of OT and good code is hard to come by...I learned most of it by looking at how OT programmers do it so CSIDe(or builder for a lot os us) is the best friend.
10. If possible attend an OT training I doubt if callbacks are covered but at least you will get some good exposure to the architecture

Happy Thanksgiving now to eat....