Quote:
|
Originally Posted by skj310 so how did your integration with PN go?
all working and away from iframes?
hoping you might pass on your instructions ... is it as simple as following the suggestions in this topic as well as the code samples from batmon? |
Going VERY WELL !!
NO FRAMES/IFRAMES or server URL rewriting used. Yes, it kinda goes the way batmon suggested and beyond.
Now called as a PN module:
.../modules.php?op=modload&name=Photopost&file=index
ALL the necessary URL's now go thru a function to change the syntax to PN style, e.g.:
.../modules.php?op=modload&name=Photopost&file=showmembers&cat=500
.../modules.php?op=modload&name=Photopost&file=showphoto&photo=27&sort=1&cat=500&page=1
The PN passthru authentication is working - sign in to PN, you're signed into PP. The auth is based on PostNuke, NOT PNphpBB tables so you
don't need PNphpBB installed.
PP admin screens function as expected. Didn't try to merge that into the PN admin scheme, not worth it, maybe I'll ad an icon there though. PP admin screens use FRAMES and as you know, PN is not very FRAME friendly.
I still need to figure out a quirk with the PN user NOT being logged in, i.e. guest/anonymous user. The default PN user groups are
Users and
Admins which are imported by PP when you install it with the
postnuke integration option. A guest/anonymous user is also a member of the
Users group even if they are NOT logged in. Problem is then that the guest/anon user has all the permissions of a user who is logged in. So I need to figure out a scheme to get around that .... maybe force the guest/anon user into a PP specific group for non-registered folks. So would have to create an additional PP user group when installing and then check if guest user - which I have to do anyway to see if user logged in ...
Probably too much info for you ... but at least it jogs my mind a bit to see it in writing
These changes were not difficult, just very tedious since I had to modify probably over 200 links to now call the url generating function. Touched almost every PHP file and about 1/2 the template files (which are just PHP/HTML code anyway). All these changes are (or should be
) transparent to the original PP code (4.8.2), so PP will operate standalone just as it does now. All this is based on a setting in the config file.
There's a few other minor quirks to work out, CSS stuff, had to fix some file paths in the admin screens to look for the installed directory instead of assuming the default dir. PN modules actually operate out of the PN root dir, not where the module is actually installed
/
versus
/modules/Photopost/...
Coupla other things that escape me right now too, no showstoppers though.
Michael P/Omegatron have both expressed interest in this integration, so I'm hoping they'll like what they see and we can work out something to merge it into the PP baseline ??
I will put up a public demo up soon, and put an annoucement on the PN forums. Work/life has been getting in the way of that for the last few weeks.
This could be great
PR, cause it then opens the door to 1000's of other sites for integration with PHPNuke/MaxDev and other related CMS's. This should work the same w/MaxDev, since's it's just a PN fork. PHPNuke has slightly different URL syntax, but that should be trivial now to just mod the url gen function for that, then add the appropriate PHPNuke authentication. Although supposedly the PHPNuke auth via phpBB is already in place.
Since ReviewPost and the Classified modules seem to be derivatives of the PP code, these techniques could be applied to those too and make those mod's PN/*nuke friendly !! Opens those mod's up to 1000's of site !! = $$$
Mike