Resetting the max_execution_time caused me great pain

I ask because we use Total Theme
https://themeforest.net/item/total-responsive-multipurpose-wordpress-theme/6339019

The theme needs a max_execution_time of 300 to work properly.

It does not like 180.

It took me over a week to find out your plugin was causing the problem.

• This reply was modified 5 months, 1 week ago by GideonLupine.

Thanks for your message and I apologise that there is a problem.

There is a known issue for a small number of users and I haven’t been able to get to the bottom of it right now, I am in the process of selling a business.

What I have found is that the user’s server is connecting to the API (licensing) server in milliseconds as expected, but somewhere, something, is causing this delay.

There is a workaround at https://speakoutpetitions.com/faqconc/version-5-slows-down-my-plugins-page/

Note the contact request at the bottom for when I solve this.

I think you misunderstood my issue.

Your plugin changed the max_execution_time for my entire WordPress site, and I could not find out where this 180 setting was coming from.

My theme required max_execution_time be set to 300, but no matter what I set .htaccess or php.ini or wp-config.php to, it would not change. It just stayed at 180.

It took me over a week to find the value of 180 was set inside of your plugin.

I just commented out the line in your plugin, and I was able to set the value of max_execution_time again.

You should have your plugin only warn the admin that they need to change max_execution_time. You should not hard code it in the plugin.

Thanks for the update. Can you tell me where you found the max_execution_time hard coded so I can have a look.

Sure:
/var/www/html/website/wp-content/plugins/speakout/includes/csv.php

//ini_set(‘max_execution_time’, 180); // extend maximum execution time

Hah! Thanks for that. That is the free version, I had changed it in the Pro version to 600 seconds, but hadn’t updated it in the free version.

Also, that directive should be moved so that it is only actioned if the CSV file is actually run, not if it is simply being included as part of the plugin.

I am going to fix this in an new release that will come shortly.

Whatever you do, make it so it does not override the server php.ini or wp-config.php.

When I run phpinfo, it will show that value no matter what.

I see your update, and it seems to work.

Using your plugin no longer changes my max_execution_time across the server.

Thanks for the fast response!