[morsagmon]

The Product Specific Info field does not support the meta links (e.g. {product_link}) but it’s good enough for me to construct the final result.

Thanks!

[morsagmon]

Thanks.

Will that work with the squeeze form for free products?

Will the customer now receive TWO emails – one as specified in the “Squeeze Form Email Settings” and another one from the Product Specific Instructions settings?

[morsagmon]

UPDATE:

I simplified things a little bit, created only two segments: for levels 5-6 and not-for levels 5-6. All seems to be working fine now.

[morsagmon]

OK, I seem to have worked things out.

For some reason, the “Start Date” of the active level was cleared every time. I cleared browser cache and created a new user, everything works fine now.

[morsagmon]

This isn’t working for me the way described.

I have a user with the following levels:

4 – Start Date 1899-11-30 – Never Expires

5 – Start Date 2018-12-04 – 1 year duration

6 – Start Date EMPTY (why?) – 3 months duration

The user is marked as Expired, and I cannot modify this through the admin panel, it keeps reverting back to “Expired”.

I’ll mention that level 4 was the primary with the first purchase, level 6 was added using the API and then level 5 was added by another purchase.

I also checked the “When a member’s primary level expires, automatically set one of the non-expired secondary level as his primary level.” – not helping. Always goes back to “Expired”…

What am I missing?

[morsagmon]

OK, I made some progress, but still can’t get the logic to work for all cases.

Basically, these are the rules:

1. Level 5 or 6 = show content.

2. (Level 4 and not (5 or 6)) or (level < 4) = show “buy content” message

3. Not logged-in = show “log-in” message.

I now have the following (not closing the nested protection tag is not a mistake – if included, the second is ignored and just echoed to the browser):

[emember_protected not_for="5-6" do_not_show_restricted_msg=1]

"buy content" message

[/emember_protected]

[emember_protected for="5-6" do_not_show_restricted_msg=1]

[emember_protected for=4 do_not_show_restricted_msg=1]

Show content

[/emember_protected]

[emember_protected scope="not_logged_in_users_only" do_not_show_restricted_msg=1]

Please log-in message

[/emember_protected]

If levels 5 and 6 are not expired, for user belong to 4+5+6, the content shows OK.

The above shows nothing if the user belongs to 4 + 5 + 6 where 6 is expired (but 5 has not yet expired) – a scenario that should show the content, but nothing is shown.

Please advise on the way to solve this, or if the partial protection logic cannot support the above requirements, how would you go about it?

Thanks!

[morsagmon]

OK, the above issue is fixed, but now it’s not working right with stacked membership levels.

Please consider the below:

[emember_protected for=4 not_for="5-6" do_not_show_restricted_msg=1]

Buy Service Agreement message goes here

[/emember_protected]

[emember_protected for="5-6" not_for=4 do_not_show_restricted_msg=1]

Getting help for customers in service agreement goes here

[/emember_protected]

[emember_protected scope="not_logged_in_users_only" do_not_show_restricted_msg=1]

Please log in to get help message goes here

[/emember_protected]

Levels 5, 6 are stacked on top level 4, i.e., they are added levels on top of level 4.

Level 4 is a customer without service agreement.

Levels 5 and 6 are customer on service agreement (either one, or both, grants service).

The above always catches the first section, even if a customer belongs to 4 + 6 levels.

I also tried nesting as follows:

[emember_protected for=4 do_not_show_restricted_msg=1]

[emember_protected not_for="5-6" do_not_show_restricted_msg=1]

Buy Service Agreement message goes here

[/emember_protected]

[/emember_protected]

[emember_protected not_for=4 do_not_show_restricted_msg=1]

[emember_protected for="5-6" do_not_show_restricted_msg=1]

Getting help for customers in service agreement goes here

[/emember_protected]

[/emember_protected]

But it also show the first section always, and also these as text (as if they are missing opening tags):

[/emember_protected]

[/emember_protected]

What am I missing?

[morsagmon]

Thanks wzp!

So, I’d be happy to see support for this in future updates of the plugin: allow multiple memberships levels to be flagged in the “Reference text” field of a product in eStore (e.g. comma delimited levels: 4,5).

In the meantime, I’ll use the API to UPDATE membership level from my software, in the transaction of activating his license – I checked it and it works as I need – APPENDS the passed membership_level to the current level of the user.

Couple of things I’m still not sure about:

1. How do I set the baseline level (#4 in the example) for the stacked levels, so that when they expire they revert back to #4, and not any other one?

2. The annual support the user buys is a PRODUCT, attached to the membership level #5 (customer + yearly support) using the “reference_text field. The expectation is for auto-renewal or until customer cancels. Where do I specify that it expires after a year – at the PRODUCT properties, or at the MEMBERSHIP LEVEL properties (or both)?

[morsagmon]

Thanks!

[morsagmon]

Thank you guys.

I like the approach of creating a dedicated 3-free months level. How do I assign a new customer to BOTH level 4 (a customer) as well as this new level 6?

wzp, to answer your questions:

The SLM is required to purchase product #1 – not the support subscription. Buying #1 triggers the email with download link and license key. This is a one-time purchase.

When buying #1 – they automatically get 3 months of this new level 6.

When they buy a YEARLY service agreement (level 5, perhaps after the complementary 3 months they received), they either renew at the end of the year, or downgrade to level 4 (customer without support agreement).

I presume I can handle the downgrade with the above mentioned auto-downgrade) add-on.

[morsagmon]

Thanks!

Sounds like a fair approach.

The only drawback, I was trying to avoid, is that in order to analyze how many customers I have using product #1, I have to consider TWO items, instead of having it all accumulated under a single code.

Perhaps that’s a reasonable compromise, though…

[morsagmon]

Very well, thanks!

[morsagmon]

Thanks! I’ll go with your advise, then.

[morsagmon]

Ohhhh, I have the Product ID in the JASON stream coming back… Good.

You need to update your documentation to reflect that, here:

Software License Manager Plugin for WordPress

Thanks, admin!

[morsagmon]

Thanks, wzp.

So, I can sell multiple products (forget the variations) for which SLM will generate and send a license key, but I cannot distinguish, on the client side, which product was licensed based on these keys. Can I combine this license mechanism with the serial number feature, in such a way that I’ll have only a single serial code per each product that will be used for ALL purchases of this product, and from the client side use some API (if exists) to query if the provided pair of license key + serial code both belong to the product purchased? or some other way to achieve this? For this approach to work, I need the following:

a) be able to set only one serial code to be used for ALL purchases per each product.

b) Have an API to query from the client side about this serial number and make sure that the provided license key belong to the product for which the provided serial key is assigned.

Any alternative approach you may offer to be able to distinguish the purchased product on the client side?

[Author]

Posts