Daniel Iser
Forum Replies Created
-
Forum: Reviews
In reply to: [User Menus - Nav Menu Visibility] Very useful feature@savoym – Sorry I didn’t respond sooner. The plugin works great with the latest versions of WordPress, we just don’t really believe in pushing an update just to update the works with tag every time WP updates. Rest assured if any issues were reported they would get patched fairly quickly, at which point we would definitely update that value.
Otherwise we do test it with the latest WordPress RC’s (6.4, 6.5, 6.6 etc) well ahead of their release, and 99% of the time there are no issues to bother fixing.
Hope that helps resolve any confusion over compatibility.
Forum: Reviews
In reply to: [User Menus - Nav Menu Visibility] Annoying notice on staging creation@leadsquad – Sorry to hear your having issues. Can you tell me more specifically what notice your talking about?
@pileo, @arbitrhand – Sorry for the delay, if your able, please try the fixes here: https://github.com/code-atlantic/content-control/commit/afa565bc1d41648ddbbaca9a6459e8b288abcfd1
Would love a confirmation, but this should go our during our next release.
- This reply was modified 2 years, 1 month ago by Daniel Iser.
@shetts – Currently you can set this up quickly with WooCommerce ore Easy Digital Downloads along with Content Control Pro.
Pro offers the ability to customize which users rules are applied to outside of just user roles, this includes ecommerce purchase/subscription data.
Further WP Fusion integrates with our Pro user rules as well, offering the ability to restrict content based on user’s tags in your CRM or similar.
Lastly we are planning to create our own payment gateway/subscription management that will go in the free version, fingers crossed we break ground on this later this year.
Oh and you keep referencing “the script” or “this script” but made no mention of what you were actually referring to if you care to elaborate.
@edfrank – Feel free to submit a PR on our github. That said I’d have to review all of the changes your proposing as we along with dozens of other plugins are all doing a very specific way to ensure maximum compatibly. I wasn’t under the impression WP core had changed anything to fix the deficiencies we all (other plugins) made workarounds for, but happy to investigate. Got a link to any docs/make posts?
Oh and per the @moderator request, you can reach out for questions about our pro products on our site if the need arises: https://contentcontrolplugin.com/support/
- This reply was modified 2 years, 1 month ago by Daniel Iser.
@moderator – This isn’t really a question about the product at all, not a pro or free question. Seems more hypothetical what can we do type of thing. Our pro product doesn’t offer anything to this users question if that makes since. I’m just trying to answer in the most helpful way.
@waystar – In reality the philosophical question is not one easily solved, nor one we can provide a technical solution for via our plugin.
The truth is, if they can view the content, there is no stopping them from feeding it into the AI generator of their choice once they copy/paste it or even screenshot and OCR the text.
What your asking for would actually require the AI scraping tools themselves to respect some pre-defined boundary. Then we could implement that boundary on the protected content.
As for unauthed users seeing the content, that shouldn’t occur with our plugin, it doesn’t leak the protected content to the page hidden somewhere if that makes since.
If you find some W3C Standard for marking up HTML in a way that AI’s respect, we can definitely add it.
Also from their own FAQ:
“With respect to the servers that power Brave Leo, your browser will share your latest prompt, the context of your current conversation, and—when the use case requires it—the necessary context from the page you’re viewing. Note that once a chat is closed, all records of that chat are erased We do not collect identifiers that can be linked to you (such as IP Address), and no personal data is retained by Brave-hosted AI models. Brave Leo offers several models to choose from. If you select a model from Anthropic and submit Leo queries, that data will be processed by Anthropic for a period of 30 days, then deleted.”
- This reply was modified 2 years, 1 month ago by Daniel Iser.
@waystar – Happy to try and help.
I am not quite sure I fully understand the question so I want more info to be sure I answer thouroughly. That said currently our restrictions can be applied based on not only specific user roles but the pro version also can apply them based on ecommerce purchase history. That can’t be faked with any “bypass”.
The content is simply not rendered to the browser if the user doesn’t have the correct access. So even a scraper will see nothing.
This applies to the Rest API as well. So assuming your registration & purchase forms are secure there shouldn’t be a way to bypass it. That would require a backdoor or leaking of the content in some way.
If there are things we can do to prevent AI scraping entirely we are happy to look at those also for future updates.
Lastly if a person has access to your content and then lets LEO scrape the page while viewing it, I’m not sure there is anything that can be done to stop it, they are using a browser extension with raw access to the DOM elements. The only way it could skip some content and not others is if the developers made a way to designate content to be ignored, otherwise it just reads everything.
@billybidley – As I mentioned before there are caveats, but both our docs/tools & our support team would have been happy to help.
We even have a tool to help you get the correct selector built into the admin toolbar on the frontend: https://docs.wppopupmaker.com/article/147-getting-css-selectors
The problem you faced isn’t something we can account for easily, its often unique per site, per theme, and every site is different, every “button” or “link” users want to target is created a different way thus the selectors need to be specialized to each scenario, no way around it.
What you missed was that your theme, page builder or gutenberg button/link wasn’t just a link.
You likely added a class to that button like
my-custom-buttonthen set your popup trigger to prevent default on the selector.my-custom-button, but your page html was most likely:<div class="my-custom-button"> <a href="someurl.com">Link Text</a> </div>In the above case you would in fact not be preventing the default of the link, but rather the
<div>, but the<div>has no click event to prevent. So even if we do what you set it to do, nothing would change. Only the<a href>has a preventable event.In these cases, and if you followed the guide above, you would hopefully end up with a selector of
.my-custom-button a, resulting in it preventing the link itself from doing default action.Simple fix, but could definitely be frustrating if you didn’t ask for help or read the docs & use the tools.
@reneyoung – Awesome, glad its working. Do you use caching, that might explain it.
@cgl102770 – We couldn’t agree more. As the founder of Popup Maker (the original) it was disheartening to see a competitor not only use the same name after nearly 7 years of use, but also to see the ww.wp.xz.cn plugin’s team approve a second plugin with the same name, something they regularly don’t allow, but in this case there was “no issue”
All for competition but this is not honest competition at all.
@woottonwebby – Sorry just seeing this, best to start new threads for issues when your error is not exactly the same as the other reporters, especially as we close them and stop checking once confirmed they are fixed.
Added a patch for that which will go out in the next update.
@strid – Sorry to hear that. I can totally understand more tutorials would be helpful in getting started quicker. That is something we are working on actively right now if I’m being honest, building out more helpful content for each plugin over the next few months.
Also I’m not sure if you did find the docs we do have: https://contentcontrolplugin.com/docs/
That said the plugin can be used in quite a few different ways, to solve a variety of problems, so I can’t begin to guess where you might have had trouble, but our support team is excellent and we would be happy to help you get it up and working for your particular needs: https://contentcontrolplugin.com/support/