Skip to content
This repository has been archived by the owner on May 26, 2023. It is now read-only.

Behaviour of modified plan features #35

Closed
boryn opened this issue May 13, 2021 · 2 comments
Closed

Behaviour of modified plan features #35

boryn opened this issue May 13, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Milestone

Comments

@boryn
Copy link
Contributor

boryn commented May 13, 2021

As far as I understand, when the plan features change, users stay with the "old" features rules? One needs to use $user->subscription('main')->syncPlanFeatures(); to reflect changes in the user's configuration?

This part of syncPlanFeatures() is only mentioned in plan-subscription-model.md - I think it's worth mentioning as well in the plan-subscription-feature-model.md because it's not that obvious.

What if we would need to update feature set for all the users? Will syncPlanFeatures() work on the Collection of subscribers?

@bpuig bpuig added the documentation Improvements or additions to documentation label May 13, 2021
@bpuig
Copy link
Owner

bpuig commented May 13, 2021

Ok, I'll try to improve docs.

What if we would need to update feature set for all the users? Will syncPlanFeatures() work on the Collection of subscribers?

Yes, you'd have to loop every user. I think it's a bit difficult to mass update, since there are some comparisons there. I'm no expert, but if you come with a method to mass update I'd be glad to implement it.

@bpuig bpuig added the enhancement New feature or request label May 13, 2021
@bpuig
Copy link
Owner

bpuig commented May 13, 2021

Added d0bcefd

If you think it's enough, you may close this issue.

@bpuig bpuig added this to the v4.0.0 milestone May 13, 2021
@boryn boryn closed this as completed May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants