Using Service Links Module

Charleston,

I see - It looks like you're misinterpreting the requirements language a bit.

For any module listing on the modules admin page, there may be two listings: "Requires" and "Required by." If a given Module A requires Module B, then you need Module B to run Module A. But "required by" is the reverse relationship - If Module A is required by Module B, then you need Module A if you want to run module B. In this second case, however, you can still use Module A without running Module B.

Think of it like this: Often in a set of modules like Service Links, the "main" module (service_links) provides a basic functionality. Note that for that module, there's no "Requires" section, so you can use just the single Service Links module on its own. Other modules in that Service Links set, such as service_links_share, depend on the basic functionality of service_links, and wouldn't work with out it. But they only add extra features to service_links - they do not provide any essential functionality that service_links needs. So these extra modules list "Service Links" under "requires." It's because of this relationship - needing Service Links to work, that they are listed under the main module's (Service Links) "Required by" section.

So if you just want the basic features provided by Service Links, you don't need to enable Service Links Share. It sounds like you're just starting to implement Service Links, so it may be the case that you don't need any of the extra modules. If you are also interested in using the Share module, then Service Links Share will "connect" the two and help them interoperate. But if you have no other reason to use Share or Service Links Share, you won't need them to run Service Links.

Does that make sense and help?

-Gabe