Merhaba arkadaşlar. Bahsi geçen pluginin Wp de çalıştıramadım bir türlü. Plugini aktif ediyorum çalıştırıp içerik girdiğimde ise hazırlanıyorda kalıyor. Bu satıcının söylediğine göre Cron ile ilgili ve cron ile ilgili tüm işlemleri yaptım ancak başarılı olamadım. Bu arada hem localhostta hemde normal hostta denedim aynı sorunu yaşadım
Yardımcı olan tüm arkadaşlara şimdiden teşekkür edeirm.
Ayrıca Access log kayıtlarım;
::1 - - [05/Sep/2018:09:38:37 +0300] "GET /wordpress/wp-admin/edit.php?post_type=scrape&scrape_id=9&_wpnonce=6655899e80&scrape_action=start_scrape HTTP/1.1" 302 -
::1 - - [05/Sep/2018:09:38:39 +0300] "GET /wordpress/wp-admin/edit.php?post_type=scrape HTTP/1.1" 200 39345
::1 - - [05/Sep/2018:09:38:41 +0300] "POST /wordpress/wp-admin/admin-ajax.php HTTP/1.1" 200 109
::1 - - [05/Sep/2018:09:38:41 +0300] "POST /wordpress/wp-admin/admin-ajax.php HTTP/1.1" 200 47
::1 - - [05/Sep/2018:09:38:41 +0300] "POST /wordpress/wp-admin/admin-ajax.php HTTP/1.1" 200 109
Uyguladığım Adımlar;
Troubleshoot – My tasks are always at “Preparing” state, why?
In order to troubleshoot this issue, please follow the steps bellow. You can also contact us from https://codecanyon.net/user/octolooks#contact with your WordPress login credentials if you need further assistance.
If you use ionMag WordPress Theme, please continue with this step otherwise you can skip to next step. You should modify the wp-content/themes/ionMag/includes/wp_booster/td_cake.php and file td_js.php.
f unction _schedule_mod ify_add_three_days() {
t o
f unction _schedule_mo dify_add_three_days($schedules) {
After you edit and save the file, re-save your task to check if is it working as expected or not. If it’s not, please follow the next step.
If you duplicated any of your tasks by clicking “Copy” button, please continue with this step otherwise you can skip to next step. Duplicated task will stay at “Preparing” state until you edit it. In this case, just re-save your task by clicking “Edit” button to check if is it working as expected or not. If it’s not, please follow the next step.
In some cases, WordPress can’t insert the tasks into schedules and “Next Run” looks empty on “All Scrapes” screen. In this case, just re-save your task by clicking “Edit” button to check if is it working as expected or not. If it’s not, please follow the next step.
Try adding the code below to your wp-config.php file before the line “That’s all, stop editing! Happy blogging.”
d efine('ALTERNATE_ WP_CRON', true);
After you edit and save the file, re-save your task to check if is it working as expected or not. If it’s not, please follow the next step.
Next steps requires “Cron Manager by Duo Leaf” WordPress Plugin to check your cron jobs which you can install from https://wordpress.org/plugins/cron-manager-by-duo-leaf/ for free.
In some cases, cron job queue might be too long. If you use other auto poster plugins or pinging external websites option is chosen in your WordPress admin, you can see a lot of “do_pings” in “Cron Manager by Duo Leaf”. In order to reset your cron job queue, please run the SQL query below in your phpMyAdmin panel to clear the list;
U PDATE wp_options SET optio n_value = '' WHE RE option_name = 'cron'
After you run the query, re-save your task to check if is it working as expected or not. If it’s not, please follow the next step.
In some cases, other themes or plugins might be interrupting your cron schedules. Please check intervals from “Cron Manager by Duo Leaf” and see ”5 Minutes” to “1 Month” schedules in the list. If they are not in the list, deactivate all possible plugins and change your theme to WordPress’s default “twentyseventeen” for a while. If they appear, re-save your task then revert your theme and try to find which plugin is causing this issue afterwards. If they not appear, please follow the next step.
Call the URL http://YOUR-DOMAIN/wp-cron.php?doing_wp_cron withreplacing “YOUR-DOMAIN” from your browser. If your task is changing its status to “Running”, contact your hosting provider to find a clue about your wp-cron.php is not firing automatically. You can also check your Apache or NGINX error logs for more details.