Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade showing non-existant Premium features link #2220

Closed
fly-man- opened this issue Dec 28, 2018 · 6 comments
Closed

Upgrade showing non-existant Premium features link #2220

fly-man- opened this issue Dec 28, 2018 · 6 comments
Assignees
Labels

Comments

@fly-man-
Copy link

After an update of MonicaHQ Open Source version, Activity type categories and Features are now Premium features ?

"This is a premium feature that requires a Paid subscription to be active. Upgrade your account by visiting Settings > Subscription."

However, there's no Subscription link in Settings that points to it and why has this "crept" into the Open Source version ??

@tbirrell
Copy link

tbirrell commented Dec 28, 2018

I am experiencing the same issue despite the fact that I have REQUIRES_SUBSCRIPTION=false in the .env and account.has_access_to_paid_version_for_free is set to 1 in my DB. I have dumped the output of hasLimitations() and it returns false so I suspect the issue is in the Vue component, but I'm not familiar with Vue and have not figured out what it thinks the value of limited is.

@ahilles107
Copy link

I have this same issue after upgrade.

@tbirrell
Copy link

I think the problem is in resources/views/settings/personalization/index.blade.php. Specifically the limited="{{ auth()->user()->account->hasLimitations() }}" portions of the component tags. I think what is happening is that hasLimitations() is returning the correct value, but it is getting passed in as a string and then cast to a boolean. The issue, therefore, being that a string naturally resolves as true, regardless of the value of the string.

I'm still digging around the code, but for those who host their own instance and want a quick fix, remove the limited="{{ auth()->user()->account->hasLimitations() }}" portions of the component tags. limited currently defaults to false, so it should go back to the expected behavior once we stop trying to pass in the value from outside.

@djaiss
Copy link
Member

djaiss commented Jan 1, 2019

Really sorry this happened.
We are going to fix this asap and make a new release.

@djaiss djaiss self-assigned this Jan 1, 2019
@djaiss djaiss added the bug label Jan 1, 2019
@djaiss
Copy link
Member

djaiss commented Jan 1, 2019

This has been fixed. Also, #2239 which should fix related stuff. I'm creating a new release right now and it will be ready in an hour. Sorry people, really.

@djaiss djaiss closed this as completed Jan 1, 2019
@github-actions
Copy link

This issue has been automatically locked since there
has not been any recent activity after it was closed.
Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants