- How do I install marcorieser/statamic-instagram in a Laravel Statamic project?
- Install it with composer require marcorieser/statamic-instagram. Statamic addons are Laravel packages, so package discovery should register the service provider automatically. Then publish the package config if the README instructs it, add your Instagram Business API token to .env, and rebuild the config cache.
- Which .env variable does statamic-instagram 2.6.1 use for the Instagram API token?
- Version 2.6.1 moves the Instagram API token out of committed configuration and into .env. The exact variable name is defined by the package config file, so check the package's .env.example or published config for the env() key. Set that variable in every environment before running composer update.
- Does marcorieser/statamic-instagram work with php artisan config:cache?
- It should be configured the Laravel way: the token is read through a config file that calls env(), not via env() at API call time. Run php artisan config:clear and php artisan config:cache after the token exists in the target environment. If config is cached without the token, it resolves to null and you can get a 401 or 403 from Instagram instead of a clear boot error.
- Why am I getting a 401 or 403 from Instagram after upgrading statamic-instagram to 2.6.1?
- The most likely cause is that the new .env token is missing in that environment or the config cache was built before the variable was set. Add the variable to the environment's secret store, then run config:clear and config:cache. Smoke test one authenticated request in staging before promoting to production.
- Is the statamic-instagram 2.6.1 upgrade backward compatible?
- It is a patch release, but in practice it is a configuration change for existing installs. If your token was previously hardcoded or committed in config, you must provision the .env variable before upgrading. Treat 2.6.1 as a coordinated deploy and pin the version explicitly rather than using a floating constraint.
- How do I show Instagram posts and captions in Antlers templates with this addon?
- The addon provides Antlers tags that pull Instagram Business API data, such as posts, images, and captions, into your Statamic views. You typically loop over the returned feed and render the image and caption fields in your template. Check the package README for the exact tag names and parameters.
- Do I need to re-publish the config file after upgrading marcorieser/statamic-instagram to 2.6.1?
- If your published config file predates the token change, it may not contain the new env-backed key. Re-publish with vendor:publish --force or manually add the key to your config file. Compare your published config against the package version before deploying.
- How should I store the Instagram API token for statamic-instagram in staging and production?
- Store it in your environment's secret manager, such as Vault, AWS Secrets Manager, Forge environment variables, or container env vars, not in the repository. Make sure the variable exists in dev, staging, and production before you bump the package version. Then rebuild the config cache as part of the deploy.
- Does statamic-instagram validate the Instagram token at boot or only on the first API call?
- The assessment flags this as a key thing to verify: the package may not fail loudly at service-provider boot and may only return an upstream 401 or 403 on the first API call. Do not rely on boot-time validation. After deployment, run an authenticated smoke test in staging to confirm the token resolves correctly.
- How do I rotate the Instagram API token for a Statamic site using this package?
- Update the token in your secret store or environment variables for each deployment. Run php artisan config:clear and php artisan config:cache after the new value is present. No application code change is required, but verify with an authenticated request before considering the rotation complete.