litespeedtech / litespeedtech/lscache_wp
Localise Resources does not work, URL to local file returns 404 error.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 257
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
The fbevents.js is not cached properly using the url provided: https://github.com/litespeedtech/lscache_wp/blob/2aa6a115e8812d26f7505280c7fcbae89e10c977/data/const.default.ini#L462
The cached file returns a 404 error.
(index):104 GET https://example.com/wp-content/litespeed/localres/aHR0cHM6Ly9jb25uZWN0LmZhY2Vib29rLm5ldC9lbl9VUy9mYmV2ZW50cy5qcw== net::ERR_ABORTED 404
The issue appears to be relatively recent as pixel data has only stopped in the last two weeks or so.
The code was inserted using Code Snippets in to wp_head. The pixel tracking works when the lscache plugin is disabled or the url of the script removed from the Localization Files list.
Plugin version: 4.6
Wordpress version: 5.9.3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Localise Resources entry in data/const.default.ini and reproduce the fbevents.js request with LiteSpeed Cache enabled, using the reported WordPress and plugin versions. Trace why the generated /wp-content/litespeed/localres/ URL returns 404; done means the localized file loads successfully and pixel tracking works without removing the URL from the Localization Files list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100