Hi well just a little suggestion.

Wouldn't it be nice to can choose two things ...

First the password "complexity" .. It would be very nice
to have the ability to put a password without putting chars AND numbers
even if it's gave a better protection...

Then the number put before or after the database or datatable name, i know that it's necessery for a lot case especially to prevent for using 2 times a db
but for some case for exmple when you want to import data and your former base is called abcde .... well

a good idea would be to put a status to user like super-users or trusted-users which can able them to don't have these 2 "constraints".

What do you think about that

i don't know if it can be understood

1) The password complexity can be disabled in ispcp-lib.php


2) In your ispcp.conf set
then your customers db's are forced to have their id infront like XYZ_superdb

2)
I think edony44 want's to have customers *with* mysql_prefix and customers *w/o* mysql_prefix

AFAIK this is possible, if you set it manually in the database (either only in mysql - withour telling ispcp or change the setting in table sql_databases... (but there ist no "status" - so you have to reanem the database also manually)

/Joxi

joximu Wrote:2)
I think edony44 want's to have customers *with* mysql_prefix and customers *w/o* mysql_prefix

AFAIK this is possible, if you set it manually in the database (either only in mysql - withour telling ispcp or change the setting in table sql_databases... (but there ist no "status" - so you have to reanem the database also manually)

/Joxi

thks your right exemple i want to transfer a website from a server to my new with ispcp .. creating account are so easy ( thks ispcp ) but my database is called DATABASE without any other thinks ,, well moreover , i've
a lot of calling of this database in my website ( no one variable ) so ... i can't make a database in ispcp it's not very convenient, isn't it ?
.

Well, if you are the admin you can do like this:
Set "MYSQL_PREFIX" to no in ispcp.conf, make your database and user for the database, then enable the option again.
This should work.

And next time: use a central file, where you can enter the database connection parameters :-)

/j