Field Paywall allows developers to replace fields on entities with a message depending on user permissions. It's useful for giving visitors teasers to content before advising them to sign up to see more.

Walkthrough video

A walkthrough video is available at with a full demonstration of how to use field_paywall and how to override field_paywall templates.

Why fields?

Paywall configuration is stored in fields because it allows developers to very easily retrofit paywalls to existing entities and export field configuration using tools such as Features. Paywalls can also be re-used across multiple entity types and bundles. Furthermore the position of the paywall can be adjusted using the Field UI display configuration.

It may seem a bit strange at first using a field to hide other fields, but it's proven a very flexible, easy to configure, easy to export and highly maintainable approach.

Project Information