Our Scripts Vault contains many game scripts that you can use to create your own game!
' FATAL ERROR: Could not find: /home/usr/public_html/game/modules/game/game.php#0 {main}
Code: [Select]' FATAL ERROR: Could not find: /home/usr/public_html/game/modules/game/game.php#0 {main}I set up the database then put sql in. Edited the config to match. When i load the site i get that error ^. Any idea's why?Posted in the other thread to.
$URI = explode('/',(string) $_SERVER['REQUEST_URI']);
$URI = explode('/',(string) str_replace(dirname($_SERVER['SCRIPT_NAME']),'',$_SERVER['REQUEST_URI']));
I download and check.It was very simple and had very clean coding.Good work.
Just download it and installed, however when i click one of the links i always get an url error:Not FoundThe requested URL /account/login was not found on this server.apache error log:[Sun Jun 28 18:40:37 2009] [error] [client 192.168.0.100] File does not exist: /var/www900/account, referer: http://192.168.0.10:900/My test server runs on port 900, could that cause the trouble in your code ?
Go to the index.php... and try doing putting the following in the beginning:echo "<pre>";print_r($_SERVER['REQUEST_URI']);echo "</pre>";then go to: http://192.168.0.10:900/account/registersee what shows up...Which should be '/account/register'
Array( [1] => account [2] => register)
hmm well, it's loading the index.php and htaccess is working... After line 27 try putting in...echo "<pre>";print_r($URI);echo "</pre>";...to make sure the URI parsing is working.If it's showing an array for /account/register asCode: [Select]Array( [1] => account [2] => register)
Strict Standards: Redefining already defined constructor for class Authenticate in C:\AppServ\www1\includes\authenticate.php on line 18Strict Standards: Non-static method Database::query() should not be called statically, assuming $this from incompatible context in C:\AppServ\www1\includes\settings.php on line 18Strict Standards: Non-static method Database::getResults() should not be called statically, assuming $this from incompatible context in C:\AppServ\www1\includes\settings.php on line 19Strict Standards: Non-static method Database::getType() should not be called statically, assuming $this from incompatible context in C:\AppServ\www1\includes\database.php on line 78
public function query(){
public static function query(){
abstract function authenticate ();
Thus, you define 2 constructors in your class:__construct ()authenticate ()
$_SESSION['cart'][$entity['id']]['quantity']++;
Let me know if you have any other issues. I've noticed there seem to be problems with the in-game links because I set them all locally...ie; <a href="/account/login">login</a> And when you load the framework into a subdirectory, this effectively doesn't work as it tries to load from the root of course. Basic HTML 101 I guess.
<base href="/[sub-directory]/" />
Code: [Select]$_SESSION['cart'][$entity['id']]['quantity']++;
++$_SESSION['cart'][$entity['id']]['quantity'];
Yes, you are right, but I doubt the difference will ever be noticeable. (Unless you are very good with stopwatches)
Quote from: karnedgeCode: [Select]$_SESSION['cart'][$entity['id']]['quantity']++;I've read a few places that ++$something; is faster then $something++;Code: [Select]++$_SESSION['cart'][$entity['id']]['quantity'];If im right someone correct me plz
What you wrote is called "premature optimization". (aka you focus on nonsense instead of writing functional code). In early stage of project it is important to create a design and write. Optimization in this phase consist of using proper date structures and algorithms. Usually when focusing on these details you omit the complex view on application. Sometimes you really try hard to optimize something only to discover that the bottleneck is somewhere else. Remember the rule 80-20 - 20% of code takes 80% of time of program run. If you discover these and optimize them, you speed up the program much more significantly than when you fiddle about with these insignificant details. Maybe you save a few thousandths, but believe me, it's not worth it. Besides, you can always buy better hardware. And even if the application is still causing performance issues, these little changes will not save it.