litespeedtech / litespeedtech/lscache_wp
Localize Resources - problem with /wp-content
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 257
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
Litespeed + WP Hide & Security Enhancer = problems
If we change default content path ex. "/wp-content/" -> "/contents" in WP Hide & Security Enhancer plugins and if "Localize Resources" is ON, all .js files from external servers doesnt works.
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
Reproduce the issue with LiteSpeed Cache for WordPress, WP Hide & Security Enhancer, a custom content path, and Localize Resources enabled; inspect how external .js resources are localized. Done means external JavaScript files load correctly with the custom /contents path, but the payload names no source file or test to begin from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php, wordpress
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100