Bill Erickson

Warning This plugin is no longer supported, and does not always work with the Gutenberg block editor.
I recommend using <a href="https://wordpress.org/plugins/change-last-modified-date/" rel="ugc">Change Last Modified Date</a> instead.
<h4>Summary</h4>
Prevent the modified date from changing when making minor changes to your content.
This plugin adds a checkbox to the Publish box, “Don’t update the modified date”. When checked, saving your post does not update the post modified date.
Minor changes like adding tags or fixing typos won’t bump the modified date.
This plugin will maintain the previous modified date. It does not let you specify a custom modified date.
When you’re ready to publish a major content change, you can uncheck this setting before saving the post.
<h4>Customization</h4>
Your theme will need to use <code>get_the_modified_date()</code> to display the modified date.
This plugin only applies to the <code>post</code> post type by default. You can customize which post types it appears on using the <code>limit_modified_date_post_types</code> filter.
<pre><code>add_filter( 'limit_modified_date_post_types', function( $post_types ) {
 $post_types[] = 'page';
 return $post_types;
});
</code></pre>

Limit Modified Date

Prevent the "modified date" from changing when making minor changes to your content.

Johnnie

<ul>
<li>NOTE: Please read installation instructions. WP Maximum Execution Time Exceeded plugin requires that you complete the website backup process. </li>
</ul>
WP Maximum Execution Time Exceeded is a very simple and effective plugin. If you’re receiving the message “Maximum execution time of 30 seconds exceeded” or “Maximum execution time of 60 seconds exceeded,” this plugin is for you.
A time out means that the process you would like to complete is simply taking longer that the program will allow. The clock needs to be set for a longer time period. To address the problem of maximum execution time exceeded, WordPress Codex offers two solutions. One, edit the .htaccess file and two, edit the php.ini file. This plugin uses the first of the two suggestions. WP Maximum Execution Time Exceeded will add and delete the necessary code to the .htaccess file.
When WP Maximum Execution Time Exceeded is activated after installation, the plugin will write to the .htaccess file. To delete the code, simply deactivate the plugin. There is no administration page.
You do not have to delete the files to remove the code. When you’re ready to rewrite the code to the .htaccess file, simply activate it. This allows you to test your process with a longer timeout. It’s that simple! And of course, this plugin creates no load on your website. It’s so light weight; you’ll never know it’s there.
<ul>
<li>NOTE: All feedback and suggestions are welcome. I am constantly looking for ways to improve and upgrade WP Maximum Execution Time Exceeded. Please contact me with your ideas for a better plugin.</li>
</ul>

WP Maximum Execution Time Exceeded

I know enough to edit .htaccess files but couldn't manage to extend the execution time without creating an Error 500.

One click and this did the job...and taught me how to do it manually in future ;o)

Perfect

Did you receive a message, "Maximum execution time of 30 seconds exceeded?" Not anymore. Just Plug'n-Play. It's that easy!

Limit Modified Date vs WP Maximum Execution Time Exceeded