zCMS [PHP, OOP, Phoenix, Secure]

Jonteh when i get vip to users why do they get the "fieldlist" on the client they cant sign on

I can't login xd.

Btw if anyone wants a good cms, use brickphp.

Quote:

---

Originally Posted by azaidi

I can't login xd.

Btw if anyone wants a good cms, use brickphp.

---

Not finished, but quite good.

Quote:

---

Originally Posted by Wupz0r

Not finished, but quite good.

---

Not finished, but still probably the best cms released in this section.....


Anyways, why don't you guys use ubercms, just fix the exploits and boom, it's actually kinda good...

Quote:

---

Originally Posted by Law

Not finished, but still probably the best cms released in this section.....


Anyways, why don't you guys use ubercms, just fix the exploits and boom, it's actually kinda good...

---

Did you look at the minimail?
I'll send you 100 messages on your hotel

Have fun with 121 queries...

Quote:

---

Originally Posted by joopie

Did you look at the minimail?
I'll send you 100 messages on your hotel

Have fun with 121 queries...

---

yeah thats fucked up but if you fix that + exploits + mysqli its good :D

Quote:

---

Originally Posted by joopie

Did you look at the minimail?
I'll send you 100 messages on your hotel

Have fun with 121 queries...

---

I never use minimail anyways, but it is easily removed :p

Quote:

---

Originally Posted by Neonish

but why use a uberdb when phoenix server wont connect without phoenixsql

---

Its based on uber, so based on his databse. Everybody knows Aaron is lazy.

Jonteh when i get vip to users why do they get the "fieldlist" on the client they cant sign on Anyone?

Notice: Undefined index: HTTP_CF_CONNECTING_IP in D:\HoloMAM\Desktop\Xampp\htdocs\zCMA\global.php on line 21
Title: Table 'uberdb.user_stats' doesn't exist
Text: Table 'uberdb.user_stats' doesn't exist :((

Quote:

---

Originally Posted by Robloxz

Notice: Undefined index: HTTP_CF_CONNECTING_IP in D:\HoloMAM\Desktop\Xampp\htdocs\zCMA\global.php on line 21
Title: Table 'uberdb.user_stats' doesn't exist
Text: Table 'uberdb.user_stats' doesn't exist :((

---

People have been complaining about getting hacked whilst using this, so I wouldn't recommend it. ;3

Quote:

---

Originally Posted by davidaap

yeah thats fucked up but if you fix that + exploits + mysqli its good :D

---

There's nothing wrong with using MySQL aslong as you filter all input. Personally, I've started using MySQLi for the security functionalities(binding) it has, unlike others such as Cobe who just use it like if it was an object-oriented style of MySQL and don't use all of its potential.

Quote:

---

Originally Posted by Kryptos

There's nothing wrong with using MySQL aslong as you filter all input. Personally, I've started using MySQLi for the security functionalities(binding) it has, unlike others such as Cobe who just use it like if it was an object-oriented style of MySQL and don't use all of its potential.

---

What do you mean by binding? Like pre-pairing MySQL Queries?

If you control the amount of queries being run at one time. You don't need to enhance the way you code your queries or how MySQL operates and obviously it matters how you create the queries..Learn more about caching in general and such to keep the systems running cooler then the breeze :)

Quote:

---

Originally Posted by Matthew

What do you mean by binding? Like pre-pairing MySQL Queries?

---

No, if you've seen Cobe's MySQLi class, you could see he prepares the query before executing, right?

Well, he doesn't really have a reason to prepare the query, since he isn't doing any further operations to the statement.
He should just do execute() and it'd be fine.

By binding I mean binding the parameters.

Example:

PHP Code:

---

<?php
$mysqli = new mysqli('localhost', 'my_user', 'my_password', 'my_database');

$stmt = $mysqli->prepare("INSERT INTO users VALUES (?, ?, ?, ?, ?)");
$stmt->bind_param('isssi', $id, $username, $password, $email, $credits);

$id = 1;
$username = "Kryptos";
$password = "783749374035RJFFMRMCUBRR894579";
$email = "kryptos@yopimpdaddy.com";
$credits = 1337;

$stmt->execute();

printf("%i Row inserted.\n", $stmt->affected_rows);

$stmt->close();

---

Quote:

---

Originally Posted by Kryptos

No, if you've seen Cobe's MySQLi class, you could see he prepares the query before executing, right?

Well, he doesn't really have a reason to prepare the query, since he isn't doing any further operations to the statement.
He should just do execute() and it'd be fine.

By binding I mean binding the parameters.

Example:

PHP Code:

---

<?php
$mysqli = new mysqli('localhost', 'my_user', 'my_password', 'my_database');

$stmt = $mysqli->prepare("INSERT INTO users VALUES (?, ?, ?, ?, ?)");
$stmt->bind_param('isssi', $id, $username, $password, $email, $credits);

$id = 1;
$username = "Kryptos";
$password = "783749374035RJFFMRMCUBRR894579";
$email = "kryptos@yopimpdaddy.com";
$credits = 1337;

$stmt->execute();

printf("%i Row inserted.\n", $stmt->affected_rows);

$stmt->close();

---

---

My problem is that I over think things, how are you supposed to know how many params they define?

Quote:

---

Originally Posted by Makarov

My problem is that I over think things, how are you supposed to know how many params they define?

---

It's pretty complicated to explain, google it up.

Quote:

---

Originally Posted by Kryptos

It's pretty complicated to explain, google it up.

---

It's why I never tackled it at the start. I've been reading up on a developer's class, seems liable.

Quote:

---

Originally Posted by Makarov

My problem is that I over think things, how are you supposed to know how many params they define?

---

PHP: func_get_args - Manual :sleep:

Quote:

---

Originally Posted by XenoGFX

If you control the amount of queries being run at one time. You don't need to enhance the way you code your queries or how MySQL operates and obviously it matters how you create the queries..Learn more about caching in general and such to keep the systems running cooler then the breeze :)

---

After doing some reseasch, it almost doesn't matter how manny queries you do.

I runned 200 queries and refreshed it for like 10 min.

There was no overload in the mysql server and it didn't slow down the load time, Thank you

Quote:

---

Originally Posted by joopie

After doing some reseasch, it almost doesn't matter how manny queries you do.

---

Where did you get that idea from?

Quote:

---

Originally Posted by Kryptos

Where did you get that idea from?

---

I tested it?

100 write queries
100 read queries

Without overloading the server:):

I don't think you fully understand. Unless you have an SSD drive, The HDD is the slowest component inside your computer/server. And where is MySQL data read/written to? Yeah, your disk. Therefore MySQL (unless on a SSD) will become a bottle neck in any application. But even on an SSD it can slow down during transitions.

You should cache everything you can - when you can. Memory is faster than reading from the HDD. You also want MySQL to do more important tasks than re-query everything on a page load.

It's logical sense, also the less reading/writing a HDD has to do the longer life span it has.

Therefore caching is both the best, cheapest and most scalable solution.

Also to add, that's 200 queries. Let's try over 1000 per second.. and lets see what happens then..

Less queries the faster the site is? ;3

Quote:

---

Originally Posted by Jupos

Less queries the faster the site is? ;3

---

Less queries, less load on the mysql server...

Quote:

---

Originally Posted by Matthew

I don't think you fully understand. Unless you have an SSD drive, The HDD is the slowest component inside your computer/server. And where is MySQL data read/written to? Yeah, your disk. Therefore MySQL (unless on a SSD) will become a bottle neck in any application. But even on an SSD it can slow down during transitions.

You should cache everything you can - when you can. Memory is faster than reading from the HDD. You also want MySQL to do more important tasks than re-query everything on a page load.

It's logical sense, also the less reading/writing a HDD has to do the longer life span it has.

Therefore caching is both the best, cheapest and most scalable solution.

Also to add, that's 200 queries. Let's try over 1000 per second.. and lets see what happens then..

---

Raid 0 (HDD):

Code:

---

1 => 0.360518 sec
2 => 0.630954 sec
3 => 0.367923 sec
4 => 0.634839 sec
5 => 0.36757 sec
6 => 0.627775 sec
7 => 0.368542 sec
8 => 0.642663 sec
9 => 0.366623 sec
10 => 0.659323 sec
------------------
Total: 5.02673 sec
Queries: 10000

---

It isn't that bad.
1000 queries per page:ott1: