Use PPPro, Classifieds, Review as a PHPNUKE module. How?

[Chuck S]

Either way Batmon as Michael stated the overhead of adding a conditional switch's everywhere is not good.

The work load in this basically involves changing every single link in our program and I dont rightly know that a forward call on every single link in the program is the best thing to do. In fact with any program the less forwards their are the better.

The Developer will weigh out the pro's and con's based on the percentage of Nuke customers

[batmon]

Great, thanks. Just want you to know that the forward() call and the url_link() is different. I am just hoping that you can use the idea of forward() that you guys already did, and apoply the same idea to change the links dynamically. This will make the PP product line more comp. with other CMS. Hoping that this one time deal "link changes" will make all the future versions much easier to enhance.

I think the reason that PHPNUKE and POSTNUKE users not using PhotoPost is because they don't really work together?? If we can fix this then I am sure your market share will be even bigger than now.

Just my two cents...

[mlucek]

The Developer will weigh out the pro's and con's based on the percentage of Nuke customers

I think the reason that PHPNUKE and POSTNUKE users not using PhotoPost is because they don't really work together?? If we can fix this then I am sure your market share will be even bigger than now.

Guys, it's a classic Catch-22 situation.

There are not very many *nuke customers because PP et.al. provides little integration outside of user authentication, for the *nuke and other CMS's. AND the PP folks provide little support for *nuke CMS's (and others like Mambo) because there's not many *nuke customers.

One follows the other.

If all it takes to make PP, etc. work natively with the *nuke's/other CMS's are some sort of URL rewrite/forward function (which is what the *nukes do anyway) and the related code changes + header/footer related too, then it's a one-time thing. I suspect it would only take < 1 day to make these changes, probably much less (Batmon - how long did it take you ?) I doubt if there's much more PHP server overhead in handling another if statement. Though there's probably a better way for that function then to use str_replace. The PP code already uses a strcat function to build the URL. Can look at the *nuke or gallery source code to see what they do. Then if there are any other CMS changes, they're pretty much isolated to that function.

The open source Gallery project does just that - it detects if it's running standalone, or embedded (e.g. phpNuke or PostNuke) and modifies the url's on-the-fly accordingly.

One guy has PP running as a PostNuke module at:

www.anointed.net

I believe he's using URL rewrites via Apache and some minor code includes to accomplish the same thing.

There are numerous folks that I know of (me included & I've already purchased PP, but haven't deployed it yet because of lack of integration - not fond of FRAMES) that would love to use PP in their *nuke sites. There's talk about that on the PostNuke, phpNuke and Mambo forums and probably a few others that I'm not aware of. I'm not a fan of Gallery's layout so am looking to move away from that. Folks not happy with Gallery are moving to the opensource Coppermine gallery which is pretty darn good alternative and pretty darn nice looking too.

Soooooo, Michael/omegatron, whattu think ? Certainly can't hurt to give it a try ? I'll be happy to alpha/beta test if for you. The old movie line: Build it and they will come. There are literally 100's of 1000's of *nuke sites out there.