Ronald Huereca

weweave

Skip page reloads and separate error screens when posting comments. Ajaxify Comments hooks into your native WordPress comment system and allows comment posting without a page reload. Lazy loading comments is also supported, which can help speed up your page load time.
<h3>TLDR</h3>
<a href="https://docs.dlxplugins.com/v/ajaxify-comments/first-time-users/getting-started" rel="nofollow ugc">Getting Started</a> | <a href="https://github.com/sponsors/DLXPlugins" rel="nofollow ugc">Sponsor Us</a> | <a href="https://dlxplugins.com/plugins/ajaxify-comments" rel="nofollow ugc">Ajaxify Home</a>
Ajaxify Comments hooks into your theme and improves the usability of the comment form by validating and adding comments without the need of page reloads. Users can remain on the page and interact with new comments as they’re posted. This plugin also supports lazy loading of comments, which can help speed up your page load time.
<h3>Introduction</h3>
When submitting the comment form, WordPress by default reloads the entire page. This can be a disorienting experience for the user. In the case of errors in the comment (invalid email, duplicate comment, empty comment), these often require a separate error screen and the user has to use the back button to edit their comment. This can be a frustrating experience for the user. Adding to that, comments can be resource intensive, and can slow down your page load time.
With Ajaxify Comments, comments are posted without a page reload. If there are errors, the error message is shown immediately, so the user can correct their comment.
Ajaxify Comments also comes with lazy loading of the comments section. For a page with a lot of comments, this can speed things up considerably. You can load comments when the DOM is ready or when the comment section is scrolled into view.
Moreover this plugin includes an option to automatically refresh the comments on the current page while the user stays on your page without requiring a page reload. This can be helpful in busy comment sections where reply response time is important.
<h3>Quick Resource Links</h3>
Here are some helpful links to help you get started with Ajaxify Comments (docs):
<ol>
<li><a href="https://docs.dlxplugins.com/v/ajaxify-comments/first-time-users/getting-started" rel="nofollow ugc">Getting Started Guide</a></li>
<li><a href="https://docs.dlxplugins.com/v/ajaxify-comments/advanced-topics/lazy-loading-comments" rel="nofollow ugc">Lazy Loading Comments</a></li>
<li><a href="https://docs.dlxplugins.com/v/ajaxify-comments/first-time-users/menu-helper" rel="nofollow ugc">Menu Helper and Selectors</a></li>
<li><a href="https://docs.dlxplugins.com/v/ajaxify-comments/advanced-topics/wpml-and-translations" rel="nofollow ugc">Translating Using WPML</a></li>
</ol>
<h3>Requirements and Compatibility</h3>
Please use the native WordPress comment system with Ajaxify Comments.
The plugin has integrations with:
<ol>
<li><a href="https://wordpress.org/plugins/confetti/" rel="ugc">Confetti</a> – Show confetti when a comment is posted.</li>
<li><a href="https://wordpress.org/plugins/simple-comment-editing/" rel="ugc">Comment Edit Core</a> – Allow users to edit their comments.</li>
<li><a href="https://dlxplugins.com/plugins/comment-edit-pro/" rel="nofollow ugc">Comment Edit Pro</a> – Add numerous utilities and automations to your comment section.</li>
</ol>
The following themes are supported out of the box:
<ol>
<li><a href="https://wordpress.org/themes/astra/" rel="ugc">Astra</a></li>
<li><a href="https://wordpress.org/themes/blocksy/" rel="ugc">Blocksy</a></li>
<li>Divi</li>
<li>Genesis</li>
<li><a href="https://wordpress.org/themes/ollie/" rel="ugc">Ollie</a></li>
<li><a href="https://wordpress.org/themes/generatepress/" rel="ugc">GeneratePress</a></li>
<li><a href="https://wordpress.org/themes/neve/" rel="ugc">Neve</a></li>
<li>Twenty Ten – Twenty Twenty Three</li>
</ol>
Ajaxify Comments should be compatible with most block themes. If <a href="https://docs.dlxplugins.com/v/ajaxify-comments/first-time-users/menu-helper" rel="nofollow ugc">Menu Helper</a> can’t find the selectors, please leave a support request.
<h3>Technical Note</h3>
Since the plugin hooks into the theme on client-side to intercept the comment form submit process, and to add new comments without reloading the page, the plugin needs to access the DOM nodes using jQuery selectors. The plugin comes with default values for these selectors that were successfully tested with WordPress’ default themes “Twenty Ten”, “Twenty Eleven”, “Twenty Twelve”, “Twenty Thirteen”, “Twenty Fourteen”, “Twenty Fifteen”, “Twenty Sixteen”. If required, the selectors can be customized to match your theme in the plugin’s settings.
<blockquote>
<a href="https://docs.dlxplugins.com/v/ajaxify-comments/first-time-users/menu-helper" rel="nofollow ugc">Menu Helper</a> is available to help you find the theme’s selectors.
</blockquote>
<h3>Features</h3>
Ajaxify Comments is community supported. If you would like to add or change anything about the plugin, please consider assisting with the development on <a href="https://github.com/DLXPlugins/wp-ajaxify-comments" rel="nofollow ugc">GitHub</a>.
<ul>
<li>Post comments without a page reload.</li>
<li>Show error messages without a page reload.</li>
<li>Lazy load comments, compatible with most themes, including block theme and inline loading.</li>
<li>Automatically refresh comments.</li>
<li>Comment form validation.</li>
<li>Support for pages with multiple comment forms.</li>
<li>Support for threaded and moderated comments.</li>
<li>Compatible with most spam plugins.</li>
<li>Menu Helper to help you find the right selectors for your theme.</li>
<li>Appearance preview to see how the plugin will look on your site.</li>
<li>Simulate Ajaxify Comments enabled or disabled for testing and to compare the difference.</li>
<li>Translate and customize the default WordPress comment messages.</li>
</ul>
<h3>Questions/Help?</h3>
Please use the <a href="https://wordpress.org/support/plugin/wp-ajaxify-comments" rel="ugc">support forum</a> to ask questions or to report issues. If you don’t want to create an account to leave a support request, please use <a href="https://dlxplugins.com/support/" rel="nofollow ugc">my support form</a>.
<blockquote>
Most questions can be resolved by checking out our docs site. <a href="https://docs.dlxplugins.com/v/ajaxify-comments" rel="nofollow ugc">https://docs.dlxplugins.com/v/ajaxify-comments</a> – the Search is AI, so it should be able to find what you’re looking for.
</blockquote>
<h3>Credits</h3>
This plugin was initially developed by Jan Jonas starting in 2012. Company <a href="https://weweave.net/" rel="nofollow ugc">weweave</a> maintained the plugin from 2014-2022. The plugin is currently supported by Ronald Huereca of <a href="https://dlxplugins.com" rel="nofollow ugc">DLX Plugins</a>.

Ajaxify Comments – Ajax and Lazy Loading Comments

This has always been a great plugin. It always worked just fine, even if weweave (the previous owners) stopped maintaining and developing it.

Since DLX plugins took over, it got even better

There’s been a lot of admin UI improvements, and Ronald has showed to be incredibly responsive to implement small additional features that can make life easier.

Sent him a feature request, and was incredibly glad to see that he also judged that it was a useful thing to implement. It took him less than 48h to push it live!

Just excellent

Ajaxify Comments speeds up your comment section, allowing for lazy loading comments, instant comment posting, and seamless success and error messages.

launchinteractive

Development for this plugin is now done on <a href="https://github.com/Launch-Interactive/Merge-Minify-Refresh" rel="nofollow ugc">GitHub</a>. Pull requests are welcome.
This plugin merges/concatenates Cascading Style Sheets & Javascript files into groups. It then minifies the generated files using Minify (for CSS) and Google Closure (for JS – fallback to Minify when not available). Minification is done via WP-Cron so that it doesn’t slow down the website. When JS or CSS changes files are re-processed. No need to empty cache!
Inspired by <a href="https://wordpress.org/plugins/minqueue/" rel="ugc">MinQueue</a> and <a href="https://wordpress.org/plugins/dependency-minification" rel="ugc">Dependency Minification</a> plugins.
Minification by <a href="https://github.com/matthiasmullie/minify" rel="nofollow ugc">Minify</a> and <a href="https://developers.google.com/closure/" rel="nofollow ugc">Google Closure</a>
In order to ensure fast loading times it’s recommended to set long expiry dates for CSS and JS as well as make sure gzip or deflate is on.
Version 1.10 added should_mmr filter which allows developers to disable MMR when needed. You could use this to disable MMR for certain WordPress roles or with some Page Builders. Three new plugins have been created that utilise this: 
<a href="https://wordpress.org/plugins/mmr-disable-for-divi" rel="ugc">Merge + Minify + Refresh Check DIVI</a>, <a href="https://wordpress.org/plugins/mmr-disable-for-visual-composer-editor" rel="ugc">Merge + Minify + Refresh Check Visual Composer</a> and <a href="https://wordpress.org/plugins/mmr-disable-for-beaver-builder-editor" rel="ugc">Merge + Minify + Refresh Check Beaver Builder</a>. Please install these when required.
Version 1.6 added support for HTTP2 Server Push to further speed up your requests (thanks to <a href="https://www.slightfuture.com" rel="nofollow ugc">Daniel Aleksandersen</a>).
Version 1.6.9 added the ability to specify the cache directory. Set MMR_CACHE_DIR & MMR_CACHE_URL constants in wp-config.php. MMR_CACHE_DIR must be full server path and MMR_CACHE_URL must be absolute URL for this to work correctly (thanks to <a href="https://www.slightfuture.com" rel="nofollow ugc">Daniel Aleksandersen</a>).
Version 1.6.11 added the ability to specify seperate cache urls for javascript and CSS. Use MMR_JS_CACHE_URL & MMR_CSS_CACHE_URL to replace MMR_CACHE_URL.
Version 1.7.0 added the ability to generate .css.gz & .js.gz files. Your webserver may need to be configured to use these files. Here is how to use these files in Apache (mod_rewrite, mod_deflate and mod_headers need to be enabled):
<pre><code><IfModule mod_rewrite.c>
 <IfModule mod_deflate.c>
 <IfModule mod_headers.c>
&#35;Serve gzip compressed CSS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

&#35;Serve gzip compressed JS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

&#35;Serve correct content types, and prevent mod_deflate double gzip.
RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1,E=is_gzip:1]
RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1,E=is_gzip:1]
Header set Content-Encoding "gzip" env=is_gzip
 </IfModule>
 </IfModule>
</IfModule>
</code></pre>
Version 1.8.8 added a “merge_minify_refresh_done” hook that fires when JS or CSS has changed.
Version 1.11 added two new constants: 
MMR_USE_CLOSURE – allows Google Closure Javascript minification to be disabled. 
MMR_REMOVE_EXPIRED – disables removing expired files.
Version 1.13 added two new filters which can be used to exclude specific files: 
mmr_ignored_css_sources 
mmr_ingnored_js_sources 
Version 1.13 also automatically moves the WordPress inline styles to a global stylesheet which it then enqueues.
Version 1.14.3 added two new filters which can be used to modify the output before it gets saved: 
modify_css_output_before_save 
modify_js_output_before_save
Note Installing this plugin on a server with the eAccellerator module installed has the potential to break as Minify uses anonymous functions which return NULL. <a href="https://github.com/eaccelerator/eaccelerator/issues/12" rel="nofollow ugc">View eAccellerator Issue Thread</a>
Features
<ul>
<li>Merges JS and CSS files to reduce the number of HTTP requests</li>
<li>Handles scripts loaded in the header & footer</li>
<li>Compatible with localised scripts</li>
<li>Creates WP-Cron for minification as this can take some time to complete</li>
<li>Minifies JS with Google Closure (requires php exec) with fallback to Minify</li>
<li>Minifies CSS with Minify</li>
<li>Failed minification doesn’t break the site. Visitors will instead only see the merged results</li>
<li>Stores Assets in /wp-content/mmr/ folder</li>
<li>Uses last modified date in filename so any changes to JS or CSS automatically get re-processed and downloaded on browser refresh</li>
<li>View status of merge and minify on settings page in WordPress admin</li>
<li>Option to enable http2 server push (thanks to <a href="https://www.slightfuture.com" rel="nofollow ugc">Daniel Aleksandersen</a>)</li>
<li>Option to enable output buffering for compatibility and so footer scripts can be HTTP2 pushed</li>
<li>Ability to turn off minification</li>
<li>Ability to turn off concatenation</li>
<li>Ability to manually ignore scripts or css</li>
<li>Ignores conditional scripts and styles</li>
<li>Ability to specify cache directories</li>
<li>Ability to generate .css.gz & .js.gz files (Thanks to Marcus Svensson)</li>
<li>Works with WordPress Multisite</li>
</ul>

Merge + Minify + Refresh

I just tested this on localhost not on a production site but its seems like it works like a charm and does its jobs really well.

So far i can't see any script or style conflicts, so i guess on a good codebase (probably when all scripts and styles are integrated via WordPress enqueue API) this plugin just works.

Im gonna test the impact on a live website but i think this is gonna be quite relevant.

Seems really powerfull

Great plugin. Works as expected.
Thank you.

Great plugin.

Merges/Concatenates CSS & Javascript and then minifies using Minify (for CSS) and Google Closure (for JS with Minify as a fallback).

Ajaxify Comments – Ajax and Lazy Loading Comments vs Merge + Minify + Refresh