- Can I install martin-georgiev/social-post-bundle in Laravel?
- No. martin-georgiev/social-post-bundle is a Symfony bundle, not a Laravel package. It ships a Symfony DI extension, configuration tree, service definitions, and compiler-pass wiring that Laravel's container does not consume. Installing it with Composer will likely fail outright or leave you with services Laravel cannot autowire.
- Is this a Laravel package or a Symfony bundle?
- It is a Symfony bundle. Laravel reuses Symfony components such as HttpFoundation, Console, and Process, but it does not load bundles. That means no service provider registration, no config publishing, and no facade or route integration out of the box.
- Does it support Laravel 10 or Laravel 11?
- Almost certainly not. A bundle last released in 2020 typically pins PHP 7.x and Symfony 3 or 4 components, which conflict with illuminate/* on Laravel 10 or 11 and with PHP 8.1+. Expect Composer to refuse the install during dependency resolution. Check the repository's composer.json constraints before spending time on it.
- What PHP and Symfony versions does it require?
- The package targets legacy PHP and Symfony versions from around 2020. Its last release was 2020-05-31 and the repository is archived. Modern PHP 8.1+ and Symfony 5, 6, or 7 are not supported. Confirm the exact constraints in the repository's composer.json.
- Is martin-georgiev/social-post-bundle still maintained?
- No. The repository is archived and the last release was 2020-05-31. There are no security patches, no API updates, and no issue triage. It has 39 stars and zero dependents, so there is no community validation or downstream fork to lean on.
- Will Facebook, LinkedIn, and Twitter publishing still work today?
- Unlikely. Every API it targets has moved since 2020: Twitter's v1.1 endpoints are gone and X now uses a paid, rewritten v2 surface; LinkedIn moved to versioned APIs with quarterly sunsets and app review gating; Facebook Graph versions expire on a roughly two-year cadence. Code targeting 2020 endpoints will return 4xx errors today.
- How does it publish a status update to multiple social networks?
- The design centers on a message object fanned out to per-network publishers, each with its own credentials, payload mapping, and length or format constraints. That abstraction is sound, but it depends on the bundle's Symfony service wiring. You would either bypass the DI extension and hand-wire dependencies or reimplement the pattern in Laravel.
- Can I reuse the code in a Laravel app instead of installing the bundle?
- Yes, and that is the recommended path. Treat the repository as a reference implementation: study the message abstraction, the per-network adapter contract, and the validation rules, then rebuild them with Laravel idioms such as a service provider, config files, facades, queued jobs, and the Http client. Expect days of reading and weeks of building, but zero framework impedance.
- Are there Laravel-friendly alternatives for cross-posting to social networks?
- Yes. Managed options include Ayrshare, Buffer's API, and Publer, while self-hosted Postiz is another route. Compare buy versus build explicitly, since cross-posting is a recurring need but rebuilding each network integration is expensive. Shipping one network well beats three badly.
- Does it handle media uploads and multi-user OAuth for social accounts?
- The package is broadcast-oriented: one brand account posting to configured networks via stored credentials. It does not solve multi-tenant OAuth with per-user token storage, refresh, revocation, and rate limits, and it does not handle media uploads, which are consistently harder than text posting. If you need either capability, plan for significantly more work.