litespeedtech / litespeedtech/lscache_wp

Empty file when using CSS Combine

Open
#881 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
257
Forks
123
PR merge metrics
No merged PRs in 30d

Description

Hello,

On my WordPress site, the CSS file is sometimes served with a 200 OK status, but its content is empty. This breaks the site's styling. The only way to fix the issue is to perform a "Purge All" from the LiteSpeed Cache plugin menu.

Here are the details of my environment:

LiteSpeed Cache Version: 7.2

WordPress Version: 6.8.1

PHP Version: 8.4

CDN: AWS CloudFront

Caching Plugins: LiteSpeed Cache and Redis Object Cache

In the LiteSpeed Cache settings (under Page Optimization > CSS Settings),

we have both Minify CSS and Combine CSS enabled. However, the issue of the empty CSS file seems to occur specifically when the Combine CSS feature is active.

Could you please help me understand the potential causes of this behavior? Thank you.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified. Start by reproducing the empty response with Minify CSS and Combine CSS enabled, using the listed WordPress, PHP, CloudFront, and Redis environment, then trace the CSS combination and purge behavior. Done means combined CSS responses consistently contain the expected styles without requiring Purge All.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, php, redis, wordpress
Domain
performance, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.