Posts by reitbrud

    Hello!

    Thanks for that.


    But that is all what i still know how to configure my max values aso.


    I want to change per Domain max_execution_time Setting on runtime of code. (PHP ini_set (max_execution_time...)

    That is what i wrote on first Post.


    I use one Domain.

    On this Domain i have set Max Execution time to 60seconds. I need this times to make big sql queries.


    But on one Script i need the execution time set to at about 5 seconds, because I read content from other Website, and if this website isnt reachable or i get no answer i dont want to wait 60seconds to get the max_execution Timeout.


    Maybe my first post was written not clearly.


    Nuxwin: OK that I also checked that ini_set doesnt work. But is there a possibility that I can change the configuration of PHP (I USE also PHP Switcher) to use ini_set?


    Thanks.


    I hope you can help me.

    Hello i have set the max_execution Time of PHP to a high level, because some programms on my Web Software can need about 60Seconds to finish the requests.


    But on one Site i need to lower the execution time to about 10Secs.


    It is why on this special site i do a request to another Server, and if this Server is not reachable the request will wait the whole 60Seconds, and Browser hangs so long.


    ini_set('max_execution_time') doesnt work.


    Thanks a lot


    (Sorry for bad english)

    The plugin will accept PHP version layout as implemented by Debian. Debian make use of a fixed layout for multi PHP versions support. So yes, with the new PhpSwitcher plugin version, you should be able to just rerun the php_manager --auto-setup <version> command to add the new version and make it available for customers. I'll see if I can add a trigger through the PhpSwitcher GUI for auto discovering of new versions.


    That is another story. You should be able to make use of Beta/RC versions if these are packaged by Ondřej Surý. Don't forget that for the self-compiled versions, we need provide a set of patches for each PHP versions as the default PHP installation layout doesn't fit good for Debian (Multiarch support, FTBFS issues and so on...). You also surely know the issues with patches: They need sometime (to not say often) be refreshed... This is due to fact that a fix provided by a patch can be integrated to PHP upstream source, or that there was too many changes in upstream source, making the patches unapplyable...

    One Question, i would need the PHP-Switcher.

    Should i use it or should i wait for new I-MSCP Update.


    If i Use PHP Switcher can i install new coming I-MSCP Update (1.6 or 2.0) which i can convert the PHP-Switcher Versions to integrated Versions?


    Thanks

    @longsyee


    You should really avoid changing the SQL_MODE... For instance, ONLY_FULL_GROUP_BY isn't compatible with i-MSCP because we rely on NON standard SQL. This will be solved in near future.


    See also: https://dev.mysql.com/doc/refm…en/group-by-handling.html

    Hello YES but this is the standard Setting after UPGRADE to I-MSCP 1.5.3 and makes also on my Software Problems!

    Pls check if I-MSCP code is working correct if everybody gets this Settings after Upgrade to 1.5.3.


    Thanks.

    Hallo ich habe das letsencrypt Plugin vor einigen Wochen auf Version 3.4.2 upgedated, und sehe gerade dass dieses die Zertifikate nicht mehr automatisch erneuert.


    Das blau eingerahmte habe ich gerade eben per Hand aktualisiert über den erneuern Button, ohne Probleme.


    Das orange eingefärbte sollte eigentlich schon lange automatisch aktualisiert worden sein, wurde es aber nicht.


    Die Beschränkung von 20 Zertifikaten / Woche wird auch nicht überschritten.

    Plugins aktualisieren habe ich auch schon gedrückt etc.


    Bitte um Hilfe