Resolved Disabled PHP "Hosting performance settings management" can be bypassed by using .user.ini or ini_set()

[forgie]

I'm using Plesk and now, after the update we can not modify for example max_execution_time on app runtime using ini_set()

I do understand @Hangover2 use case, but our use case is different and all the vhosts running under the Plesk are using our own app and we do really need to be able to modify for example max_execution_time on app runtime, what is not possible after this update.
Could it be optional so we can chose if we want to generate the configuration using php_admin_value or php_value, so we can than by using ini_set() change for example max_execution_time, or memory_limit or zlib.output_compression ... ?

 

[forgie]

I found this Question - Plesk 18.0.70 Bypass the default PHP performance settings and modifying the panel.ini file solved my problem. Is this option "settings.useAdminValuesForPerformanceSettings" going to stay in panel.ini also in future Plesk versions? Otherwise I would be in trouble.

 

[Sebahat.hadzhi]

@forgie , your custom settings in panel.ini should be preserved and remain unaffected after a Plesk update.

 

[Hangover2]

@forgie Basically you can just activate or disable the feature in the service plan settings under tab "Permissions" => "Show more available permissions":

 

[debizoh]

I'm sorry this may be an outdated topic, but it doesn't seem like I can create a new one, so I'd like to ask my question here.

I read that useAdminValuesForPerformanceSettings
allows me to use .user.ini as before, so I'm trying it, but only the performance settings are filtered out and the contents of .user.ini are not reflected.

The panel has been updated to the latest version, and old customers were still able to override performance settings in .user.ini.
When I updated the Apache directives with the latest panel (with empty content), .user.ini was no longer bypassed.

I have confirmed that performance settings can be changed by granting them in the panel's contract permissions, but they have to be granted to all users again, and the behavior has changed, which is a major problem.

Have other Plesk users been able to bypass this?
I haven't received a satisfactory answer from support, so I'm not sure what to do...

Plesk Obsidian v18.0.74_build1800251204.13 os_RedHat el8
AlmaLinux 8.10 (Cerulean Leopard)