litespeedtech / litespeedtech/lscache_wp
Third Party integration with LifterLMS (WordPress plugin)
- Dominant language
- PHP
- Stars
- 257
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
I'm a cofounder and developer at [LifterLMS](https://wordpress.org/plugins/lifterlms/)
Recently we've had a lot of users encountering issues with our plugin which we can correlate to usage of LiteSpeed Cache.
I've been reviewing your API docs and would like to implement compatibility for our plugin as a third party similar to how you currently support WooCommerce, form plugins, page builders, etc...
LifterLMS provides a large amount of content to logged in users which should not be cached in *most* circumstances, we also have frontend login/registration/checkout functionality (similar to WooCommerce or other WP ecomm plugins).
Common issues our users face when using LiteSpeed cache are complaints of "My users cannot login" (it seems this is because the frontend account page gets cached so after logging in they're served the cached logged-out view of the page). We also see users who attempt to access their private course content who are unable to do so because the cached version of the content (which prevents a logged-out user from accessing the content) is cached.
After reviewing your API and other integrations I believe it will not be too much effort to implement compatibility and if amenable to your team, myself or someone from my team could write and test the code and submit it as a pull request for your review.
If you would like to discuss this further in private as opposed to via GitHub please reach out to us via email: team@lifterlms.com
Thanks for considering my proposal!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the LiteSpeed Cache API documentation and the existing WooCommerce and other third-party integrations mentioned in the issue. Define compatibility for LifterLMS's logged-in content and frontend login, registration, and checkout flows, then verify that these pages are not served incorrectly from cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100