[SOLVED] Error on Read Access to Content

7 years 3 weeks ago - 7 years 3 weeks ago #292659 by highonryan
[SOLVED] Error on Read Access to Content was created by highonryan
I have three subscriptions, a free member, a newsletter member and a supporting member.

I would like to block some articles (content), which may have public links, from both the public and free members, but allow newsletter and supporting members to see it.

I set up the three plan, but on newsletter and supporting member plans, I set:

Plan > Integrations > Content > READ: By Content > specific article (I also tried in content category and menu item)

The article, category and menu item are all set to public.

I go to the site, log in as free member, try to access the content, get a message saying I need a certain membership.

I go to the site as public, do not log in at all, try to access the content, the URL is really long, and I get an error that reads [an error occurred while processing this directive], or a 411 Request URI too long error

How to I get a message that tells the public to sign up for a newsletter or supporting membership (subscription)?

I have all subscriptions set up like this:
Exclusive = Yes
Validity = 1 Year
Maximum recurrings = unlimited
First Period Validity = No initial validity
Published = Yes
Allow New Subscriptions = Yes
Allow Registration = Yes
Allow to upgrade to this = Yes
Access Level = Public
Access Group = Public
Plan > Integrations > Extensions = No "By Component" "By Module" or "By URL parts"

What am I doing wrong? Why is this breaking for the public, and not logged in users?

**EDIT: It is also breaking for expired Free Membership accounts, too **

Thanks for any help,
HighOnRyan

Joomla 3.6.5
CB 2.1.2
CBSubs 4.1.0+build.2016.11.16.23.56.48.1a7e1aade

Please Log in to join the conversation.

7 years 3 weeks ago #292664 by highonryan
Replied by highonryan on topic Error on Read Access to Content
I realized my mistake.

Under Plan > Workflows I had some settings here wrong. I made adjustments and got this working.

Sorry for the hasty and needless post.

Thanks,
HighOnRyan
The following user(s) said Thank You: krileon

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.168 seconds

Facebook Twitter LinkedIn