[SOLVED] Debugging why GPL Content Protection Plugin

10 years 11 months ago #227187 by krileon
Replied by krileon on topic Debugging why GPL Content Protection Plugin
That's the only known issue and in all my tests, with the fix applied, it works fine (J2.5 and J3.0). Menu item protection does not hide the menu item. It protects the destination so the link must be clicked for it to begin protecting. Menu protection is also purely Itemid based so you may want to use By URL Part instead. It's also possible to set Usergroups to ignore the protection within CBSubs > Settings > Integrations > Content/Extensions; ensure you didn't set everyone to ignore its protection. Also ensure the CBSubs Bot is installed, enabled, and public as without it CBSubs Content will do nothing.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

Please Log in to join the conversation.

10 years 11 months ago #227414 by tbream
Replied by tbream on topic Debugging why GPL Content Protection Plugin
For the record, we've resolved this issue.

We never figured out why it was happening, but we simply did a restore to just prior to when the issue surfaced. All is now working as expected. Clearly, some odd-bit was set incorrectly.
The following user(s) said Thank You: krileon

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.186 seconds

Facebook Twitter LinkedIn