Hey!

I have two questions.

Question One:
We are a fairly large guild, translated we have close to 500 charaters.
The problem here is that index.php (the one generated by php at least) weighs in at 500KB, because it's showing all members to every who hits the page. Now, for me this is no problem with my 10mbit line, but I've been getting complaints from other ppl who have smaller lines that it takes a long time to load the main page.

My question is this, is there someway I can turn off the memberslist on the main page? I tried removing some php code with any great luck.
Officers in our guild have agreed on *not* to link to the roster before we can fix this issue. A part for that everything works great!

I'd really like it if I could have a clean frontpage with no memberslist showing, then when you clik on roster it would show the memberslist

Question two:
I've been getting some questions with it's possible to show the recipes,formluas,plan and so on that you havn't learnt yet? So ppl can use the page to plan on what they need get.

One last thing, thottbot and wow.ala.. linkings on quest log dosn't seem to return any results.. I dont know if that's a bug or not...

Cheers!

Question one I figured out myself just now..
If anyone else has thought of this, here how I did it:

First of all, u need a new index.php, so i made that
Before u start making a new index.php file, make sure u rename it to main.php

Code: Select all

<?php
require_once( 'settings.php' );
error_reporting(E_ALL &~ (E_NOTICE | E_WARNING));
include_once (ROSTER_BASE.'roster_header.tpl');

include_once (ROSTER_BASE.'memberslist.php');
?>


Notice there is a error reporting line in there:
error_reporting(E_ALL &~ (E_NOTICE | E_WARNING));

That's because without this statement, the new index.php will report a error, but it's not vital as far as I can tell.

Then go into the LIB folder and edit menu.php search for these lines

Code: Select all

<a href="<?php print $roster_conf['roster_dir']; ?>/index.php">
<a href="'.$roster_conf['roster_dir'].'/main.php?s=class">


Both these lines appear right after each other. Replace index.php with main.php In short just do a search and replace in the menu.php file with search for index.php and replace with main.php

And that's it, "job's done"

I still need an answer to that other question!

Cheers!

Why dont you just turn off some of the rows

I know that turning off the profession icons will reduce the amount of sql queries by quite alot

Just turn off most of the columns and your page will shrink in size

We still have almost 500 lines poping up on the frontpage.

With the modifications I made, the frontpage is rather small, just the menu comes up and that works much better.

I thought of something else. For large guilds as ours..
We have some members who havn't played in a wee bit. So I'm thinking, is there a easy what to not show members that havn't been online since xx.xx.06 ??

Still need an answer to the bit about unlearnt skills and proffesions.

crewsader wrote:Still need an answer to the bit about unlearnt skills and proffesions.

No, there is no way, unless some one builds a roster addon for that

crewsader wrote:So I'm thinking, is there a easy what to not show members that havn't been online since xx.xx.06 ??

Well, easy...I'm not sure

Edit the main SQL query in memberslist.php
I'm not too good with SQL queries though

I'm thinking of trying something like this:

WHERE (lastOnline AFTER "2006-02-01")

zanix wrote:

crewsader wrote:Still need an answer to the bit about unlearnt skills and proffesions.

No, there is no way, unless some one builds a roster addon for that

The obvious challenge here is who is going to go and CREATE AND MAINTAIN a very large database of every recipe, plan, etc. to achieve this? The Thottbot's and Allakhazam's of the world struggle to do this well even with thousands of use contributions.

Once you get past then you'll people saying "Oh, don't show me things I haven't learnt that are grey or green to me" or "Show me everything but I don't care about Cooking" etc.

All in all there's a massive amount of initial and ongoing work involved that is most definitely not within the scope of what we do with the WoW Roster.

crewsader wrote:WHERE (lastOnline AFTER "2006-02-01")

Try this instead

Code: Select all

SELECT * FROM `members` where `last_online`>= '2006-02-01'

I'm not too sure "AFTER" is a vailid SQL Keyword.