DRUPAL LOGIN BLOCK SHOWING TWICE INSTALL

Or you can install this handy plugin from JoomlaWorks which covers all Joomla versions from 1.5 to 3.x and extends/improves the built-in changes introduced in Joomla v3.6 (as stated above). Just have a look at the 2 blocks starting with 'Exclude the following paths.' below in the Varnish configurations. Since Joomla v3.6, all you need to do to have Joomla play nicely with Varnish is add your exclusion points (URLs). Once a user logs into WordPress, Varnish will shut down its caching for that user. WordPress and WooCommerce are fully supported by these configurations. You can even exclude the domains you don't want to cache if you're looking to use it in a multi-site setup.

If your CMS provides a way to add these two requirements, then you can use this configuration to speed up your site or entire server. This configuration requires an HTTP Header and a user cookie to identify if a user is logged in a site, in order to bypass caching overall (see how it's done for Joomla & WordPress). You can safely increase this to 300 sec (or more) for less busier sites or drop it to 60 sec or even 30 sec for high traffic sites. IMPORTANT: The following setup assumes a 180 sec (3 minute) cache time for cacheable content that does not have the correct cache-control HTTP headers. USE: Replace the contents of the main Varnish configuration file located in /etc/varnish/default.vcl (root server access required - obviously) with the contents of the configuration you'll use (depending on your Varnish version) from the 2 examples provided below. IMPORTANT: Read this before implementing one of the configuration files below (for either Varnish 3.x or 4.x+). The perfect Varnish configuration for WordPress, Joomla, Drupal & other (common) CMS based websites Updated on December 15th, 2021

Drupal login block showing twice