Home › Forums › Newsletter Plugin Support › Continously deleted 'newsletter' cron event
- This topic has 5 replies, 2 voices, and was last updated 8 years, 10 months ago by
szepe.viktor.
-
AuthorPosts
-
January 23, 2015 at 1:47 pm #14888
szepe.viktor
ParticipantCould it be that even though it is not a “Non-repeating” event it gets deleted after each run?
# wp cron event list +--------------------------------+---------------------+----------------------+---------------+ | hook | next_run_gmt | next_run_relative | recurrence | +--------------------------------+---------------------+----------------------+---------------+ | w3_pgcache_prime | 2015-01-23 12:35:39 | now | 15 minutes | | newsletter | 2015-01-23 12:43:43 | 24 seconds | 5 minutes | | w3_pgcache_cleanup | 2015-01-23 12:48:01 | 4 minutes 42 seconds | 1 óra | | w3_pgcache_prime | 2015-01-23 12:50:14 | 6 minutes 55 seconds | Non-repeating | +--------------------------------+---------------------+----------------------+---------------+
# wp cron event run newsletter
Success: Executed the cron event ‘newsletter’# wp cron event list +--------------------------------+---------------------+----------------------+---------------+ | hook | next_run_gmt | next_run_relative | recurrence | +--------------------------------+---------------------+----------------------+---------------+ | w3_pgcache_prime | 2015-01-23 12:35:39 | now | 15 minutes | | w3_pgcache_cleanup | 2015-01-23 12:48:01 | 4 minutes 14 seconds | 1 óra | | w3_pgcache_prime | 2015-01-23 12:50:14 | 6 minutes 27 seconds | Non-repeating | +--------------------------------+---------------------+----------------------+---------------+
January 23, 2015 at 1:55 pm #14891szepe.viktor
ParticipantThe schedule is missing:
wp cron schedule list +---------------------------+------------------------------------------------+----------+ | name | display | interval | +---------------------------+------------------------------------------------+----------+ | w3_cdn_cron_queue_process | [W3TC] CDN queue process (every 900 seconds) | 900 | | w3_pgcache_prime | [W3TC] Page Cache prime (every 900 seconds) | 900 | | hourly | Óránként | 3600 | | w3_cdn_cron_upload | [W3TC] CDN auto upload (every 3600 seconds) | 3600 | | w3_pgcache_cleanup | [W3TC] Page Cache file GC (every 3600 seconds) | 3600 | | twicedaily | Naponta kétszer | 43200 | | daily | Naponta egyszer | 86400 | | w3_minify_cleanup | [W3TC] Minify file GC (every 86400 seconds) | 86400 | +---------------------------+------------------------------------------------+----------+
January 23, 2015 at 1:56 pm #14892szepe.viktor
ParticipantI am very sorry. Your plugin was excluded from wp-cli run.
January 23, 2015 at 11:16 pm #14911Stefano
Keymasterwp-cli run? Can you explain me what’s?
January 24, 2015 at 2:57 pm #14915szepe.viktor
Participantwp-cli is – I quote –
a set of command-line tools for managing WordPress installations.
I prefer runnig background job (mail sending, backup, cache preload etc.) from CLI thus not putting load on the webserver. That is why wp-cron is disabled.
Now I run your main wp-cron event separately because Newsletter demands a more frequent run than other things (twice in an hour for others).wp --quiet --url=http://www.domain.hu/ --path=/home/user/path-to-wordpress cron event run newsletter
January 24, 2015 at 2:59 pm #14916szepe.viktor
ParticipantOh! And the run thing.
You can set skip-plugins in wp-cli config thus running WordPress faster from CLI.
-
AuthorPosts
- You must be logged in to reply to this topic.