Dave McHale

Okay thanks for letting me know. I’ll mark this as resolved for now since it doesn’t seem to be an issue with this plugin, but let me know if there’s anything we need to know for a future update. Take care!

Hmm, there are no known issues with WooCommerce. Can you reply with the WooCommerce system status report? Maybe I can see if there’s an issue with a particular version. https://www.wpdesk.net/docs/how-to-get-woocommerce-system-status/

Is there an actual error happening, or is the whole screen simply white? And have you tried enabling WP_DEBUG yet to see if anything is in your error log? That may tell us where the smoking gun is.

Hi @dutchallianz

Thanks for using the plugin, sorry to hear you are running into issues though. The plugin should not block access to your whole website, so it sounds like another error is occurring. Have you tried enabling WP_DEBUG to see what error(s) are being thrown? Have you tried testing with all other plugins disabled? It sounds like there may be a plugin/theme conflict or an issue with your hosting environment in general. Can you provide more information about your setup? What version of WordPress, what version of PHP are you running, etc?

Cheers

Not a problem, clearly there was an issue on the site and if it was this plugin then obviously I want to fix it! I will close this as resolved, but do reach back out if you have any other problems. Cheers!

Thanks for those screenshots @ahmadegbaria000 . It does appear that your /posts endpoint is allowing access, but I tested a number of other ones from your screenshot and all of those appear to be properly protected. /pages, /blocks, /shipping_company, etc

Is it possible that a theme or another plugin is stepping in and also modifying your REST API access? If you could send me a list of the plugins active on the site and what theme you’re using I would appreciate it, and in the meantime I’ll look at things on this end to see if I can find a bug in the code.

Thanks! Talk to you soon.

Hi @ahmadegbaria000 Thanks for using the plugin! But sorry to hear you’re having trouble.

Can you provide more information on the issue you are having? The new functionality was tested quite a bit, and your old rules should have migrated to the new version when you upgraded. Are you certain that you are testing with a session that is not logged in?

Let me know, and I’ll be happy to look into it further. Thanks!

@marlimant glad to hear it’s working for you now, and not a bother at all. Take care and thanks for using the plugin!

@jdembowski Is there any way as a plugin author to change that for threads in my own support forums? I would love the ability to reply to threads that may otherwise be closed to everyone else. There’s a feature I pushed tonight which has been requested for quite some time, and I found that I can’t reply to a support thread from 6 months 3 weeks ago. I understand that’s a fairly long time, but I’d love to reply in that thread and tag the OP to let them know what they asked for back then is now available. Perhaps a “plugin author” role override could be allowed, even if the general public can’t necropost?

Hi @marlimant

Do you have any additional info you can share about the issues you’re seeing? That certainly should not be the case, since this plugin should not affect any REST endpoint functionality while you are logged into WordPress. What do you see in the network tab of the developer console – is there a specific error you can share?

Unfortunately I do not have access to an Oxygen license to test this myself, but am happy to look into it if you can get me more information.

Cheers!

Thanks for the positive review @brianrshim ! Glad you enjoy the plugin ??

@gerold1968 sorry no, nothing yet for this. Will have to do some extensive testing on this front since this kind of tool is probably going to end up being a “give the admin enough rope to hang themselves with” situation. I also have a fairly large feature update coming for the plugin already and want to that that pushed out before adding this, which HOPEFULLY itself will be out by week’s end.

@tai just tested this on a production site, working as expected! thanks for the update (and the release props ?? ) Cheers

@tai thanks for the update, seems to work after I forced a hard refresh!

To prevent possible issues with cached static files, you probably still want to update the “version” attribute on your wp_register_script() call that loads the file. Other than that, looks good on my end.

Looks to me like the function call to replaceFileNames() is happening ABOVE the actual UL with the ID of included-files-list in my markup. It may be best/safest across all themes to throw that function call inside of a DOM Ready check, to ensure it exists before it is accessed. I tested this on my server and it seemed to work. Just my $0.02

function replaceFileNames() {
	let c = document.getElementById('included-files-fie-on-wp-footer').innerHTML;
	document.getElementById('included-files-list').innerHTML = c;
}
jQuery( function() { 
	replaceFileNames();
});