Laravel WordPress Integration
WordPress as a CMS, Laravel as the application — not “WordPress with extra steps”.
Authentication and data flow
Typical pattern: WordPress REST API with application passwords or OAuth, consumed from Laravel jobs — not from a page controller on every request. Cache published content; do not cache drafts. For logged-in experiences, pick one identity provider. Dual login is how you get dual security bugs.
Failure modes
- Syncing users both ways until permissions diverge.
- Putting business rules in WordPress hooks that Laravel also implements, slightly differently.
- Exposing REST to the world with
edit_postsbecause a plugin tutorial said so.
WordPress REST handbook: developer.wordpress.org/rest-api.
Qualification
Discuss your Laravel project
Name, work email, and a short description of the application is enough. No discovery call theatre before I know whether I can actually help.
- UK businesses with a real Laravel (or legacy PHP) application
- Build, support, rescue, upgrade or integration work
- Reply from Oliver Burton, usually within one working day