- How do I install medz/phpwind in a Laravel project?
- Run composer require medz/phpwind, but treat it as a legacy PHPWind application codebase rather than a Laravel package. It does not register a service provider or provide a container-aware bootstrap, so composer require alone will not give you a drop-in Laravel integration. Plan to bootstrap PHPWind separately and connect Laravel through a thin adapter or shared database.
- Is medz/phpwind compatible with Laravel 10 or Laravel 11?
- It is not Laravel-version-specific because it is not a native Laravel package; it has no service provider or Laravel conventions. You can install it in a Laravel 10 or 11 project via Composer, but expect to run PHPWind as a sidecar or separate vhost rather than inside the framework lifecycle. Compatibility depends more on your PHP runtime and database than on the Laravel version.
- Does medz/phpwind work on PHP 8.2 or PHP 8.3?
- PHPWind targets PHP 5.3 through 7.x, and PHP 8.2 or 8.3 compatibility is not guaranteed. Expect deprecation notices, type errors, and legacy assumptions to surface on modern PHP. Pin to a tested PHP minor such as 7.4, or use 8.1 only with a compatibility shim you own and test thoroughly.
- How can I sync PHPWind users with Laravel authentication?
- Decide whether Laravel or PHPWind is the auth source of truth, then bridge them with a shared cookie domain or a signed handoff token. Sync Laravel users to PHPWind's pw_members table through a queued job or adapter service with methods like findUserByLegacyId, issueSessionCookie, and syncPasswordReset. Be aware that PHPWind uses legacy password hashing, so password reset and login flows need careful handling.
- Can I use medz/phpwind as a normal Composer dependency inside Laravel?
- Not really. medz/phpwind is a Composer-packaged distribution of a monolithic PHPWind forum application, not a well-scoped library, and it assumes it owns the request lifecycle and filesystem layout. A normal Composer dependency inside Laravel is likely to conflict with framework bootstrapping and routing. Run it as a separate vhost, subdirectory, or sidecar and integrate at the seams.
- How do I migrate existing PHPWind users, forums, threads, and posts to Laravel?
- Start with a lift-and-shift: preserve the pw_* tables verbatim and run PHPWind against a copy of the existing database to de-risk data migration. Build a Laravel forum_bridge service for user lookup, session issuance, and password reset sync, then verify parity before changing schemas. Avoid in-place schema surgery in phase one, and only consolidate user tables after the bridge is stable.
- What are the security concerns of using medz/phpwind in production?
- The codebase is an unmaintained 2010s PHP forum engine, with risks including SQL built via string concatenation, legacy md5-family password hashing, and no expected upstream security response. There are also GPL-adjacent ecosystem concerns under an MIT label and unclear provenance of the packaged source. Isolate it, restrict network access, and assign someone to patch CVE-class issues yourself.
- Does medz/phpwind provide a Laravel service provider or facades?
- No. medz/phpwind does not provide a Laravel service provider, facades, container-aware bootstrapping, or PSR-3/PSR-4 purity throughout. It exposes a legacy application codebase under a namespace, so do not expect composer require to yield a Laravel-ready service. Any Laravel-style facade would need to be written by you as an adapter.
- How do I run PHPWind under a /forum path alongside a Laravel app?
- Run PHPWind behind a path prefix such as /forum using an Nginx location rewrite or a Laravel fallback route that hands off to a separately bootstrapped PHPWind entrypoint. Share the same MySQL instance and keep PHPWind templates separate from Laravel Blade. This topology lets Laravel own the modern app and auth while PHPWind serves legacy forum behavior.
- Is medz/phpwind actively maintained, and what are the alternatives?
- medz/phpwind has a low maintenance signal, around 180 stars, and an assessment score of 2.23, so assume limited community patterns and no upstream security response. If your requirement is not literally PHPWind-compatible forum semantics, consider a maintained Laravel-native forum package, Flarum via API, or another Laravel BBS solution. Use medz/phpwind only when preserving PHPWind behavior or data is the real constraint.