ISPConfig 3.0.0.5 Beta Released

Today i've created a Dutch language file set for ISPConfig 3.
I'll send it to you by email,

Kind regards,

Click to expand...

Can I also start translating? Is english translation complete (all the phrases or some descriptions like eg. OK_BUTTON_SUBMIT )?
I want to start as soon as it is possible , because you said the release date will be also soon and I want to be prepared . Of course I will send it to you, and add it to some release.

Hi, with the translation from Hans I found several missing parts like headers in the menu that are still hard coded in english. I will fix this until the next beta and add the missing sentences to the language files. It might be better if you wait until the next beta release with the translation.

i played around with 3.0.0.2 beta a while back, but i would like to see some screen shots of this one if anyone can post a few. i will try and install 3.0.0.5 later this week(end) to get a feel, and do some testing

Hi, with the translation from Hans I found several missing parts like headers in the menu that are still hard coded in english. I will fix this until the next beta and add the missing sentences to the language files. It might be better if you wait until the next beta release with the translation.

@Gimly: afaik it is more or less on a todo list but it won't be too easy since the architecture is completely difrferent between both systems. But Falko / Till already stated that the plan a kind of migration script.

On each server, you will have to install the php packages (except the mod_php package, which is only needed if apache is installed too), as ISPConfig requires them for local processing. Then install only the services that you want on the server. The server can be divided in the following parts:

There is a updated version in SVN that fixes several bugs related to multiserver use.

Also, make sure that you use the hostname and not IP address to connect to the mysql server. MySQL has problems when the IP is used in the permission tables. If you run the setup in a test enviroment without real assigned hostnames, you can add all hostnames and corresponding IP addresses in the /etc/hosts files of all servers that are part of this setup.

There is a updated version in SVN that fixes several bugs related to multiserver use.

Also, make sure that you use the hostname and not IP address to connect to the mysql server. MySQL has problems when the IP is used in the permission tables. If you run the setup in a test enviroment without real assigned hostnames, you can add all hostnames and corresponding IP addresses in the /etc/hosts files of all servers that are part of this setup.

This is local mydns database or remote, i think it should be local otherwise DNS server with mysql tables on frontend server have no meaning. Because if frontend will be down, DNS will be "down" too. Can i set this some where ?