Manu

This plugin lets your readers run snippets of code directly from your blog.
Simply add a class “run-this” and a lang attribute to the PRE tag surrounding the code. 
The lang attribute should have one of the following values : ada, assembler, awk, bash, bc, brainf**k, c, csharp, cpp, c99, clips, clojure, cobol, clisp, d, erlang, forth, fortran, go, haskell, icon, intercal, java, rhino, javascript, lua, nemerle, nice, ocaml, pascal, perl, php, pike, prolog, python, python3, r, ruby, scala, scheme, smalltalk, tcl, unlambda, vbasic, whitespace
The code is sent over to <a href="http://ideone.com/" rel="nofollow ugc">Ideone</a> to run; results (output, time and language implementation details) are displayed on your blog, in a table underneath the code.
This plugin is free software released under the GNU General Public License.
<h3>Release Notes</h3>
<ul>
<li>
This plugin depends on the <a href="https://wordpress.org/extend/plugins/wp-syntax/" rel="ugc">WP-Syntax plugin</a> being installed and activated.
</li>
<li>
This plugin uses CORS to send the code source accross to a different domain, recent browsers should work fine (See <a href="http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#Browser_support" rel="nofollow ugc">Browser support</a>)
</li>
<li>
This plugin uses jQuery, which is also included in the plugin archive
</li>
<li>
This plugin relies on Ideone web services API (http://ideone.com/api)
</li>
<li>
This is an alpha release, please send bug reports to runthis.plugin@gmail.com
</li>
</ul>

Run This!

This plugin lets your readers run snippets of code directly from your blog.

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!

Run This! vs WP Maximum Execution Time Exceeded