开发者 | dartiss |
---|---|
更新时间 | 2024年11月1日 02:18 |
捐献地址: | 去捐款 |
PHP版本: | 7.4 及以上 |
WordPress版本: | 6.7 |
版权: | GPLv2 or later |
版权网址: | 版权信息 |
draft-concluder
folder to your wp-content/plugins/
directory.Because it helps you find an end to those annoying drafts that sit around and never get completed. And it's a pun on "draft excluder". Yes, I know - blame my SO, who came up with the name.
In Settings -> General -> Draft Concluder, you'll see, under the title, a status - this will tell you when it last ran and whether it was successful or not.
The success is dependent on whether any error was returned when sending out emails - a failure would indicate a problem with wp_mail
and will need further investigation.
The internal WordPress scheduler is an interesting beast. It's totally reliant on someone visiting your site for it to trigger - so if you set it to 1am but nobody visits until 8am then, yeah, you won't get email until after 8am.
Thankfully, I thought of you when I wrote the plugin. As per the previous question, there's a status on the settings screen. Additionally, there are 2 shortcodes that you can add to any post or page to help you out.
[dc_now]
- this will run the email generator and show, on screen, what would be sent if you were running it now.
[dc_last_run]
- this will show, on screen, what happened during the last scheduled run. So, if the status in the settings shows it ran, you can use this shortcode to display what was actually sent and to whom.
Heck, no. That's the beauty of this plugin.
I wouldn't do that. The email comes from the site's account - marking it as spam may also lead to all other site emails going the same way, including password resets and important security information. Look, if it means that much to you, maybe look to sorting out your drafts, yes?
...said no-one. But seriously, you want to remove the temptation, right?
Crack open your site's wp-config.php
and add the following line of code...
define( 'DO_NOT_DISABLE_MY_DRAFT_REMINDER', true );
And the deed is done - you can no longer disable the plugin (cue diabolical laughter).
No. It was developed for WordPress and so forks remain unsupported. I have no intention of developing and testing this on any other version.
selected
command for my settings output (thanks to Tom Nowell)