Limit subscription per record field

I think yes, if you limit useage to 1 but not for field, for article submission in general.

Sergey I think yes, if you limit useage to 1 but not for field, for article submission in general.

Doesn't this restrict submission of article in general? I want for users to submit articles with fewer fields even if they do not have subscription. If they buy subscription then extra fields appear.

Did you try restriction on field level in Emerald tab? Restrict submission and try count limit parameter. Not sure how it behaves in detail... and if it works on record basis... or for all submissions of this field.

Then is is complicated. Every field will add it's own count. If user use only one field only one count. If you switch count limit off for some fields, then no restriction for those fields.

It is not designed to count individual submissions with by fields restriction.

Any thoughts on how I can make this happen?

Sergey It is not designed to count individual submissions with by fields restriction.

Somehow, the field's emerald restriction parameters implies to work like this. Especially the "count" parameter. What is the purpose and typical usage of those parameters (on field level). Can you give an example to "draw a better picture for a designer" ;)

klox7 Any thoughts on how I can make this happen?

No thoughts. As I have mentioned you either count fields or submissions. You cannot count submissions with restriction by fields.

pepperstreet What is the purpose and typical usage of those parameters (on field level). Can you give an example to "draw a better picture for a designer" ;)

For example you do not want fields counts to be applied but you want submission general restriction to be applied.

How will count limit for article submission in general work if I will have different languages? If I use 1 in count limit and use parallel translation will user be able to submit article only in one language?

Yes only 1 user can submit, emerald haven't any dependency on language.

So if I have 2 languages user will have to buy 2 subscriptions for 1 record (one original and one translated)?

Yes

Sergey

pepperstreet What is the purpose and typical usage of those parameters (on field level). Can you give an example to "draw a better picture for a designer" ;)

For example you do not want fields counts to be applied but you want submission general restriction to be applied.

Sorry but I still don't get the idea. I understand count limit for submission - if 1 you can only add one record. But what is count limit for field? If count limit in plan is 1 then what? You can add field 1 time in all your records? What If it's 2?

klox7 You can add field 1 time in all your records?

Yes. Every time field value is added count is increased. If you have 2 fields in a type with count limit ON, and both has values, then count of subscription will increase by 2. If there is only one field and your subscription limit is 2 then you will see this field in the form when create 2 articles. On third article field will be not accessible.

Pay attention on edit. If you do not protect it with subscription after add, youer will be always able to edit this field for free. So it should be protected for edit and count limit NO, so user may edit even when count limits was reached.

So for my main question it would be best to create separate subscriptions for each field and set count limit to 1 to restrict it to just one record?

But that opens another question for me. If I have 5 subscription (one for every field) than user must buy 5 subscriptions and that can be time consuming for some users. Does Emerald support "Buy multiple subscriptions at once" options? I know I can have one subscription plan and include multiple fields in it but then count limit can be used only in type settings for whole article submission (just as we discussed above).

Or could a developer make it so that I can link user subscription to specific article with multiple fields enabled. For example when user wants to add article it asks him "Which subscription you want to use with this article".

Somehow I'm still figuring out how to do "Buy subscription that enables extra fields (add, edit) but only for one record". If no subscription user can edit only fields that are free.

I'm trying to restrict article submission. I have this settings:

But I can still submit 2nd article. I mean when I click "Post here" for 2nd article it opens up a form.

From is open up, but you can save?

Yes I can save. But that wouldn't be ok. Why would you restrict article submission and let user to add entry anyway?

Because it is count unique URL. When you create new article, the URL is the same for all new articles. Once you create first, it will not count the same URL again. Only another URL. So it counts only unique URLs.

You have to set it Count every acces.

Sergey Because it is count unique URL. When you create new article, the URL is the same for all new articles.

So this applies to form url? OK will try with other option.

This will be possible with one exception. the full plan is the problem here. This have to have usuage limit number of fields it restrict. For example 4 fields. Then if usr adds only 2 fields, he will be able to add another article with another 2 fields. Or 4 articles with one fields.

To achieve what you want, count usage have to hav it's own number per every restriction. This is something we are looking into for the future.

What I would do in your case, I would simplify it. Since fields data is not shown if user has no submscription, I would allow to add all fields without restrictions. And I would just restrict article submissions to 1. this is set of paramters

Plan 1 Show all fields

• Usage limit 1
• Count mode Every URL

Plan 2 Show field telephone

• Usage limit 1
• Count mode Every URL

Plan 3 Show field website

• Usage limit 1
• Count mode Every URL

Type settings

• Submision restriction Plan 1, Plan 2, Plan 3
• Count limit Yes

Field telephone

• Display restriction Plan 1, Plan 2
• Count limit No

Field website

• Display restriction Plan 1, Plan 3
• Count limit No

Somethign like this.