Domain Previous/Next

Sorry i forgot to mention that the Coding Module, may return a critical error due to the way I've included a variable within the query to act as a modifier (< >). This shouldn't be an issue.

Hey thanks for the reply and taking the time to look at the project.

1) True, these other modules don't support this. This was the main reason why i developed the module. I believe making the module not rely on Domain Access and still run on single sites appeals to more users.
2) Cron isn't needed to index and node listings as a direct query against the node table is done, I wouldn't personally consider this a design flaw. But i'm open for suggestions?
3) Very true, probably should reconsider the description on the project page so it's not aimed at bugs within other modules.
4) Always a great feature of any module. It's obvious users want to be able to customize the output the way they want.
5) A good example with this point is:

You have a standard image gallery on your website using the Image Content Type. You install this module which adds previous and next functionality but you want a little bit more outputted such as the image of the next and previous node next to the links. Other examples could include custom teaser text or a custom link, these would of course all vary based on what's available within that content type.

Cheers.

Thanks for the fast reply...

All true, I've added all this functionality feeling as though It was needed as a base to support previous/next on Domain Access, theres functionality mixing from both Custom Pagers and Previous/Next API. I guess you could say I'm trying to grab the best from each and provide even more features.

While bugs can be raised not all tickets are actioned within a time needed which is understandable, no one can dedicate the majority of their time purely to a single module. The maintainers of the module also need to consider suggestions if they feel they are valid to add to the project theres always a chance of rejection.

This is what I required and i feel that i should share and maintain it with the community.

I wouldn't consider Cron a design flaw at all, theres different ways to go about achieving a goal, mine just happened to be not using Cron. (While most users would have this functionality enabled on their server some may not).

As i said before i should probably reconsider the description on the project.

I've updated the description of the module to not be aimed at other modules missing functionality and/or bugs. I've also provided an example.

http://drupal.org/sandbox/Funke-Tom/1133180

Thanks Joachim for taking a look, appreciate it.

I don't want to appear rude but if I may quote yourself:

My point is that missing features can be added, and bugs can be fixed, and theming capability can be improved

You're right it is limited... this would be a good enhancement I could work on in the future.

Cheers,
Tom

Fixed an error that would occur when not using the Domain module. Please see commit: http://drupalcode.org/sandbox/Funke-Tom/1133180.git/commit/0ddfa6b

Thanks! Hoping the module will still be considered for approval as I'm about to start enhancements within the coming days.

Once again i've updated the project description to include examples of a site running Domain Access with the use of the Domain Previous/Next module.

http://drupal.org/sandbox/Funke-Tom/1133180

I've taken into account your view and created issues within both modules to see if the contributors believe the functionality should be added.

http://drupal.org/node/1189870
http://drupal.org/node/1189868

I'd be more than happy to contribute code towards these modules, this could potentially mean this work doesn't goto waste or at least the idea.

Cheers.

Thanks attiks, definitely considering it when i have a spare moment.