Fix Multisite Cache Deletion Issue with lazyload background images feature

[wordpressfan]

Description

Fixes #6340

Here we unify the caching directory path for lazyload background images feature.

Type of change

• Bug fix (non-breaking change which fixes an issue).

Detailed scenario

Everything is mentioned in the issue itself, u can install multisite and add some background images in some pages (different sub-sites) then in one site try clearing the cache, this will remove the background images for all sub-sites.

Technical description

Here we unify the way that we instantiate "lazyload_css_cache" in the container service provider.

Documentation

N/A

New dependencies

N/A

Risks

I think we will need to clear cache with update to that version because the files urls are changed, but need to confirm that with QA and product.

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

Unticked items justification

N/A

Additional Checks

• In the case of complex code, I wrote comments to explain it.
• When possible, I prepared ways to observe the implemented system (logs, data, etc.).
• I added error handling logic when using functions that could throw errors (HTTP/API request, filesystem, etc.)

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -0.10%)	❌ 36.84% (target: 50.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (3f3bcb6)	39338	17145	43.58%
Head commit (c2a0d4e)	39354 (+16)	17152 (+7)	43.58% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#7226)	19	7	36.84%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[Mai-Saad]

For test:

• share e2e results for LLBGCSS
• share test plan results https://wpmediaqa.testrail.io/index.php?/runs/view/957&group_by=cases:section_id&group_order=asc

[Mai-Saad]

Working fine (failed tests are already failing on 3.18)

• VR failing due to minify CSS affecting the template https://wp-media.slack.com/archives/CUKB44GNN/p1738109842184439
  
  
  
  
  

testrail-report-688.pdf