Issues with 1.7.2 and phpNuke 7.9

by **granbidit** » Sat Dec 23, 2006 12:27 pm

I managed to install 1.7.2 on my site and get it working. Almost. If a member links from the module list, they get this:

http://www.erusguild.com/modules.php?name=Roster

Which doesnt work too well. If you click on a character name, it gives you a 404 error. Any other attempts to select another function direct you to the homepage with the exception of clicking the roster button, which directs you to:

http://erusguild.com/modules/Roster/index.php

And the second link works fine. How do I get the module to link directly to the index.php page? The roster works, I just have to instruct all my guildmates to click on the roster button after linking from the modules list. Very annoying. Thank you in advance for any help.

by **UNIT1977** » Sat Dec 23, 2006 2:56 pm

Hi,

Just a dumb question, but do you have the privileges set correctly on the Roster module in your nuke admin section.

When I click on your first link it tells me that that section is for administrators only.

I am guessing that the privileges might be set to administrator only instead of public or registered.

Just a guess....I could be wrong....hope this helps though.

by **zanix** » Sat Dec 23, 2006 4:33 pm

Roster is NOT a phpnuke module
Roster is meant to be a standalone web application

There are many, many things that need to be changed to make it work as a module in phpnuke

by **Anaxent** » Sat Dec 23, 2006 4:52 pm

Not only is it not made for being any type of module this version is also with in beta meaning there are strict guidlines that need to be met and followed

Beta Software Guidlines

Restrictions on Use

You may not:
* Create derivative works based on the Beta Software
* Reproduce the Beta Software except as described in this Agreement
* Sell, assign, license, disclose, or otherwise transfer or make available the Beta Software or any copies of the Beta Software in any form to any third parties
* Alter, translate, decompile, or attempt to reverse engineer the Beta Software, subject to applicable law which permits such activity notwithstanding this contractual prohibition
* Remove or alter any proprietary notices or marks on the Beta Software
* Use the Beta Software for production use

Production use includes, without limitation, using the Beta Software on commercial websites; providing, or offering to provide, any service using the Beta Software; using the Beta Software to provide web design or other services to commercial and non- commercial websites; receiving compensation from others for copies or modified copies of the Beta Software; hosting, or offering to host, the Beta Software, on any basis; receiving compensation for any service that uses the Beta Software, including support services
WoWRoster.net shall have the right to determine, in its sole discretion, whether a use is a commercial use or non-personal use
WoWRoster.net owns all rights, title and interest in and to the Beta Software
All rights not expressly granted to you are retained by WoWRoster.net
Your use shall be in accordance with applicable restrictions concerning privacy and intellectual property rights

by **Jalandar** » Sun Dec 24, 2006 5:09 pm

The way I read it, he is allowed to do it for his own use, just not distribute it.

That is all he is trying to do, and get help doing.

I understand the desire to keep people from distributing derived versions until the current one is final, but surely you don't mean to say that you interpret the license to mean that we can't privately do that?

by **zanix** » Sun Dec 24, 2006 5:20 pm

Yeah, I think you are right, he is just trying to make it work in nuke perhaps without knowing that is is in fact not a nuke module

by **Anaxent** » Sun Dec 24, 2006 5:46 pm

zanix wrote:Yeah, I think you are right, he is just trying to make it work in nuke perhaps without knowing that is is in fact not a nuke module

Ok then exuse my reactions then as i do not mean to come accross being a bad guy(I really am nice). I just want to make sure all of us here understand all the guide lines that are put in place.

by **Scatmanicus** » Mon Dec 25, 2006 11:53 am

No matter what the guidelines say or don't say, it is not advisable to try and get Roster to work within the phpNuke CMS system. Take it from someone who has tried and, to a point, has succeeded in such an integration. BUT...you knew there was a 'but' didn't you, but... the major problem is addons. In some cases, you simply cannot get addons to either work or work properly. So what I have done is to setup Roster separately from my phpNuke and then just link to it from my home page just like any other phpNuke module. I modified the header and footer for my Roster to match my website design.

Take it from someone who knows...it works better this way!

by **Asawako** » Tue Dec 26, 2006 3:57 am

I spent several days working on it to get it to work, and while reading the forums today, saw the post by Scatmanicus. Dagnabbit, his solution is so simple its aggrivating. I only had to change 2 lines of code, versus editing several files to get this to work on my test server. Many props Scatmanicus!!! If you are ever in S.Korea (not like you have that on your list of places to visit before you die) I will treat you to the biggest steak they have at Outback, and drown you in beer.

/slaps himself and grumbles something about forest and trees

by **Drazzilb** » Tue Dec 26, 2006 1:00 pm

What changes were made? Is it possable to have the files that you edited to be uploaded or just copy and paste the changes so that we can see. Thanks.

by **Asawako** » Tue Dec 26, 2006 11:00 pm

The only changes I made was in phpNuke site, not in the roster, it worked fine, but after fooling with it some more, you can get it to work by just creating a custom block that calls roster (remember you don't want to install WoWRoster under modules, just within your site).

IE:

Code: Select all: <?php /************************************************/ /* PHP-NUKE: Roster Block */ /* =========================== */ /************************************************/ if (eregi("block-Roster.php",$_SERVER['PHP_SELF'])) { Header("Location: index.php"); die(); } $content .= "<center><br>"; $content .= "<center><a href=\"http://marconus.com/Sanctuary/Roster/index.php\"><b>Roster</b></a></center><br>"; ?>

I didn't tailor the header and footer yet, cosmetic things can wait till final release.

by **Anaxent** » Wed Dec 27, 2006 12:31 am

how about this, since I port roster to dragonfly every release and dragonflycms is alot like php-nuke... as soon as we get 1.7.2 released i will port roster to DF and to php-nuke. I was thinking of porting it for php fussion though so please let me know if there are any diffrences in them.

by **Asawako** » Wed Dec 27, 2006 12:49 am

Some people are just better of served if given an installable version of something, all of my tweaking comes from trial and error, and having a test server along with a production one. I'd help ya with testing and such Anaxent. I just don't feel confident enough to make a packaged product.

by **sedrikk** » Wed Dec 27, 2006 1:45 am

Anaxent wrote:how about this, since I port roster to dragonfly every release and dragonflycms is alot like php-nuke... as soon as we get 1.7.2 released i will port roster to DF and to php-nuke. I was thinking of porting it for php fussion though so please let me know if there are any diffrences in them.

That would be awesome.

by **DrSuSE** » Wed Dec 27, 2006 9:11 am

Anaxent wrote:how about this, since I port roster to dragonfly every release and dragonflycms is alot like php-nuke... as soon as we get 1.7.2 released i will port roster to DF and to php-nuke. I was thinking of porting it for php fussion though so please let me know if there are any diffrences in them.