Subtotal: $84,990.00
In Live Articles, subscription (subscriber-only) content can be controlled through a combination of explicit permissions and Live Article settings. However, there isn't a way to inject subscriber-only content into a Live Articles template.
In other words, there is a token named "Article:no_permission_content" for injecting non-subscriber content into a template, but there isn't a token for injecting subscriber-only content, e.g. "Article:has_permission_content" and that is what this suggested feature addition is for.
Eric, Isn't the Article Content is the "Subscriber-only content"? Wouldn't [Article:content] meet your use case?
Article Content just injects the content of the article. There isn't a way to inject a subscriber-only message elsewhere in a template. For example, having a subscriber-only offer appear that has nothing to do with the article itself.
So basically you're suggesting that we introduce another Text Editor for subscriber only content for each article?
I suddenly realized that from your perspective this is a thin use case - that of having one instance of Live Articles, with all content defined within the built-in article/page hierarchy. It's probably redundant in that case.
For me, this request was driven by a setup whereby there are multiple instances of Live Articles, with each instance serving as an individual issue of a magazine-style bi-monthly Journal (www.birdobserver.org for those interested). In this example, the use case for this idea makes much more sense. I know that you discourage the above practice so can see why the idea should probably be dropped.