FTP Access restrictions (bug?)

[Mark_NL]

Hi there,

I don't know if i posted this in the correct forum, just move it otherwise

I just completed a ISPConfig migration to a fresh new server.
It runs on Debian Etch - ISPConfig 2.2.25

Now i've got a complaint from a reseller that he couldn't log in with newly created users on the ftp server. Now i noticed when i logged in with the admin login, i saw "FTP Access" on that account wasn't checked, checked it, and worked.

Logging in as that reseller i noticed the "FTP Access" option wasn't visible in deck 0, whilst i did give him those rights to set ftp access for sites under his account.

so i started debugging, and found out that in the file lib/classes/ispconfig_isp_web.lib.php line 134 says:

if ($reseller["limit_ftp"] != 1) $doc->deck[0]->elements[23]->visible = 0;

but the element 23 is not the "web_ftp" element, it should be element 21

if i hard code element 21 to visible = 1, the ftp access option shows on deck 0 while logging in with the reseller account.

if you print_r($doc->deck[0]); you'll find:

[21] => checkboxField Object
                (
                    [value] => 
                    [css_class] => 
                    [name] => web_ftp
                    [type] => checkboxField
                    [title] => FTP Zugang
                    [language] => de
                    [description] => 
                    [length] => 30
                    [visible] => 1
                    [required] => 0
                    [reg_expression] => 
                    [reg_fehler] => 
                    [search] => 
                )

element 23 is:

[23] => checkboxField Object
                (
                    [value] => 
                    [css_class] => 
                    [name] => web_mysql
                    [type] => checkboxField
                    [title] => MySQL
                    [language] => de
                    [description] => 
                    [length] => 30
                    [visible] => 1
                    [required] => 0
                    [reg_expression] => 
                    [reg_fehler] => 
                    [search] => 
                )

curently element21 is shown depending on $reseller["limit_python"]

bug? or am i missing something here?

Best reagards,
Mark