I hadn’t planned on anything like that. But if you can be more specific and let me know exactly which constants and/or what you have in mind, I certainly will consider it.
Hi Jeff,
OK, so here’s the use-case I have in mind for my team:
We have a setup where we develop multiple projects working in a mixed env where some work is done locally, but each site ends the dev cycle on a pass-protected remote server for the client to review and accept. With the current state of the plugin, we’d need to manually install it on each deployed site and add configuration in the UI.
Ideally, we’d have 2 config variables, eg WP_CRON_BASICAUTH_LOGIN and WP_CRON_BASICAUTH_PASSWORD, that setup would render the admin form inactive and the plugin configured automatically. You can see a similar approach in WP Offload SES plugin:
https://deliciousbrains.com/wp-offload-ses/doc/settings-constants/
Thanks @nowakpiotrek, I will take a closer look and see about implementing for the next plugin update.
Sure, let me know if you need me to test it 😀
Just to follow up with this. Next version (2.3) adds support for the following constants (defined in wp-config.php):
WP_CRON_HTTP_AUTH_USERNAME
WP_CRON_HTTP_AUTH_PASSWORD
So in wp-config.php, you can do this:
define('WP_CRON_HTTP_AUTH_USERNAME', 'your-http-auth-username');
define('WP_CRON_HTTP_AUTH_PASSWORD', 'your-http-auth-password');
And done. More details about this in the Installation docs. Thank you for the idea, @nowakpiotrek 🙂
