Log In
Home
Related Topics
(0 votes) 10:23 am
March 25, 2017
Offline
Hello, I see some problem when using cyberseo.
1. Cyberseo freuqntly freezes when parses big numbers of posts, like thousands at once.[This is my way of importing, later I drip the posts…]
I need to repeat this proccess every time again, example: I want to parse 3000 posts at once, I set up it to shuffle feed contents, cyberseo pulls around few hundreds posts, later it freezes, I need to repeat this proccess again and again until I will import my desired number (of 3000 lets say).
Any idea how to fix it ? It looks like internet connection is frozen or lagged somewhere, and browser stops responding to server, thats why cyberseo stop the importing proccess…[thats my diagnosis — true ? ] Possibility to fix it ? Maybe some refreshing connection back echo or whatever to keep connection alive ? Problem exists on very good internet speed and various ISPs with good pings.
2. Similar problem with modyfing large quantities of posts. example: i want to modify post titles of few thousands posts. i use global synonim table for that. cyberseo freezes after modyfng just few hundred posts. Its impossible to finish the task of modyfng titles of few thousands posts, as it starts over and over again from the first position…so it modyfies the same posts all the time, always freezing after first few hundred. How to use it properly on blogs with thousands of posts ? Once again: various ISPs, good pings, fiber optic etc.
Thanks :)
3:06 am
July 2, 2009
Offline
There is only one way to fix it is to increase the maximum PHP execution time: 
Login to see this link
4:44 am
March 25, 2017
Offline
Hello, I may do what you suggested, however I’m not sure if that will solve the problem. Why ?
Because cyberseo parser works for various periods of times without “freezing”, sometimes it is 5 minutes, sometimes it is 10 minutes or even 20 minutes.
However post modification tools function while changing post titles using syn. table always freezes just after few minutes.At the same time
5:12 am
July 2, 2009
Offline
I’m not sure what do you mean of “freezing”. It’s a PHP script and it runs every time when launched till the end of the task.
7:30 am
March 25, 2017
Offline
admin said
I’m not sure what do you mean of “freezing”. It’s a PHP script and it runs every time when launched till the end of the task.
by freezing I mean not cold :), but freezing like it stops for no reason without finishing the tasks (it says working, browser “works”, but nothing happens)
Like I said the times after it stops are different for both parsing (for parsing they vary and are different all the time, sometimes it stops after 5 minutes, sometimes after 15 minutes) and modifying post titles with syntax table (it stopped always after few minutes, like around 2), so I doubt that it depends on that php variable…
7:47 am
July 2, 2009
Offline
The plugin does not stop itself, especially w/o a reason. Your PHP engine stops it when it runs our the execution time. And yes, it fully depends on the maximum PHP execution time. Otherwise you will get a error message. That’s how PHP works.
9:37 am
March 25, 2017
Offline
admin said
The plugin does not stop itself, especially w/o a reason. Your PHP engine stops it when it runs our the execution time. And yes, it fully depends on the maximum PHP execution time. Otherwise you will get a error message. That’s how PHP works.
So how would you explain that it stops in various times, if variable (php setting execution limit) has only ONE value ?
times of stopping are different for parsing cvs feeds and different for modyfing post titles (this is the only action when it stops ALWAYS at the same time, ~2-3 minutes I guess).
for parsing feeds it stop after various times, always much longer than for post modification titles with spintax
9:49 am
July 2, 2009
Offline
I can’t explain anything w/o looking at your PHP message logs. You must enable WordPress debug mode. Add
define(‘WP_DEBUG’, true);
into your wp-config.php, pull the feeds and send the error report to my email. If there will be no error message, that means that your PHP execution time just run out.
All RSSMost Users Ever Online: 541
Currently Online:
8 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 64
Freedom: 61
MediFormatica: 49
B8europe: 47
saviulisse67: 45
Member Stats:
Guest Posters: 338
Members: 2653
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1541
Posts: 7776
Newest Members:
frajaros, federico_pac, rexfordkent, nick.jtsevents, christophe.megaphone, r94alvesAdministrators: CyberSEO: 3687