• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

[BUG] php max_execution_time

DJSnoopy

New Pleskian
Hiho Odin Team.

During my current test installation i think i found a small bug.
If you set up max_execution_time for php and set it to default (60) it´s set to 30 in the php.ini
Problem here is the default in the ini is 30 and the panel seems not to save a value if default selected.

Steps to reproduce:
- create three serviceplans with 30, default and 120 max_execution_time
- use a phpinfo script to see which values are active for the test site.
- 30 goes to 30
- 60 goes to 30
- 120 goes to 120

ways to fix:
i´ve update every php.ini for the php handlers and set the max_execution_time to 60
so the panel drop downs match the ini files.
 
Back
Top