- Can I install oh/instagram-bundle in a Laravel application?
- No, not as a usable dependency. It is a Symfony 2 bundle built around the Symfony DI container and Instaphp, with no Laravel service provider, facade, or framework-agnostic core. Composer will also conflict with modern Laravel and Symfony versions, and forcing installation yields an unrunnable service.
- Does oh/instagram-bundle support Laravel 10, 11, or 12?
- No. The package targets Symfony 2.x, which reached end of life in 2018, and pins ancient dependency constraints. Laravel 10, 11, and 12 have no bundle kernel or container extension mechanism, so there is nothing to register. Installation will fail dependency resolution rather than provide Instagram functionality.
- Why does Composer fail when I require oh/instagram-bundle?
- Its constraints pin symfony/symfony to the 2.x line and an old PHP floor, which conflicts with modern Laravel and Symfony dependencies. Using --ignore-platform-reqs may bypass the resolver but leaves you with an unrunnable Symfony 2 service definition. The conflict is architectural, not a simple version bump.
- Is the Instagram API used by oh/instagram-bundle still available?
- No. Instaphp targets the retired Instagram Platform API at api.instagram.com/v1, which was shut down in 2018–2020 in favour of the Graph API and Basic Display API. The endpoints this bundle calls no longer exist, so the integration is non-functional by design. No integration work can revive the underlying API contract.
- What should Laravel developers use instead of oh/instagram-bundle for Instagram feeds?
- Use Meta's current Graph API or Basic Display API through a small adapter you control, or use Instagram oEmbed for simple public post embeds. Define an internal interface such as InstagramFeedProvider with a narrow fetch-media contract so the transport can change. Commercial aggregators can also be faster if you need hashtag aggregation or multi-account feeds.
- Does oh/instagram-bundle work with Symfony 6 or Symfony 7?
- No, not without a full rewrite. It relies on Symfony 2 bundle conventions, a bundle class, Resources/config/services.yml, and a container extension that modern Symfony no longer supports in that form. You would need to extract a plain library and wrap it in a small autowired service, at which point you have effectively written your own package.
- Is oh/instagram-bundle maintained and safe for production?
- No. It has a single maintainer, effectively no release cadence, two stars, zero dependents, and a very low package score, so there is no community validation or security response. The underlying 2014-era library predates current Meta terms and does not model today's caching or re-display obligations. Credential handling, token storage, and TLS behaviour would need a full audit before any production use.
- Can I fork oh/instagram-bundle and make it Laravel-compatible?
- You can, but it is not worth it. The bundle is a thin wrapper around Instaphp, so a fork would mostly be deleting Symfony wiring and replacing a dead API client. You would still inherit abandoned code and take on permanent liability. A fresh 200-line Graph API adapter or an oEmbed embed is usually cheaper and clearer.
- What is required to use the Instagram Graph API from Laravel today?
- You need a Meta developer app, business verification where applicable, OAuth token handling, and app-review approval for the permissions you request. That review and approval process is typically the real critical path and can take two to six weeks. The bundle provides no support for any of these current requirements.
- How do I decide between building an Instagram integration, using oEmbed, or buying an aggregator?
- First clarify the capability: public content display, hashtag aggregation, or publishing. oEmbed is fastest for simple public post embeds, a self-built Graph API adapter gives control for feeds you own, and a commercial aggregator fits broader aggregation or multi-account needs. Given the platform's history of breaking API changes, choose the shortest-lived integration that meets the requirement.