chexwarrior
Forum Replies Created
-
Forum: Alpha/Beta/RC
In reply to: Sitewide Basic Authentication and Application Password Causing Issues@timothyblynjacobs Confirming that this fixes my issue!
Forum: Alpha/Beta/RC
In reply to: Sitewide Basic Authentication and Application Password Causing IssuesThank you very much for your attention!
Forum: Alpha/Beta/RC
In reply to: Sitewide Basic Authentication and Application Password Causing IssuesVery much appreciated, thank you!
Forum: Alpha/Beta/RC
In reply to: Sitewide Basic Authentication and Application Password Causing IssuesHi @timothyblynjacobs, it is implemented via NGINX.
Forum: Alpha/Beta/RC
In reply to: Sitewide Basic Authentication and Application Password Causing IssuesI guess what I’d like to discuss is whats the best way to handle this? It seems like Application Passwords purposefully uses Basic Auth headers for authentication, in which case a site setup like my staging site is going to have issues whenever an anonymous user triggers an API request.
- This reply was modified 5 years, 5 months ago by chexwarrior.
Forum: Alpha/Beta/RC
In reply to: Sitewide Basic Authentication and Application Password Causing IssuesI don’t believe the plugin is at fault, when I debug the request it doesn’t even make it to the plugins code, it actually fails in authentication.
Forum: Plugins
In reply to: [Contact Form 7] Form submit only works when logged in to WP Backend@neubi Ah, maybe your reason is different, does the error still occur when you submit the form in a private browsing session?
Forum: Plugins
In reply to: [Contact Form 7] Form submit only works when logged in to WP Backend@neubi What version of WordPress are you using? I started getting this same 401 error on my forms submitted by anon users when I upgraded my staging site to the WordPress 5.6 RC2 release.
I should mention that this occurs even when I’ve disabled all other plugins and themes.
- This reply was modified 5 years, 5 months ago by chexwarrior.
Looks like it didn’t fix the issue, got the same error as before. My workflow is as follows:
All of my WordPress sites are built in Docker containers, I don’t think that should matter much for this but its just some background. I am using PHP 7.3.
When I build a site locally I run the following commands:
1. Install composer packages (I use wpackagist to install plugins/themes)
2. I wait for the Docker container with my database to be ready by continuously running the wp db check command until it stops giving an error (this always works with no issue)
3. I replace all instances of the production site url with a local site url using the wp search-replace, this is usually where the error occurs though I’ve noticed it happens with other wp cli commands if I skip this one.
4. I activate some dev plugins: wp plugin activate debug-bar query-monitor
5. I run wp core update-dbLike I mentioned previously it doesn’t seem to matter which wp cli commands I skip or run this error eventually occurs so I’m assuming it happens as soon as one of the wp cli commands loads wp core and initializes the plugins. Running the wp-cli commands with —skip-packages does fix the issue, but I was hoping to not have to use that option.
Hi all,
Been looking into this issue now that I have some time and I think I’ve narrowed down the problem to the blc_init function within the core/init.php file.
Like digitaldog mentioned the issue is a call to load_modules on a null object. The null object in question is the $blc_config_manager used within the blc_init method.
In the latest version of the plugin the activation.php file is required during the initialization of the plugin which in turn requires the modules.php file. When the blc_init function is called during the WP init action it attempts to load the modules.php file using require_once, but since that file has already been required it doesn’t load and the $blc_module_manager variable initialized in modules.php is null and fails when it attempts to run the load_modules method.
Changing the require_once within the blc_init function to requires seems to fix the issue but I have no idea if this might cause other issues, haven’t tested it enough yet. Maybe the dev team can shed some further light on the issue.
EDIT: Just to be clear this error only seems to occur when I use wp-cli command as I’m bringing up the site.
@digitaldog247 @wpmudev-support2
- This reply was modified 5 years, 8 months ago by chexwarrior.
- This reply was modified 5 years, 8 months ago by chexwarrior.
Hi, just wanted to add them when I updated to the latest version of the plugin (1.11.13) I also get this error when running wp-cli commands.