Forum Replies Created

Viewing 11 replies - 211 through 221 (of 221 total)
  • Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Brad,

    From what I understand about your screen shots, the litespeed-cache directory is inside your mu-plugins directory, and that is it. Is that correct?

    1. In that scenario, are you able to see the LiteSpeed Cache settings in the WP Admin?

    2. Is Super Cache enabled in its settings?

    3. If the answer to #2 is yes, in the wp-config.php file, is there a line that says the following:
    define('WP_CACHE', true);
    If the answer to #2 is no, is that line commented out?
    //define('WP_CACHE', true);

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Brad,

    I tested using the following procedure:
    1. In an Apache WordPress installation, install the plugin via WP Admin Panel.
    2. Move the plugin to the mu directory.
    *3. Refreshed the admin page, confirm that it is on
    4. Check out the front page, confirm that it is still working.
    **5. Delete the plugin.

    * For mu plugins, the loading file must be in the mu-plugins directory, not a sub directory. Once moved, I found that if the require-once path was not fixed, it resulted in a white blank screen on the front page.
    ** If the litespeed-cache directory was deleted, but the litespeed-cache.php file was not, it also resulted in a white blank screen (likely meaning require-once failed like above).

    If configured correctly according to WP instructions, everything worked fine.

    Can you provide step by step instructions on how to reproduce this issue?
    What does your set up look like?

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Alec,

    Our primary objective is to have the cache working correctly out of the box, with minimal extra configurations. We are currently working on a script that automates enabling the plugin to make things even easier.

    We agree with you in that it should be easier to manage the rewrite rules, and that it should be available in the plugin to configure.

    If you don’t mind me asking, what are you looking to do with excluding by cookie or user-agent? Do you have any example use cases? We’d like to make it work automatically if it isn’t already covered yet.

    Also, this plugin is open source, so we welcome any/all contributions and suggestions.

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    The link in our previous comment has been moved here ??

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Martin,

    Thanks for the questions!

    Our LiteSpeed Web Server has do-not-cache URL and Domain options.
    The plugin itself has options to exclude (do-not-cache) by URI (specific to WordPress), Post Categories and Post Tags.

    Excluding by cookie name and user agent must be done through rewrite rules.

    The mobile cache is also done through rewrite rules, as seen here

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Knut,

    The WebAdmin is our graphical interface for controlling LiteSpeed Web Server and it’s settings. If you are under shared hosting than your hosting provider would have access to this.

    Back to your issue, we are currently working on a fix. There seems to be some issues when there are multiple WordPress installations.

    How are your sites set up? Is it using WordPress’ multisite setup, or do you have a different sub directory per installation?

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Most of our cache control for this plugin is handled through headers and cookies, so the rewrite rules should not be necessary. The only thing we recommend in .htaccess is

    <IfModule LiteSpeed>
    CacheLookup public on
    </IfModule>

    Which allows you to disable “Check Public Cache” in the webadmin and instead enable it through .htaccess only for the sites that use LSCache.

    Our current Cache Policy settings for LSCWP are:
    Enable Public Cache – No
    Check Public Cache – Yes
    Cache Request with Query String – Yes
    Cache Request with Cookie – Yes
    Cache Response with Cookie – Yes
    Ignore Request Cache-Control – Yes
    Ignore Response Cache-Control – Yes

    Since I was not able to quickly reproduce this problem on my end, could you provide a link to your affected sites? You can also email us at [email protected] with some more information/temporary login so we can investigate further.

    Thanks

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hello Knut,

    Thanks for the review!

    As for what is excluded, admin pages and logged in users. We provide a “For more info” link to our wiki at the end of our installation instructions which explains this. We also have a help tab at the top of our plugin’s settings page that links to “LSCache Documentation”.

    If you would like to debug/test you can click on one of the links previously mentioned take a look at our more in-depth WP plugin installation guide page. It contains info on testing as well as enabling the WordPress debug log.

    Let me know if you run into any issue, I would be happy to help.

    Regards

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    As of version 1.0.2, not yet, but we are actively working on improving WooCommerce compatibility.

    Forum: Reviews
    In reply to: [LiteSpeed Cache] Nice work
    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi TrueZone,

    Thanks for the feedback! I can’t seem to find the broken link you mentioned. Can you give me a little more information on that?

    Thanks

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hello John,

    At current, this plugin does not work with Woocommerce. However, we do plan to add Woocommece compatibility in a future version.

    If you have any further questions or concerns, feel free to ask.

    Regards,
    ~Rob

Viewing 11 replies - 211 through 221 (of 221 total)