It it happened in the latest version only, it should be investigated. At my own sites it works correctly and I have no complains from other customers. That meas it something special in your case. Please export a problem feed's setting (just one, not a bunch of them) into a file and send it to Login to see this link
Course I should post this link to a manual here again, but I believe you know about it and I assume you don't use WordPress cron emulator at your sites. Anyways, here is the link: Login to see this link
I've checked your feed settings and got no double posts at my test site. Please make sure you are using a server cron pull mode. This is the only way to avoid any possible issues with double posts, because WordPress pseudo cron is not reliable. It may generate double posts on sites with a large amount of traffic. The server cron solves this problem in 100% cases.
Also make sure you don't pull the feeds very often. Please read this: Login to see this link
8:01 pm
CyberSEO said
CyberSEO Pro 10.022 has got a serious revision for WordPress pseudo cron. Now it should not generate duplicated posts even in "auto" mode. It's still recommended to use the real server cron, but "auto" mode got much more reliable.Please make sure to update your CyberSEO Pro core code.
It has been set to cron from the beginning but after I add a new feed I will run a pull from all at that time. Still whether it is cron or me clicking pull it shouldn't pull duplicates when the settings are supposed to prevent that correct?
8:07 pm
CyberSEO said
As it explained Login to see this link, it depends on the time your server needs to process the feeds and on how often you pull them. If you pull them faster that your server physically works, you get the duplicates.So my question is at what intervals does your cron work?
It's set to check every 10 minutes
8:20 pm
CyberSEO said
Set it to 20 minutes. Also make sure that the cron triggering period is about twice longer than the maximum PHP execution time limit. Please read the thread I gave a link to above. It explains how the system works.Also make sure you have only one single cron job running for that site.
0 | * | * | * | * |
IS_CRON=1 php -q /home/zothnet1/fetishtube.tk/cron.php
|
- I don't understand what your cron.php script really does. Can I see its code?
- Can you be sure it's not called by someone else. E.g. if I add the URL of your cron.php to my webpage and set it to refresh by JavaScript every second, what will happen to your site? What if I do the same via 100000 threads at the same time? Won't your server be DDoS-ed to death? Can you be sure that nobody else does it right now?
This is definitely not a way you should use cron with CyberSEO Pro. Open its General Settings page, find the "RSS pull mode" and and find the exact URL with a secret parameter that must be triggered by your cron. From what I see above, you do it wrong.
Your cron job must look like this:
Login to see the code
It should be pulled by curl and never run by php.
I don't know what exactly your cron.php really does, but it must be deleted from your site ASAP, because it's an open door for an easy DDoS attack.
8:42 pm
CyberSEO said
- I don't understand what your cron.php script really does. Can I see its code?
- Can you be sure it's not called by someone else. E.g. if I add the URL of your cron.php to my webpage and set it to refresh by JavaScript every second, what will happen to your site? What if I do the same via 100000 threads at the same time? Won't your server be DDoS-ed to death? Can you be sure that nobody else does it right now?
This is definitely not a way you should use cron with CyberSEO Pro. Open its General Settings page, find the "RSS pull mode" and and find the exact URL with a secret parameter that must be triggered by your cron. From what I see above, you do it wrong.
Your cron job must look like this:
https://fetishtube.tk?pull-feeds=A_VERY_SECRET_CODE_HERE
It should be triggered by curl, not by php.
I don't know what exactly your cron.php really does, but it must be deleted from your site ASAP, because it's an open door for an easy DDoS attack.
Sorry I posted the wrong one. Here is the right one changed:
Login to see the code
Most Users Ever Online: 541
Currently Online:
13 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2853
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1640
Posts: 8352
Newest Members:
wanmarkets, torontomark48, info.ckmedianetwork, contact.mybeautystar, samuelbodde, john.prushAdministrators: CyberSEO: 3947