Issues after changing LSCache to W3 Total Cache

  • Resolved EdKrasnov

    (@alshoker)


    2 years, 1 month ago

    I decided to change the caching plugin and install W3 Total Cache (before that, the LSCache plugin was installed).
    I installed W3TC 2 times and 2 times there were problems: headings disappeared, several plugins stopped working, and the last time the sidebar settings disappeared.

    I tried different options with W3TC, with and without a DB cache, set the object cache to Redis and Memcached, the page cache on disks.

    I didn’t have time to get to minification and combining js and css.
    Why are settings and plugins removed? So I didn’t understand. Perhaps because of the change of plugins with caching occurred. But in the few hours I tested W3TC, pages opened much faster than LSCache.

    Unfortunately, the problems described have been a major disappointment to the W3TC. I would be glad if the developer explains the reasons or tells you how to avoid the described problems.
    The server is using OpenLiteSpeed.

    —————–

    Решил сменить плагин кэширования и установить W3 Total Cache (до этого был установлен плагин LSCache).
    Ставил 2 раза W3TC и 2 раза происходили проблемы: исчезали рубрики, перестали работать несколько плагинов, а в последний раз пропали настройки сайдбаров.

    С W3TC пробовал разные варианты, с кэшем DB и без, кэш объектов настраивал на Redis и Memcached, кэш страниц на дисках.

    До минификации и объединения js и css не успел дойти.
    Почему удаляются настройки и плагины? Так и не понял. Возможно из-за смены плагинов с кэшированием произошла. Но те недолгие часы, которые я тестил W3TC – страницы открывались намного быстрее чем LSCache.

    К сожалению, описанные проблемы сильно разочаровали в W3TC. Буду рад, если разработчик объяснит причины или подскажет как избежать описанных проблем.
    Сервер использую OpenLiteSpeed.

    • This topic was modified 2 years, 1 month ago by EdKrasnov.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @alshoker

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

    Basically, you have answered your own question with the last statement: “The server is using OpenLiteSpeed.”

    What happens is that OpenLiteSpeed (OLS) can’t process the rules that W3TC writes on the HTACCESS file.
    However, the rules work when you use LiteSpeed Enterprise. The reason is that OLS htaccess rules differ slightly from LiteSpeed (That’s fully compatible with Apache rewrite rules).

    OLS does have the option to auto-load?.htaccess?on web server startup, but only reads the?mod_rewrite?directives?RewriteCond?and?RewriteRule. OLS will ignore all other items. It appears that OLS web admins are forced to configure available items in the?OpenLiteSpeed Webadmin?panel.

    As you can see from our changelog, we’ve added basic OpenLiteSpeed support. However, this does not work out of the box due to the OLS requirements. (basically forcing you to use their plugin)

    We are preparing documentation for this, however, you can check this doc for more details and information on how to achieve this.

    I hope this helps!

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Issues after changing LSCache to W3 Total Cache’ is closed to new replies.

Tags