Daniel Iser
Forum Replies Created
-
@nobo73 Oh no, sorry to hear that, can you tell me what version of WP & PHP you have. We tested v2.0.0 extensively for months, though there are always edge cases we might miss.
If possible can you give me the full error message, that shows only the line, not the reason it errored.
Will get it patched as soon as we determine what went wrong.
- This reply was modified 2 years, 9 months ago by Daniel Iser.
@kokoruz I’ll add that we are super close, very likely within 1 week of releasing v2.0.
You can test out a demo at https://app.instawp.io/launch?t=content-control-v2-beta-test-sites&d=v2I assume your confirming those roles show up as available to select.
The only thing that comes to mind is that they register roles later than expected.
You might try forcing those roles to be in the list of roles earlier using this filter: https://github.com/code-atlantic/content-control/blob/master/classes/Roles.php#L23C29-L23C45Forum: Plugins
In reply to: [User Menus - Nav Menu Visibility] Remove Review Nag Notification@dickraney Typically this means you have JS errors on the admin page your viewing when you dismiss it, or PHP errors during the AJAX request that saves the dismissal.
Quick solution that is more effective long term is to install the Health Check plugin, then go to Plugins and use the “Troubleshoot” function on our plugin, this will disable all other plugins that could be causing the issue temporarily & only for you. Then dismiss it and exit troubeshooting mode.You can then either leave Health Check plugin or remove it.
This should explain it better: https://www.hongkiat.com/blog/wordpress-attachment-pages/
That said v2 is very close to release, and there will be a pro version. It will not initially support blocking actual media access, but we are exploring several methods to handle that in the future.
The reason it doesn’t do it now, this was a very simple plugin initially and to block access in a way that respects the variety of dynamic settings we already offer would be very un-performant. In large sites it could lead to slow downs and reduction in server perfomance we found unacceptable.As such it was never made a priority. Hope that helps.
Forum: Plugins
In reply to: [User Menus - Nav Menu Visibility] Remove Review Nag Notification@dickraney – This almost always indicates one of 2 issues:
- You have a Fatal PHP error occurring in the background preventing it from saving the dismissal.
- There is a JS error on the admin pages where you are clicking the X, causing the request to never get sent.
You might want to check your PHP error logs first, see if there is something there standing out. Could just as easily be another plugin throwing an error for example during the AJAX request.
Simplest solution is usually to enable Troubleshooting mode (Health Check plugin) and use it to enable only our plugin, dismiss it the notice, then disable troubleshooting mode.Hope that helps.
@expansion8933 This is on our list, but the complexity of doing this dynamically without imposing big performance penalties on the sites loading & server resources is not as simple as hiding content on each post etc.
We will likely have to build an index of all users/posts and whether they have access or not. Very few good ways to do this efficiently, and we won’t move forward with a solution that would impact site performance.@lotfreeman An alternative is to simply register your own custom shortcode with WordPress and point the handler callback to the class we use, though v2 is about to release and the code needed would change:
https://github.com/code-atlantic/content-control/blob/develop/classes/Controllers/Shortcodes.php#L28C10-L28C10In your case you would have to replace $this, with a reference to that class since our plugin has already loaded it, this is only usable for v2
add_shortcode( 'some_code', [ \ContentControl\plugin()->get_controller('Shortcodes'), 'content_control' ] );
^^ PS Haven’t tested this, purely theoretical.V2 core is in beta, v2 Pro & store are getting there 🙂
@markman111 – Appreciate the great feedback. We are in the process of releasing v2 of Content Control and it will offer a Pro version that does support a lot of rules based on WooCommerce.
It will also offer block level controls for both user status, but many other things, including devices, schedules etc.
Look forward to hearing your feedback after it goes live.
In the mean time if you’d like to try the v2 beta demo: https://app.instawp.io/launch?t=content-control-v2-beta-test-sites&d=v2
@branhampaul – Theoretically it could be disabled for specific bot types like search agents, but we’d have to do some research on it and it might end up as a pro feature for our upcoming v2 that goes into beta this week.
@momo360modena – Appreciate the report & your patience. Just patched this so it shouldn’t throw errors.
Will look to push an update this week for it.
In the mean time modifyclasses/Admin/Notices.php:261
Replace with$env = function_exists( 'wp_get_environment_type' ) ? wp_get_environment_type() : 'production';@sirotwo – In what way? The plugin will work fine for all of the sites if network activated, but currently no network wide restriction capabilities. It would still be per site, but I can add that to the list for possible future features.
@dcbaker keep us posted, we have a major update coming for this plugin so would be a great time to work out any edge cases.
@terry2124 – Based on what you’ve stated, the only conclusion I can draw is your browser or dns cache locally on your own machine may have memorized the redirects, only way to clear that is flushing dns and clearing browser cache/history to clear the redirects.
That said I want to clear up the technical possibilities:
- If our plugin’s code is not both installed and active, the redirects are not coming from it. This is simply how WordPress works, not something we set up.
- There are no stored files, no redirect lists in the database, they are processed live as the page is requested. We compare content being rendered to the rules you set and redirect if they match.
- The only way php file can be used after deleted is if its already in opcache that never expires, not ideal. But this also means your db is perma cached as well since again,
installed & active, and active status comes from wp_options table. - There are other plugins that provide similar redirect/protection under different guises, such as membership plugins, seo redirect managers. Its possible the redirect in question never came from our plugin to begin with.
Happy to try and debug for you, but given the files aren’t even installed, there is pretty much 0% chance our plugin is causing it now given all the steps you said you already tried.