Forum Replies Created

Viewing 40 posts - 961 through 1,000 (of 1,036 total)
  • Author
    Posts
  • Hello Sean,

    Thank you for your inquiry and I am happy to answer.
    W3 Total Cache is a separate plugin and Premium BoldGrid Connect does not include W3 Total Cache Pro.
    As a separate plugin, it requires a separate license.
    Thanks!

    in reply to: W3TC Pro #35170

    Hello Mateusz,

    W3 Total Cache Pro licenses are valid on a per-install basis, meaning you need one for every WordPress instance you run. If you have three separate websites, you will need three licenses in total — one for each site. If you have five sites in a WordPress multisite instance, you need just one license for all five sites. If you are interested in bulk licensing, please email us for more information.
    Thanks!

    in reply to: How to Flush W3TC Programatically? #35169

    Hello Celine,

    Thank you for your inquiry and I am happy to assist you with this.
    You can use w3tc_flush_all
    You can check more functions in wp-content/plugins/w3-total-cache/w3-total-cache-api.php
    In this case the function:

    /**
     * Purges/Flushes everything
     */
    function w3tc_flush_all( $extras = null ) {
    	$o = \W3TC\Dispatcher::component( 'CacheFlush' );
    	$o->flush_all( $extras );

    Thanks!

    Hell Jared,

    Does the issue occur again after the cache is cleared?
    How often do you see the issue happens?
    MOst likely this was a temporary hiccup until the files are uploaded and served from the CDN.
    I’ve checked your website and I am not seeing any issues at the moment.
    Thanks!

    in reply to: Please Help, The AMP URL points to a non-AMP page #35037

    Hello Pernando,

    We received your email and replied to it. Please follow the instructions provided and continue the correspondence via the support channel so we can avoid duplicating the answers.
    Thanks!

    in reply to: Lazy load failed on ajax blog module #35000

    Hello Dominique,

    Thank you for the information and the Dev team is doing the best it can.
    Please understand that the issue is related to specific themes/plugins.
    Thanks!

    in reply to: WTC3 #34992

    Hello James,

    I am sorry about the issue you are experiencing when upgrading the W3TC and I am happy to assist you with this.
    What you can do is to make a backup of wp-content/w3tc-config/master.php and completely remove and re-install W3 Total Cache following the instructions below:
    1. Purge Cache
    2. Deactivate and Delete Plugin
    3. Check .htaccess File (make a backup)
    W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
    Ensure that no residual entries are leftover in your .htaccess file after deleting the plugin.
    4. Delete wp-content files and folders
    – cache folder
    – w3tc-config folder
    – object-cache.php (if exists)
    – advanced-cache.php (if exists)
    – dbcache.php (if exists)
    – upgrade folder
    – delete w3-total-cache folder in wp-content/plugins/ (if exists)
    5. Delete Cached Files from CDN (if using CDN)
    Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    6. Go to your wp dashboard and re-install W3 Total Cache
    7. copy and paste the backup of master.php to wp-content/w3tc-config/

    Alternatively, you can try upgrading the plugin to 2.1.1, download the latest version from here and copy the \w3-total-cache\lib\Minify\Minify\HTMLTidy.php from the downloaded folder into /home/xxxxxx/public_html/wp-content/plugins/w3-total-cache/lib/Minify/Minify/
    I hope this helps!
    Thanks!

    in reply to: W3TC minify has made all fusion elements large #34988

    Hello Lian,
    Thank you for the information.
    Glad to know the issue is resolved!
    Thanks!

    in reply to: Lazy load failed on ajax blog module #34984

    Hello Dominique

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    We have an open issue in our Github Repository, regarding this problem. Please make sure to track the progress of the issue regularly and feel free to commend on it and share more info.
    Thanks!

    in reply to: Fatal error #34982

    Hello

    Thank you for your inquiry and I am happy to assist you with this.
    This means that the memory_limit of 128M is being exhausted. There is no particular reason why this happens with the role other than Administrator.
    What you should do is to increase the memory limit
    To increase the PHP memory limit setting, edit your PHP.ini file. Increase the default value (example: Maximum amount of memory a script may consume = 128MB) of the PHP memory limit line in php.ini.

    memory_limit = 256M
    Alternatively, you can edit your .htaccess file (Not recommended see: Apache Performance: Disable .htaccess)

    php_value memory_limit 256M
    If you don’t have access to these files or lack the experience to make this change, you can contact your web host and ask them to increase your PHP memory limit.

    in reply to: W3TC minify has made all fusion elements large #34931

    Hello Lian,

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    I’ve checked your website and I am not seeing any issues, or better said, I don’t know how it supposes to look like.
    Can you please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled, and see which one might be causing the issue?
    If for example minify is causing the issue, re-enable minify, and disable the settings in Performance>minify one by one (HTML minify, JS minify, CSS minify) and see which one might be causing the issue.
    Make sure to save all settings and purge the cache after each option is disabled.
    Thanks!

    in reply to: AWS Autodiscovery not working #34929

    Hello Mike.

    Looking at your website I see

    Object Caching 419/23626 objects using Memcached
    Page Caching using Memcached 
    Content Delivery Network via Amazon Web Services: S3: mvpproshop-media.s3.amazonaws.com
    Database Caching 2/4883 queries in 14.265 seconds using Memcached (Request-wide modification query)
    Served from: localhost @ 2021-03-12 10:06:23 by W3 Total Cache

    Have you switched to a regular Memcached client and not autodiscovery?
    If you check this article you need to Install the Memcached Client
    That requires a PHP module amazon-elasticache-cluster-client.so
    https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/AutoDiscovery.HowAutoDiscoveryWorks.html
    There are the module for:
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-7.3/latest-64bit
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-7.2/latest-64bit
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-7.0/latest-64bit
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.6/latest-64bit
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.5/latest-64bit
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.4/latest-64bit
    https://elasticache-downloads.s3.amazonaws.com/ClusterClient/PHP-5.3/latest-64bit
    5:15
    No 7.4 or 8.0 yet. No 7.1.

    Thanks!

    in reply to: AWS Autodiscovery not working #34893

    Hello Mike,

    Thank you for the information.

    Does this always happen when logged in or have you checked when logged out from the wp-admin?

    Thanks!

    in reply to: How to exclude the cookie PHPSESSID from the cache #34890

    Hello Anna,

    Thank you for your inquiry and I am happy to assist you with this.

    Ah yes, the PHPSESSID. This makes caching a lot harder. Make sure that caching is disabled to logged-in users in Performance>Page Cache “Don’t cache pages for logged in users”

    You can also add PHPSESSID in Performance>Page Cache>Advanced>Reject Cookies filed, save all settings and purge the cache.

    Thanks!

    Hello Avi,

    As I already replied via the support channel, this depends on what changes you are making in the backend. When installing new plugins or removing the unneeded plugins it’s recommended to purge the cache.

    However, if you are referring to updating the posts or creating new articles then no, there is no need to purge the cache manually as it’s being handled by the Purge policy in Performance>Page Cache so the cache will be cleared automatically.

    Thanks!

    in reply to: AWS Autodiscovery not working #34863

    Hello Mike,

    Thank you for your inquiry and I am happy to assist you with this.

    There is a possible issue in /wp-content/plugins/w3-total-cache/DbCache_WpdbInjection_QueryCaching.php lines 742-744.
    Change the double-quotes to single:

    $strings[] = sprintf( "%s%d", str_pad( 'Total queries: ', 20 ), $this->query_total );
    $strings[] = sprintf( "%s%d", str_pad( 'Cached queries: ', 20 ), $this->query_hits );
    $strings[] = sprintf( "%s%.4f", str_pad( 'Total query time: ', 20 ), $this->time_total
    );

    to

    $strings[] = sprintf( '%s%d', str_pad( 'Total queries: ', 20 ), $this->query_total );
    $strings[] = sprintf( '%s%d', str_pad( 'Cached queries: ', 20 ), $this->query_hits );
    $strings[] = sprintf( '%s%.4f', str_pad( 'Total query time: ', 20 ), $this->time_total );

     

    Try this out and let me know if this helps!

    Thanks!

    in reply to: Error 502 when W3 activated #34839

    Hello Tim,

    Thank you for your questions and I am happy to answer.

    1. We are not offering any discount for a single license at the moment. If you are interested in a multiple license activation please drop us a note via the plugin in Pefrormance>Support.
    2. Without looking at the logs I cannot share any specifics on why this may be occurring. Make sure that the Object Cache and DB cache are not enabled, especially if caching to disk and on the shared server. If those options are enabled, disable them, save all settings and purge the cache and see if the issue persists.
      If the DB is the bottleneck of your website performance, I would recommend upgrading the hosting plan and usin memory-based caching for DB like Redis or Memcached.

    Thanks!

    in reply to: How to reduce the effect of critical request #34834

    Hello Kevin,

    Thank you for your inquiry and I am happy to assist you with this.

    Thank you for your support and as I can see in the test, the results are amazing.  This chain response time is not incrementing, so it’s not 2.5 s but 650ms as you can see in the waterfall chart.

    So there is nothing to worry about in this case as the time to interactive is 0.4 s

    Thanks!

    in reply to: W3 Total Cache Pro deferring external files #34777

    Hello Mark,

    As you already stated those are external files and no plugins can handle those files because they are coming from an external server.

    If Minify is set to Auto you may try to Include external files/libraries: option in Performance>Minify>Advanced and enable the option “Use Regular Expressions for file name matching”

    The best solution is to host those files on your server.

    Thanks!

    in reply to: Premium Set Up Services #34685

    Hello Howard,

    We’ve received both of your emails via the support channel and replied. Please continue the correspondence there so we can avoid duplicating the answers.

    Thanks!

    in reply to: Fatal error #34681

    Hello,

    I am sorry about the issue you are experiencing and I am happy to assist you with this.

    Can you please make sure that all files are completely removed before reinstalling the plugin?

    1. Purge Cache
    2. Deactivate and Delete Plugin
    3. Check .htaccess File (make backup)
    W3TC will create many directives in .htaccess file to control the caching behavior. Each section will start and end with comments like "#BEGIN W3TC Page Cache core" and "#END W3TC Page Cache core".
    Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
    4. Delete wp-content files and folders
    - cache folder
    - w3tc-config folder 
    - object-cache.php (if exists)
    - advanced-cache.php (if exists)
    - dbcache.php (if exists)
    - upgrade folder
    - delete w3-total-cache folder in wp-content (if exists)
    5. Delete Cached Files from CDN (if using CDN)
    Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    6. Go to your wp dashboard and re-install W3 Total Cache
    Thanks!
    
    

     

    Hello Bart,

    I am sorry about the issue you are experiencing and I am happy to assist you with this.

    Without looking into the logs there is no way we can be 100% sure what might be causing this. Most likely is a memory issue on the server. So make sure that you are not using Database Cache and Object Cache if on a shared server and caching to disk. Also, check the size of wp-content/cache/ folder

    There is also a possibility of a conflict with some other plugin so you may want to check that by disabling other plugins while W3TC is enabled.

    Thanks!

    in reply to: WPX CDN #34605

    Hello Eugene,

    MaxCDN is now Stackpath and it’s not ours, it’s something we recommend as a CDN provider. It is not recommended to use more than one CDN solution. Simply to avoid any issues. however, since these are two different types of CDN, you can try serving the static assets from the CDN by using Stackpath.

    Please check this article for more details.

    Thanks!

     

     

    in reply to: W3TC Can’t access pro features after upgrade #34575

    Hello Chris,

    I’ve replied to the email. Please continue correspondence there and follow the instructions so we can avoid sharing any private info on a public forum.

    Thanks!

    in reply to: W3TC Can’t access pro features after upgrade #34571

    Hello Chris,

    I can see that the license is activated on your website.

    Remove the license key from Performance>General settings, Licensing sub-box, license field, and save all settings. Re-enter the license, verify the license with the “verify license button” and save all settings.

    W3 Total Cache Pro should be active after these steps!

    Thanks!

    in reply to: database sharding & cache #34559

    Hello Mike,

    There is an example config wp-content/plugins/w3-total-cache/ini/dbcluster-config-sample.php

    Once edited create /wp-content/db-cluster-config.php and paste the config there. It should work after these steps.

    Thanks!

     

    in reply to: WPX CDN #34557

    Hello Eugene.

    Thank you for your inquiry and I am happy to assist you with this.

    As I can see, the WPX CDN needs to be enabled in the WPX Control Panel. AS this is being done outside of W3TC there is no need to do anything in W3 Total Cache.

    Thanks!

    in reply to: database sharding & cache #34512

    Hello Mike,
    With W3TC PRO you may use a cluster of MySQL servers when a single MySQL instance can’t handle all your traffic.

    Choosing a Database Caching Method in W3 Total Cache

    Thanks!

    in reply to: Total cache pro #34510

    Hello Ketil,
    W3 Total Cache Pro licenses are valid on a per-install basis, meaning you need one for every WordPress instance you run. If you have three separate websites, you will need three licenses in total—one for each site. If you have five sites in a WordPress multisite instance, you need just one license for all five sites.
    Thanks!

    in reply to: problem with images #34470

    Hello,

    I am sorry about the issue you are experiencing with the images and I am happy to assist you with this.

    Can you please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled and see which one might be causing the issue?

    Thanks!

    in reply to: database sharding & cache #34468

    Hello Mike,
    Using more than one plugin for this is not recommended.
    If you are planning to use the mentioned plugin you should disable W3TC db caching as both plugins are using the same drop-in – db.php.

    Thanks!

    in reply to: Table “wp_w3tc_cdn_queue” doesn’t exist error #34422

    Hello Kiem,

    Please make sure to check this link for assistance with this and also check the Performance>Install page for more details.
    Thanks!

    Hello Mark,

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    WE’ve received your email via the support channel and replied to it so please continue the correspondence there so we can avoid duplicating the answers.
    Thanks!

    in reply to: W3 Total Cache + Amazon Cloudfront #34339

    Hello Aninda,
    Thank you for your inquiry and I am happy to assist you with this.
    Are you trying to setup FSD CDN or just serving the static assets from the AWS?
    Can you please share the screenshot of the settings in Performance>CDN>Configuration: Objects?
    Thanks!

    in reply to: Table “wp_w3tc_cdn_queue” doesn’t exist error #34337

    Hello Kiem,

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Can you please share the screenshot or more detailed information about where you are seeing the error message?
    A screenshot would be great.
    Thanks!

    in reply to: [Resolved] Recurring Mixed Content with W3 Total Cache #34307

    Hello Michael,

    I am sorry about the issue you are experiencing with mixed content and I am happy to assist you with this.
    I would recommend completely removing and re-installing W3 Total Cache, including all residual files:
    1. Purge Cache
    2. Deactivate and Delete Plugin
    3. Check .htaccess File (make a backup)
    W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
    Ensure that no residual entries are leftover in your .htaccess file after deleting the plugin.
    4. Delete wp-content files and folders
    – cache folder
    – w3tc-config folder
    – object-cache.php (if exists)
    – advanced-cache.php (if exists)
    – dbcache.php (if exists)
    – upgrade folder
    – delete w3-total-cache folder in wp-content (if exists)
    5. Delete Cached Files from CDN (if using CDN)
    Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    6. Go to your wp dashboard and re-install W3 Total Cache

    Once enabled, Enable the settings one by one, save all settings and purge the cache after each setting is enabled, and make sure to check your website.
    Also in Page Cache, make sure that the option “Cache SSL (HTTPS) requests” is enabled
    I hope this helps!

    in reply to: [Resolved] activation W3 caused site error, no access #34305

    Hello Mitchell,
    Thank you for the information.
    I’ve checked your website and as I can see the website is accessible as well as the https://custom-tiles.com/wp-admin/ and W3 Total Cache is active on your website.

    <!--
    Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/
    
    Page Caching using disk: enhanced 
    Content Delivery Network via N/A
    Lazy Loading
    Minified using disk
    
    Served from: custom-tiles.com @ 2021-02-24 19:55:39 by W3 Total Cache
    -->

    Can you please confirm that you are still experiencing the issue?
    Thanks!

    in reply to: [Resolved] activation W3 caused site error, no access #34275

    Hello Mitchell,

    The provided steps need to be taken first in order to access your dashboard. So to access your dashboard you need to manually delete those files from the server following the steps provided.
    Once those files are deleted, you can then access the dashboard and re-install W3TC and making sure that OC and DB Cache are not enabled.
    What hosting support did is most probably disabled the plugin by renaming it in the wp-content/plugins/
    The problem is that the settings you enabled are still in wp-content/w3tc-config/master.php and the cached files are in the /cache/ folder.
    Thanks!

    in reply to: [Resolved] activation W3 caused site error, no access #34265

    Hello Mitchell,

    Simple deactivation of the plugin is not sufficient.
    Please follow the steps provided and completely remove everything related to W3 Total Cache.
    Once that’s done, install W3 Total Cache without any leftover files remaining and make sure not to use Object Caching and Database caching if on shared hosting and if caching to Disk.
    Thanks!

    in reply to: [Resolved] activation W3 caused site error, no access #34252

    Hello Mitchell,

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Can you please completely remove W3 Total Cache and re-install it and once the plugin is reinstalled make sure that Object Cache and Database Cache are not enabled in the General settings especially if on shared hosting and if caching to disk and see if the issue persists:
    1. Check .htaccess File (make a backup)
    W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
    Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
    2. Delete wp-content files and folders
    – cache folder
    – w3tc-config folder
    – object-cache.php (if exists)
    – advanced-cache.php (if exists)
    – dbcache.php (if exists)
    – upgrade folder
    – delete w3-total-cache folder in wp-content/plugins/ (if exists)
    3. Delete Cached Files from CDN (if using CDN)
    Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    4. Go to your wp dashboard and re-install W3 Total Cache, and as I mentioned, make sure that Object Caching and Database Caching are disabled if on shared hosting plan and if caching to disk.
    Thanks!

Viewing 40 posts - 961 through 1,000 (of 1,036 total)