Since alot of servers lately that I have seen are over ran with auto composing, I figured I would create something that allows
server owners and their staff to check the compose logs easier than using notepad.
What this does:
Owners put their compose logs in the folder, and go to the index.php page, enter the name of the file, example: sacrifice 2012-9-20.log
Then hit the "Run" buttonNote: if your compose log is huge, this may take some time to insert the data. The script
goes through the file and creates a table based on the name of the file. When its done it spits out a link that enables you to view
the compose log easier (See the first picture).
While on the read.php page, you have the ability to change between any tables currently in that database (which is why you shouldnt use
the default "my" database for this)(See image 1 number 1). You also can change the composer, so its easier to read based on who is
doing the composing (See image 1 number 2). After changing the composer you get a list of their composes with the difference per compose.
(See Image 2).
Setting this up:
Its quite simple to set up.
1. Open the fig.php file and change the following to suit your server.
2. Open the folder you made for this. And put your compose log in there. You can find the log by going to your MsgServer/d_log/MonthFolder/
Inside that folder find your sacrificeYear-Month-Day.log file.
3. Open your browser to the folder you made for this. Example would be [Only registered and activated users can see links. Click Here To Register...]
4. Input the name of the file you put into the folder. Example sacrifice 2012-9-20.log and then hit "Run". Wait for the script to do
its work, and then click on the link the script gives you.
5. Enjoy it
As I said before, if your compose log is huge, this may take a few minutes to run.
While I have tested this to the fullest, I take no responsibility if it screws something up. Use at your own risk
Pictures
[Only registered and activated users can see links. Click Here To Register...]
1. Tables found in the database. Good way of keeping track of your compose logs, just in case you want to let your staff check them.
2. The Composers name. When you change the selected dropdown, it will pull the logs for that user.
[Only registered and activated users can see links. Click Here To Register...]
What it looks like while looking at a characters composes.
[Only registered and activated users can see links. Click Here To Register...]
Make sure the log file is in the directory with the others.
server owners and their staff to check the compose logs easier than using notepad.
What this does:
Owners put their compose logs in the folder, and go to the index.php page, enter the name of the file, example: sacrifice 2012-9-20.log
Then hit the "Run" buttonNote: if your compose log is huge, this may take some time to insert the data. The script
goes through the file and creates a table based on the name of the file. When its done it spits out a link that enables you to view
the compose log easier (See the first picture).
While on the read.php page, you have the ability to change between any tables currently in that database (which is why you shouldnt use
the default "my" database for this)(See image 1 number 1). You also can change the composer, so its easier to read based on who is
doing the composing (See image 1 number 2). After changing the composer you get a list of their composes with the difference per compose.
(See Image 2).
Setting this up:
Its quite simple to set up.
1. Open the fig.php file and change the following to suit your server.
Code:
$host = "127.0.0.1"; //This is the host for your db. Usually 127.0.0.1 or localhost $user = "root"; //This is your db's username $pw = "test"; //This is your db's password $db = "log"; //This is your database
Inside that folder find your sacrificeYear-Month-Day.log file.
3. Open your browser to the folder you made for this. Example would be [Only registered and activated users can see links. Click Here To Register...]
4. Input the name of the file you put into the folder. Example sacrifice 2012-9-20.log and then hit "Run". Wait for the script to do
its work, and then click on the link the script gives you.
5. Enjoy it
As I said before, if your compose log is huge, this may take a few minutes to run.
While I have tested this to the fullest, I take no responsibility if it screws something up. Use at your own risk
Pictures
[Only registered and activated users can see links. Click Here To Register...]
1. Tables found in the database. Good way of keeping track of your compose logs, just in case you want to let your staff check them.
2. The Composers name. When you change the selected dropdown, it will pull the logs for that user.
[Only registered and activated users can see links. Click Here To Register...]
What it looks like while looking at a characters composes.
[Only registered and activated users can see links. Click Here To Register...]
Make sure the log file is in the directory with the others.