FTP usernames have to be unique for the whole server as the FTP protocol never verifies by domain, thats independant if you use ispconfig or not. To ensure unique usernames, every username has a prefix. Make sure that you did not remove or modified the prefix.

1) I created new website test1.tld
2) I created new website test2.tld
3) I created FTP user test1 for website test1.tld
4) I created FTP User test2 for website test2.tld
5) I disabled user test1, the path of user test2 does not change.

The path does not change on my systems with 3.0.3 installed. You should recheck this on your server. there is exactly one situation where the path is rewritten for FTP users and thats when a website is assigned to a new client, as this means that the path of the site has been changed and in that case, ispconfig has to remap the FTP user to the new path of this website.

The path does not change on my systems with 3.0.3 installed. You should recheck this on your server. there is exactly one situation where the path is rewritten for FTP users and thats when a website is assigned to a new client, as this means that the path of the site has been changed and in that case, ispconfig has to remap the FTP user to the new path of this website.

Click to expand...

Add a client.
add 2 domains to that client
add 1 ftp user for each domain.

Open filezilla and configure the 2 accounts.

Add a file to domain1.
Disable domain 1

refresh ftp account(filezilla) of domain1, and is connected to domain2.

Tested this with fireftp and it is not reproducable. Site1 remains site1. Deactivating a site can not have a influence on FTP which you can see in the sources. Disabling FTP just removes the vhost file for apache.

Tested this with fireftp and it is not reproducable. Site1 remains site1. Deactivating a site can not have a influence on FTP which you can see in the sources. Disabling FTP just removes the vhost file for apache.

Click to expand...

Yes, you are right i cant reproduce like i say it will.

But one thing is right, that bug really exists, you can bet on that.
Maybe something related auto disable by cron when the site is over traffic.

In my other "bug" is the traffic Limit(status) wont go away, now that "bug" is fixed (24 H later).

My 2 bugs where active during that 24H time, now in not possible to reproduce, you can take your conclusions.