Daniel Iser
Forum Replies Created
-
Its simple to point the finger and say their plugin did it, but in my experience that usually just masks a problem somewhere else.
Generally speaking any conflict requires at least 2 or more parties. So even if its on their end, we can investigate to harden our code against such failures if possible. This could mean it resolves random issues other users are experiencing with plugins other than yoast.
Your call. Let us know, happy to close this and move on if you are.
- This reply was modified 2 years, 5 months ago by Daniel Iser.
@acreativity – 100% affirmative. Content Control Pro offers the ability to both make restrictions targeting users based on purchase history, but also active subscriptions & many other things.
You can create New York Times style content teasers with a few clicks with the Teasers addon.
Hope that helps.
@goodcall1 – If we set you up with a private WP site to duplicate the issue, do you think you could replicate it reliably for us to use to see if we can resolve it with changes on our end?
If so submit the support form on our website and ask for Sarai, she can get you a site you can use to reproduce it for us without using your own.
@hqraja – I’ve added this to our feature request board so we can look at offering it in the future.
@delrod – That is on our list for this year. We are looking to add our own payment integration with Stripe & Paypal offering basic subscription management.
At this time though it does require using another plugin to facilitate the payment/membership part, our plugin can then be used to lock down your site with more precision than is typically offered.
That said our Pro offering includes ways to restrict content beyond user roles, such as if they have purchased a specific product or have an active subscription with popular WooCommerce & Easy Digital Downloads integrations.
This means you can skip a “membership” plugin to manage adding roles and changing levels etc, and simply sell subscriptions. Our plugin doesn’t have to rely on roles and can work on any conditional user data.Hope that helps.
- This reply was modified 2 years, 5 months ago by Daniel Iser.
Also, our plugin file path would be popup-maker, not popupmaker, so I’m really not sure what I’m looking at. Look forward to your email.
@rohitsapna – Can you please submit a ticket on our website with full details? I’m not even sure I understand what your claiming or how it could be attacked without more context, and best to not disclose it publicly right away if there really is an issue, at least until the patch is released to the masses.
@mlplus – I’ve patched the nav menu links issue, it will be in the next update.
Let me know about the other 2 issues.
@blackandbluebird – Its possible that they don’t play by the normal WP rules for checking pages. WooCommerce does the same, for example
is_page( 'shop' )returnsfalseon theshoppage and requires special considerations.I’ll try to test it, but assuming we do need to add custom rules like we do for BuddyPress and WooCommerce, those will end up being added to our Pro version at this time.
I’ll ping you with my findings.
@rpoulin80 – You should be safe to update anyways. We are only officially supporting the last 3 major versions, but I suspect it should still work fine on 6.0+.
I might have to add some filter or constant that forces it to activate on those versions if you can’t get it to just work on your version, our code may be triggering it to not initiate due to the low version, which was an unintended consequence and we may be able to address it.
We want to start limiting our support for older stuff, but not necessarily require the new stuff to run it if its not needed.@mlplus – Hmm, first we’ve heard that. Gonna break your report down into separate parts:
Admin Issue
Every change exits the navigation item
Looking at it just now on my dev site, I’m not seeing any issues in the admin when inserting a Navigation block, then adding rules to individual menu items. This is the same for both in page or Full Site Editor.
For confirmation I added both user rules & device rules, there was no jumping or switching blocks.

Can you try one of our demo sites and see if you can replicate it there? If not it would suggest a conflict with another plugin which we can help you narrow.
User Rules applied to nav menu items
This one I confirmed just now, though if its not working, it may suggest the nav menu item blocks do not get run through known filters for removal/replacement
I’ll dig into the core code there, but its actually possible at this stage that there is no filter to allow handling that for those block items. Our device controls are managed by adding classes, user rules are applied by removing blocks entirely via specific filters. Clearly these aren’t using that.
Shortcodes block controls not working
I was also not able to duplicate this. Adding a non-existent shortcode for a test as it simply renders itself, the block does hide for device controls & user controls for me.
One thing to keep in mind is, admins are excluded from restrictions by default, so you may need to disable that in plugin settings.
Recapping I only can confirm one of these 3 issues, the other 2 I wasn’t able to duplicate.
Feel free to try and reproduce them on one of our clean demo sites: https://app.instawp.io/launch?t=content-control-pro-demo—star-wars-theme&d=v2
As for the 1st & 3rd issues, I suspect a conflict with another plugin or theme, but its hard to say without narrowing it down. You can use the Health Check & Troubleshooting plugin to do that via its Troubleshooting mode if you like.
Will work on the menu item user controls issue and see what I can come up with.
@blackandbluebird – Glad you got it worked out, caching can be tricky some times.
@billyrobertsgws – Sorry to here that, had typed up a much longer more thourough response but lost it due to accidental refresh, so here is the short version.
We use Cloudways as well, and haven’t seen any issues, nor have there been any similar issues reported, so I’m gonna rule out hosting or actual file permission issues in our code on its own.
Couple of questions to help narrow what code of ours is having an issue:
- Have you entered a CC Pro license key?
- Do these errors happen every page load, or are they occurring during on of our data upgrade processes?
If no key & not during upgrade process, it indicates our logs are attempting to write data, this on its own shouldn’t be a problem as its doing so in existing folders that don’t need permissions generally.
If its logging does adding the following make it stop?
define( 'CONTENT_CONTROL_DISABLE_LOGGING', true );There are only 3 places in our plugin that can write files at all. And the questions above should determine which it is.
In any case I’d assume due to lack of other reports that the issue is being caused due to a conflict with another plugin, theme or custom code, so next would be narrowing that down using the Health Check & Troubleshooting plugin’s Troubleshooting mode on our plugin alone.
You should install the Twenty-Twenty-Three theme as well before using troubleshooting mode for best results.
Retest, if the issue is no longer present its not from our plugin (alone at least).
- Enable a few more plugins in troubleshooting mode
- retest, repeat until you see the issue again.
- disable the last few plugins one by one until it clears up again.
- The last on disabled is the culprit we need to look at.
- If no plugins cause the issue, activate your normal theme (top toolbar).
- Retest.
If you still don’t see the issue, you likely have custom code in an mu-plugin or parent theme etc that is causing trouble.
Let us know what you find.
@ercanakcay – Though your welcome to rollback, it wouldn’t be my first or even last suggestion. That is effectively saying I’m ok that my theme breaks things it shouldn’t. Leaving it will lead to future issues with other plugins if not ours.
I’d be happy to look at this theme specifically, I haven’t seen it named in any of these tickets.
It generally means they are doing something they shouldn’t be (read outside the WordPress guidelines and documented methods). It should be addressed likely
In reality you rarely should need to use the Restriction editor in our plugin to select those pages, if you know the theme is the source of the issue, you could select all your plugins on the plugins page, then in the bulk menu choose Troubleshoot. This will efectively disable your theme temporarily, letting you make the needed changes in our plugins pages, then disable troubleshooting mode.
Since troubleshooting mode only effects your experience, its safe to use, and our settings once saved shouldn’t give you any issues.You are free to rollback, but we won’t be patching v1.x.x any further, so if any issues, bugs or security issues come up you would be left vulnerable.
Hope that clears up our position on this situation.
@derweili – That is not something we control, so if its possible with WP, its should be possible with our plugin. To be clear we call get_the_excerpt to generate excerpts by default, so that’s effecitvely where you should be looking to make the needed changes.
That said we are releasing a Pro version and some cool addons including Content Teasers such as those on NYT or Wall Street Journal. Its gonna be available next week. That solution does include a custom teaser generator that fully maintains all formatting and html structures, and can truncate chars, words, sentences or block level elements (paragraphs, divs, img etc).
You can try a demo of the early version here: https://app.instawp.io/launch?t=content-control-pro-demo—star-wars-theme&d=v2