WordPress.org

Ready to get started?Download WordPress

Forums

Subscribe2
[resolved] Deluge of digests, mulitple unique messages sent (6 posts)

  1. belg4mit
    Member
    Posted 10 months ago #

    This morning Subscribe2 sent everyone 30 separate copies (different Message-IDs, examples below) of the digest over a 74 minute period. Double plus ungood. Other jobs do not seem to be so repetitious.

    Message-ID: <66023b94c36203c16b89b36284770981@sciencefromscientists.org>
    Message-ID: <f8b1501359bc00f88aafdde06e60ad3e@sciencefromscientists.org>
    Message-ID: <30ff8e5b0ec939ab0dc594ace5130fdf@sciencefromscientists.org>

    Not sure if this related to the loss of "cron" job from last week.

    http://wordpress.org/plugins/subscribe2/

  2. mattyrob
    Member
    Plugin Contributor

    Posted 10 months ago #

    @belg4mit,

    There seem to be a few issues currently with the WordPress cron that I'm getting at the moment and so far all of these have been due to server configuration breaking the expected cron functionality.

    The WP-Crontrol plugin is an excellent tool for making sure that the cron tasks are being called and execute regularly and successfully.

    Also, the wp-config.php file can be amended to use fallback cron code as discussed here.

  3. belg4mit
    Member
    Posted 10 months ago #

    Yes, I used crontrol to replace the lost job last week. The job clearly ran, and there is only one of them.

    Nothing has been explictly changed in my server settings, only an upgrade to WP3.6 and update to Subscribe2 about two weeks ago.

    The alternate cron does not sound like a good idea i.e; not guaranteed, and meant as a fallback when things aren't running at all.

  4. mattyrob
    Member
    Plugin Contributor

    Posted 10 months ago #

    @belg4mit,

    When replacing the cron job I suspect there were still old subscribe2 cron database entries then. All being well, and if cron works correctly, you should be okay from now.

  5. belg4mit
    Member
    Posted 10 months ago #

    Unfortunately I am still getting a digest at every cron invocation for many invocations after the digest is first sent. And only the first digest has fresh content, the others only contain current sticky posts. The cron entry in wp_options does not contain multiple s2_digest_cron entries either...

    The "complete" digest also included posts that are weeks old, and had been reported on in a previous digest.

  6. mattyrob
    Member
    Plugin Contributor

    Posted 10 months ago #

    @belg4mit,

    Try re-setting the digest database entries by changing to per-post and saving the options and then returning your settings to your preferred digest period.

Reply

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.