FTP User Disable Feature

Discussion in 'Developers' Forum' started by t-mug, May 13, 2009.

  1. t-mug

    t-mug New Member

    At first glance it should be not be that hard to implement this:


    I think this doesn't break the concept of ISPConfig 2. And it would be surely backward compatible, if all existing users get the box checked.

    Would you integrate this feature, if available as a patch, into ISPConfig 2.x? What do you think about it?
  2. t-mug

    t-mug New Member

    Although the task is really a minor change: one thing makes me a bit confusing.
    Till, how do you distribute an update of the field `doctype_def`, inside the doctype table? It seems that you don't perform db updates during ISPConfig install (update) time, when forms have changed... - so how would this be done?? :confused:

    The other post in this forum ("ISPConfig doctype (form) handling"), regarding to a changed doctype handling from database to filesystem, didn't help me. There is no /home/admispconfig/ispconfig/lib/doctypes/ folder and maybe you've changed the doctype handling again?

    EDIT: Oh - I had never supposed that you delete the comlete db during update. So my grepping after "ALTER TABLE" had no chance there :)
    Last edited: May 14, 2009
  3. t-mug

    t-mug New Member

    One possibility to separate FTP and E-mail for 2.x

    Look into the attachment, if you're in the mood. Otherwise: it's only half the way. In fact, I think, one can change this with similar effort to have FTP users without e-mail as well.

    So instead of a checkbox - like in the attached solution - one could use an option field on the user tab, represented in the db as an char(1) field:
    1. => E-mail only
    2. => FTP & E-mail
    3. => FTP only
    Then: only if the option value is > 1 you would define the /dev/false user directory in the password file. If the value is > 2 you would NOT write into virtualusertable of postfix.
    Backward compabilty: for all already existing users the option '2' could be set. Make that sense?

    Attached Files:

  4. sirrus

    sirrus ISPConfig Developer ISPConfig Developer

    FTP Users

    This patch is quite simple - but it seems to work...

    In my opinion it would be easy to add an additional field for ftp_path too.

    But this should be an addional option (ftp with path) to keep the original functionality.

  5. t-mug

    t-mug New Member

    Almost ready

    I am almost ready with a complete e-mail // FTP separation. Changed only a couple of lines! I will post this to the tipps and tricks section.

    I would deny to hack around on this subject further (like configurable FTP dirs or fully virtual mail users) - too much effort for a falling star ... ;-)

    I think ISPconfig 3 is the real thrill now. I think I'm going to love it, although usability is much more an issue for v3 than for v2 - surprisingly. But that's always the cost of flexibility, if you look closer.
  6. sirrus

    sirrus ISPConfig Developer ISPConfig Developer

    ... ISPCOnfig 3

    ... is a good point - but I think the admin/reseller/customer seperation is not implemented yet...

  7. t-mug

    t-mug New Member

  8. sirrus

    sirrus ISPConfig Developer ISPConfig Developer


    It a totally different approach... I'm a bit confused by the new Admin/Client structure. But I can handle it now :)

    You're right - I'll move to ISPConfig3 - FTP users path can be configured now.

    -> see Version

  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Fully agreed. We tried to find a good path between flexibility and easy usage. I know that some iSPConfig 2 users think that ispconfig 3 is not so easy to use, but thats always the case if you add more features and if the layout of the system changes to achieve this. In ISPConfig 2 everyone complained before that the same features were missing :) So you will never make the product that everone likes...
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    It is implemented. You can select in the customer settings that a customer may have "sub customers" and then he is a reseller.
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    No, thats not possible as ISPConfig 2 uses system users. Changing the FTP path ould also change the path of mailboxes, autoresponders, SSH logins, etc....
  12. sirrus

    sirrus ISPConfig Developer ISPConfig Developer

    Reseller/Client Seperation

    Yes - I've got that point a few days ago. It is confusing - Other systems (including ISPConfig2) seperate this more clearly.

    But otherwise - you can be a subreseller of a master reseller...

    But what happens if I am a subreseller? Would my folder be something like /var/www/client1/client2 ???

  13. till

    till Super Moderator Staff Member ISPConfig Developer

    You can not be a subreseller. The option to have clients is not available then.

    We cana make a copy of the menu point named reseller with a list that shows only clients that have clients if everyone is confused by this.

    Personally I dont like it to dupliacte the same information in two places.

Share This Page