By Pawel Malecki on Thursday, 06 February 2020
Replies 8
Likes 0
Views 784
Votes 0
The App Module Access can be applied to all plans or only to selected ones.
A useful feature would be the ability to disable a given module for another selected plan.

For example:
The user who has access to the BASIC plan receives access to the module, which is e.g. a description of how to get an additional SPECIAL plan.
If he buys a SPECIAL plan, the module with this information is no longer needed. An additional option in Module Access then disables the information module.
Hello Pawel,

Thank you for your suggestions but I do not quite understand your request here. You could setup two module access app and then configure it the way you want it correct?
·
Thursday, 14 May 2020 16:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Currently, whether the module will be displayed depends on the subscriptions the user has.

If the user purchases a specific plan, he gets access to a specific module.

I am talking about a solution in which the user gets access to a given module (whose task will be, for example, displaying information on how he can access the secondary plan).

However, after purchasing this secondary plan, this message is no longer needed and no access to the module is needed. However, this message is still displayed because the user has purchased the primary plan that gave him this access.

It would be enough to place an additional condition in the Module Access application, e.g. DISABLE ON ADDITIONAL PLANS.

Then I can choose: PRIMARY PLAN in the option Apply on selected plans.
In the Disable on additional plans option, select SECONDARY PLAN.

This would be a condition for switching off the module for any other plans.

If the user would have purchased only the basic plan, he will automatically see the module. After purchasing the secondary plan, the module disappears.
·
Thursday, 14 May 2020 17:21
·
0 Likes
·
0 Votes
·
0 Comments
·
If I understand you correctly you could already achieve this with PayPlans but in a different way.

1. Create an app with module access to "module A" for "plan A"

2. Create another app with module access to "module B" for "plan B"

This way, users with "plan A" will not see "module B" and vice versa. Is that the behavior you are looking for? Or am I missing anything here?
·
Thursday, 14 May 2020 17:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Only in my solution the user has both plans active.
To be able to use Plan B, you must have Plan A at the same time, without a basic one you cannot get a second.

So if plan A will give access to module A and plan B will give access to module B, with both plans both modules will be visible simultaneously.

However, I want the user to see module A having plan A, and after buying plan B that module A disappears - because it is only needed if the user does not have plan B
·
Thursday, 14 May 2020 17:49
·
0 Likes
·
0 Votes
·
0 Comments
·
I don't think this feature makes sense to be honest and it adds a lot of complexity. What if the user only has plan B and does not have plan A?
·
Thursday, 14 May 2020 17:51
·
0 Likes
·
0 Votes
·
0 Comments
·
I don't think this would complicate the module.
There is an occurrence condition and a second condition for blocking the module instance.
Both are associated with plans that are active.

In earlier versions of 3.xx this function was implemented by a plugin that could show and hide the content of both the module and the text in the article depending on the active plan / plans.

This could replace the module access application, but it is missing for the second attribute - the negative one.
·
Friday, 15 May 2020 03:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hm, to be honest I do not see how would this be beneficial to most users who use PayPlans but will monitor this thread to see if there are anyone else who are interested in having similar functionality.
·
Friday, 15 May 2020 15:32
·
0 Likes
·
0 Votes
·
0 Comments
·
I added this thread because this simple modification of Module Access would restore the functionality that was available in Joomla. Article Content Hider

https://stackideas.com/docs/payplans/administrators/legacy-documentation/joomla-article-content-hider

The ability to profile content for users with varying level (plan) of access was excellent.

Of course, you can always restore that component and this thread will not be needed.
·
Friday, 15 May 2020 18:09
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post