- How do I install robindrost/prismic-eloquent in a Laravel app?
- Install it with Composer using robindrost/prismic-eloquent, then wire up your Prismic repository credentials and define model classes that map to your Prismic custom types. Because the repository is archived and last released in 2021, check its composer.json first: the Laravel, PHP and Prismic SDK constraints decide whether it installs at all on a modern stack. Expect to adjust service provider registration manually on newer Laravel versions.
- Does prismic-eloquent support Laravel 10 or Laravel 11?
- There is no published compatibility work after the 2021-06-29 release, so current Laravel majors are not officially supported. The package was built against the Laravel and PHP versions current at that time, and no maintainer will add support for newer framework releases. Verify the version constraints in composer.json before assuming it will resolve on Laravel 10 or 11, and budget for a fork if it does not.
- How does prismic-eloquent handle relationships between Prismic documents?
- It exposes Eloquent-style relationship methods, but each resolution is a live lookup against the Prismic HTTP API rather than a database join. That means lazy loading can turn a single page render into dozens of network round trips. Before using it, confirm whether relationships are batched into one request or resolved per document, because that difference dominates page latency.
- Is robindrost/prismic-eloquent safe to use in production?
- Treat it as abandoned: the repository is archived, it has roughly 12 stars, a single maintainer, and no releases since June 2021. You will get no security patches, no fixes for Prismic API changes, and no response to dependency advisories. It is only reasonable in production if you consciously accept owning the code, including forking it, from day one.
- Can I save or update Prismic documents with prismic-eloquent?
- No. The package is a read-only projection of content that lives in Prismic, so there are no transactional writes, no save() persistence guarantees, and no model events that fire like database events. Attempting to treat it as a full ORM leads to bugs that look like ORM problems but are really architecture mismatches. Write operations should go through Prismic's own APIs or the official SDK.
- How do I query Prismic content with Eloquent-style syntax in Laravel?
- You define a model per Prismic custom type and then use a fluent query surface that mimics Eloquent, such as where-style filters on fields and slices. Each call translates into a request against Prismic's HTTP API, so query count equals API calls. Chain your filters carefully and cache results where the content does not change often.
- Does prismic-eloquent work with Prismic's current API and official PHP SDK?
- The package was written against Prismic's API surface as it existed in 2021, and Prismic has since moved its clients and query conventions forward. If the request shaping no longer matches the live API, the failure appears at runtime rather than at install time. The official Prismic PHP SDK is the supported path today, and this package does not track it.
- What happens when an editor changes a Prismic custom type field?
- Casts, accessors and attribute mappings in your model classes are coded against a schema that editors can change without a deploy. A renamed slice or changed field can silently break casts, throw in accessors, or render empty pages in production. There is no migration file to diff against, so you need a content modeling change process on your side to keep deployed models in sync.
- What are the alternatives to prismic-eloquent for Laravel and Prismic?
- The main alternative is the official Prismic PHP SDK, wrapped in your own thin repository or service layer so the query surface stays under your control. That keeps you on a supported client while still giving controllers a friendly API. Forking this package in-house is another option if you want the Eloquent-style ergonomics and accept the maintenance cost.
- How hard is it to fork and maintain prismic-eloquent in-house?
- The codebase is a thin adapter that maps Prismic responses onto model classes and exposes a fluent query surface, so the code itself is small. The real cost is ongoing ownership: tracking Prismic API drift, updating a 2021 dependency tree with EOL branches, and writing tests that hit a live Prismic repository. Decide up front whether you have someone to carry that indefinitely.