- How do I install adamgoose/prismic-io in a Laravel application?
- Install it with Composer using adamgoose/prismic-io, then register the package's service provider and facade manually in config/app.php because Laravel 4.2 does not support package auto-discovery. Publish the package configuration and set your Prismic repository endpoint and API credentials. This installation path is only appropriate for a legacy Laravel 4.2 application.
- Which Laravel versions does adamgoose/prismic-io support?
- The package's last release, v1.3 in 2014, was specifically updated for Laravel 4.2 compatibility. There is no evidence of support for Laravel 5, 9, 10, or 11, and using it on a modern stack would require a fork. Treat it as a Laravel 4.2-only package.
- How do I configure Prismic API credentials for this package?
- After publishing the config file, set the Prismic repository endpoint and the API credentials the package needs to authenticate. The wrapper is config-driven, so the service provider and facade read those values when resolving the Prismic client. Keep credentials out of source control and load them from environment-specific configuration.
- Can I use adamgoose/prismic-io with Prismic's current v2 API?
- That is the key risk: this is a 2014-era wrapper for Prismic's API at that time, and Prismic has since moved to a v2 API with different endpoints and response shapes. The package may fail at runtime rather than at install time if it targets retired endpoints. Verify the source against your actual Prismic repository before adopting it, and prefer Prismic's current official PHP SDK for new work.
- How do I query Prismic documents using the facade?
- Use the provided facade to call the wrapper's query methods for Prismic documents, bookmarks, and tags. The package returns Prismic API responses that you can pass into controllers and views. Check the source for the exact method names and response shapes, because the package is a thin wrapper around the Prismic PHP SDK.
- Does adamgoose/prismic-io support Laravel package auto-discovery?
- No. Package auto-discovery was introduced after Laravel 4.2, so you must add the service provider to the providers array and the facade to the aliases array in config/app.php. That manual registration is expected for this package's target framework.
- Is adamgoose/prismic-io maintained or safe for production in 2024?
- It is not a good choice for new production work: the last release was v1.3 in 2014, Laravel 4.2 has been end-of-life since 2015, and the package inherits unpatched framework and PHP dependency risk. The changelog is thin, with no clear test evidence or active maintainer commitment. Use it only as a pinned stopgap in an existing Laravel 4.2 application that is already scheduled for replacement.
- What should I use instead of adamgoose/prismic-io for a modern Laravel app?
- For a modern Laravel application, use Prismic's current official PHP SDK and wrap it in a small Laravel service provider and facade yourself. That gives you supported PHP and Laravel versions plus control over the Prismic API version. A maintained community integration is another option if one exists for your Laravel version.
- What Prismic features does adamgoose/prismic-io expose?
- The package exposes Prismic documents, bookmarks, and tags through a Laravel facade and service provider. It also provides config-driven setup for the repository endpoint and API credentials, returning Prismic API responses for use in controllers and views. It is a lightweight wrapper around the Prismic PHP SDK rather than a full CMS abstraction.
- How do I test a Laravel app that uses adamgoose/prismic-io?
- The package itself has no visible test evidence in the release notes, so test your integration boundaries rather than relying on it. Mock the facade or inject a fake Prismic client so your controllers and views do not make real API calls during tests. Also add a contract test against a real Prismic repository to confirm the wrapper still matches the API version you use.