mark l chaves
Forum Replies Created
-
Hey @ahortonserene,
Thanks so much for posting.
Have you tried switching to a default theme like Twenty Twenty-One?
Are there any errors in the browser console or error logs?
What does your site health tool say?
If you can reproduce the issue on a staging site, you can give us access and we can have a look. Just submit a ticket via our contact form so we can work out the admin access details.
https://code-atlantic.com/contact/
Cheers!
Hey @cecilior,
Since we don’t see that error on our end and no one else is reporting it right now, it might be something specific to your environment.
Did you switch to Twenty Twenty-One for your testing?
Did you make sure you turned off any custom code?
What does your site health report say? Any issues or PHP settings that are too low?
Lastly, you can also delete Content Control completely and do a fresh reinstall.
Let us know how that goes.
Thanks!
Hey @hermanhenskens,
We don’t see your
“Special info for Administrator only”
content when we visit your page. Here’s a recording.
https://share.wppopupmaker.com/7Ku6nkWj
It looks like the Content Control shortcode is working fine for us. You might want to add a message parameter as another test. Check out examples 2 and 3 here.
https://gist.github.com/marklchaves/230ba030334d9f3984cedd71e1dc9193
If you’re not seeing your changes, have you tried clearing all of your caches or testing on another computer?
If you’re still not seeing any changes, are you seeing any JS or PHP errors? How about DB errors? Are your PHP vars meeting minimum WP specs for your theme (check your theme’s docs)?
Also, the shortcode doesn’t do a redirect. You’ll need to add a restriction rule and select the redirect protection for that.
https://share.wppopupmaker.com/L1uWxd4g
Let us know if we missed anything.
Cheers!
P.S. This thread is closed. So, please start a new one if you have any more questions or run into any issues π
Hey @cecilior,
OK. That helps.
So (without seeing your site and backend), you might have a plugin or theme conflict. Can you follow this guide to figure out which plugin is conflicting with Content Control?
https://gist.github.com/marklchaves/90f5af8d0ea08d6e54254f2afb1109df
Let us know how that goes.
Cheers!
Hey @dgold75,
Just a heads up that we submitted a ticket to the WPB support team late last week. We haven’t heard back yet.
We’re going to close this thread here, but we’ll post an update if anything changes.
Crossing fingers π
Hwy @misulicus,
So, I interpreted your reply as “Have the customer check their subscription status in the account for the payment method they used (e.g., PayPal, credit card, Applet Pay).” In this case, it was PayPal.
Unfortunately, I couldn’t find any PayPal docs for instructions on how to check that. So, I borrowed a personal PayPal account and figured out that you can:
1) Log into PayPal.
2) View your transaction history and look for any recurring or subscription payments.
3) Open a recurring payment to view the details.
4) Finally, there should be a link to view all recurring payments. Click that and find the one that was canceled for some reason.
5) Check the status of the supposedly canceled subscription and update as needed.Hope that helps anyone else that runs into this problem.
Thanks!
Hey @cecilior,
Thanks for posting. Would you mind giving us more details?
1) What do you exactly mean by “It does not work.”? What steps did you take to set up your restriction (e.g., logged in vs logged out, all roles vs specific roles, custom denial message vs redirect)? What content are you trying to restrict? What steps did you take to test your restriction?
2) What kind of restriction did you add (i.e., custom message or redirect)? So, if you want a denial message to display instead of redirecting people to a login page, make sure your Protection tab settings are correct.
3) Have you tried clearing all of your caches and testing with an incognito browser?
4) Are you seeing any JavaScript or PHP error messages? If so, please share them with us.
Lastly, if you want us to take a closer look, can you submit a ticket via our contact form?
https://code-atlantic.com/contact/
Cheers!
Forum: Plugins
In reply to: [User Menus - Nav Menu Visibility] Custom Login Not the WordPress one’sHey @jonathanmayor,
Thanks for posting.
I was wondering if there where a possibility of using your plugin with custom user info I donβt want to use the WordPress oneβs
What do you mean by “custom user info”? Do you mean that you want to have a custom login (as in your subject line)?
You can definitely use a custom login with User Menus. That’s because User Menus simply calls WordPress’s built-in login code. All you need to do is make sure your custom login completely overrides WordPress’s:
1) Login page
2) Forgot password page
3) Register pageOnce that’s all done, when User Menus calls the WordPress login, your custom override should take over.
Shout if you have any more questions π
Cheers!
Hey @richards1052,
There are a couple of things you can check:
1) Make sure your popup is published and enabled. Here’s a quick demo of that.
https://share.wppopupmaker.com/Wnu76qAv
2) Open your browser’s console for the preview tab that opens. Check if there are JavaScript errors in the console for that tab. Screen capture the errors and share that with us.
https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#chrome
Please let us know how that goes.
Cheers!
Hey @tdouglass50,
Thanks so much for posting. The Content Control widget restriction stopped working around WordPress 5.8.2. Here’s the known issue report for that.
https://github.com/code-atlantic/content-control/issues/52
Sorry about that.
We also know there are display issues with the new block style settings in the admin area.
We’ve got that on our to-do list for an upcoming release.
We appreciate your patience π
Cheers!
Hey @polinsys,
Content Control restricts content based on roles. If you have a tag restricted to subscribers, all subscribers can see that content.
Let’s say we have a
subscriberrole and Jimi and Janis have that role (i.e., Jimi and Janis are subscribers).We also have 2 tags:
guitaristandsinger.We can create a restriction that lets only subscribers see posts that are tagged,
guitarist.That means both Jimi and Janis can see any post that has a
guitaristtag. But, any other role (e.g., editor), can’t see posts withguitarist. Lastly, all roles (including subscribers and non-logged-in people) can see posts withsingersince there’s no restriction on that.As you can see, to get your scenario to work, you’d need to have a role for each job title. And, that doesn’t sound scalable.
Does that make sense? We wish we had better news for you.
Shout if you have any more questions.
Cheers!
Hey @dgold75,
Just following up.
There was a recent post on this forum about a WPB image gallery conflict. We confirmed the issue and are doing more testing so we can report it to the WPB team.
Are you trying to use a WPB image gallery in your carousel?
We tested Carousel Anything with posts and images. The posts work fine, but the images have the same issue that we’re investigating now.
The workaround is to use the built-in WordPress Gallery shortcode instead of the WPB gallery.
Here’s a screencast that shows the differences between the 2 galleries side by side.
https://share.wppopupmaker.com/mXuxK0ko
Thanks!
- This reply was modified 3 years, 11 months ago by mark l chaves. Reason: Typo
Forum: Plugins
In reply to: [User Menus - Nav Menu Visibility] Compatibility with 6.0Hey @erikwirring,
Yes. User Menus is compatible with 6.0. We just haven’t updated the README yet. We’ll do that soon.
Just a heads up that User Menus is not compatible with block-based themes such as Twenty Twenty-Two.
Here’s the issue on GitHub for that.
https://github.com/JunglePlugins/User-Menus/issues/43
Let us know if you need anything else.
Have a great day π
Hey @engrrajonahmed,
We’re going to mark this thread as resolved since we haven’t heard back from you.
Please feel free to start a new thread or submit a help request π
https://code-atlantic.com/contact/
Have a great day!
Hey @antonzhu,
That’s a great question.
Out of the box, no. Content Control can’t mix logged-out and logged-in visitors at the same time right now.
Sorry about that.
If we decide to bypass our short circuit logic in a future release, you probably can do what you’re asking by creating 2 separate restrictions: one for logged-out visitors and one for logged-in administrator roles.
When the short-circuiting is bypassed, Content Control won’t stop at the first restriction that fails. That means if there’s a passing restriction in the stack it can find out and respect the second restriction if it passes.
Let us know if you need anything else.
Have a great day π