Posts by Nuxwin


    it apears but don´t work(change color)


    The feature is implemented for all level but:


    When you are logged as admin and you switch to the reseller or to the customer interface, and then, you change the color, you cannot see the change because the admin keeps its own layout color. It's same thing for the reseller.


    To resume, when an admin or a reseller switch to another level, they keep their layout color. It's the expected behavior.


    Try to connect with a customer account credential and change the color. You will see change.

    i-MSCP (1.0.1.6) Feature overview - Layout color switcher


    Layout color switcher is now in the bag. Feel free to try it and report any bug you found. You can test it by installing the master branch.


    Thank for interest.







    Note: Still the jQuery UI part to be updated for each Layout color. I'll do it today.

    I do not want the fight and I'm not the boss. You begin stupid fight with stupid words, not me...


    BTW: About DNS editor, I wait to know where I've contradicted you... Definitively, that becomes really annoying to work with you. Daniel, I don't like liars, you know that. About the DNS thread (opened by kika), I've answered before you, and I've say "I'll review this". That all. I don't know if you dream too much... The problem with you is that you are in competition. The result is that you read all my sentences against you. You become paranoid. I'm not a competitor like you Daniel.


    @Delta, ignora-l pe Laurent, el nu a inteles despre ce se vorbea pe aici. A HowTo este necesar si cand este posibil / timp, o sa introduc si compilarea de diferite module / programe, ca si pas optional, lasat la latitudinea adminului.
    @ Laurent please mind your business and ignore this corner. Is not nice what you do, especially is you do not know our language. Google translator sucks big time so .... If i asked a ticket means i do have some plans with that. Was a wish list so please just ignore it!
    @Delta: ticket reopen http://trac.i-mscp.net/ticket/291#comment:5


    I've not to listen daniel! You are not the boss here! Also, my answer is nice. Maybe I don't understand your language but I'm not so stupid...


    BTW: In past we decided to not compile modules but now, you do what you want... Now, when I see how you are working, I'm afraid for the result. I'm really curious how you will be able to manage such thing correctly.


    Breaking News, tichetul a fost inchis pe motivul din cate am inteles eu "nu-i treaba noastra". :s Oh well...


    Hello ;


    Code
    1. Status changed from new to accepted
    2. Severity changed from Hard to Don't know
    3. Summary changed from Slow Loris problem in Apache2 to Security Failure - Slow Loris Denial of Service attack
    4. Priority changed from Major to Normal
    5. Version set to git (master)
    6. Milestone changed from Working to i-MSCP 1.0.1.6 (Beta 6)
    7. Owner changed from Apache2 to nuxwin
    8. As you said, this module is not packaged and must be compiled/installed by hand. We will not integrate such as module as long they are not available in Debian repository. Anyway, a good admin will be able to install the module from upstream sources. I reject this ticket for now.
    9. Thanks for your interest.
    10. comment:4


    Did you read the comment correctly ? --> "nu-i treaba noastra"


    I've never say that. Implementing a setup script that is able to compile external modules either for Apache or for any other thing will make our life hell. It's exactly the same thing for the cband module. Doing this is not impossible but it's a nightmare to handle.