But basically this version adds extra bits to the Feeds list, consolidates (and fixes a couple of issues) with the Site admin interface and network admin interfaces and more importantly handles the feed importing on individual sites based on their own timezones.
Plus, I've added a few extra configuration options to enable more fine-grained control over processing and timings.
But basically this version adds extra bits to the Feeds list, consolidates (and fixes a couple of issues) with the Site admin interface and network admin interfaces and more importantly handles the feed importing on individual sites based on their own timezones.
Plus, I've added a few extra configuration options to enable more fine-grained control over processing and timings.
We're are still not seeing any feeds process. We manually processed and "next check" time has come and gone and is in the past .... Since we have to manually, we've noticed that in the Network Admin section, the pre-existing issue with trying to check all feeds and process them all at once still exists. The only way to process feeds is to process each one by one ... checking all and clicking the "Process" button has no affect.
We also have a user who has processing and last checked stuck significantly in the future (tomorow, the 4th), so manually processing his feeds does nothing. Using the reset plugin and deleting the feed altogether and re-creating it also have no effect as the processing times again revert to the future ...
If you've got access to the database, can you check the wp_autoblog table and reset the lastupdated field to 0, and the nextcheck field to a timestamp of a few hours or a day ago:
Also, version 3.5.3 is out now, but it's only a fix for some non-multisite functions - will get the update notifications sorted, we're still not sure why it's ignore autoblog but we're getting closer.
Every feed has it's own value for lastupdated, it sounds you are asking me to change a singular value though, is this correct? If so, I may not be looking in the right place. Since the feeds only run if we manually process them, all nextcheck times are in the past, they only get updated when we manually process. We are on 3.5.3.
The same issue where feeds do not process occurs for us on other multi-site installs as well.
There are only two places that determine whether a feed should be processed or not - the nextcheck field in the autoblog table and the autoblog timestamp that can be reset with the reset autoblog add-on.
The only thing I can think of is to remove those checks from your installs and see if the feeds process then, that way we can determine which part is causing the main problem.
I'll put together a replacement autoblogprocess file and upload it to here so you can test it if you want to and we'll see what happens.
I'm also going to put up a debug add-on that will run a check on the autoblog feed listings to make sure they are pointing to the correct places in every location (the plugin stores the target blog in two places now, so we need to make sure they are the same otherwise we'll get issues).
I did find that two feeds among hundreds are processing correctly, the commonality between them is that both users have their website / blog time zone set to UTC-0 in the "General" settings ... everyone else has US based time zones so they are using settings other than UTC-0. Hopefully this can shed a little light on where to look when troubleshooting ...
Tracy, are you saying that you changed your time zones from inside wordpress admin panel "settings"? If so, I am going to give that a whirl. I really need to get these feeds automating. I am burned out on manually turning them.
Just put 3.5.4 up - will put a new sticky on here shortly.
Updates are - new add-on, if you activate the Check Feed Entries add on, and go to the network admin area and view your feeds it will run a quick check for each one to make sure they are set up correctly.
I've also added some options to the config.php file, they are commented just above each entry so have a look, you can now control most aspects from there.
Ones to test on your installs would be setting AUTOBLOG_FORCE_PROCESS_ALL to true first and see if that does anything to get the feeds processing again, and then test the AUTOBLOG_PROCESS_EVERY_PAGE_LOAD one to get rid of a chunk of the timestamp checking.
It processes the feed and says feed processed but no posts are made.
You can copy and paste the link into your browser and see that it is a valid rss feed.
I understand what you might think about the link but it is for testing purposes only. I will however be asking for permission to use this to pull info from some news sites so really would like this to work.
Ideas?
P.S It can be done as wp-robot pulls the content fine and before you say why not just use that.. it is too bulky and munches resources ;)
We are still seeing all feeds broken unless the user has their time zone set to UTC-0. We are also still unable to process all feeds manually by checking them all using the select all check box and then using the process button, we have to literally process each feed one by one by one.
Barry: If you can explain how to use the feed checks, I will take a look. When I turn it on for a single blog and then go to the Network Admin section, nothing happens. What blog should this be turned on for? What should we be seeing?
10-4. when I turn it on for a single blog and go to the network admin section, nothing there...nothing happens. I am not seeing anything different from previous versions. nothing there to configure in other words...
I've also added some options to the config.php file, they are commented just above each entry so have a look, you can now control most aspects from there.
Ones to test on your installs would be setting AUTOBLOG_FORCE_PROCESS_ALL to true first and see if that does anything to get the feeds processing again, and then test the AUTOBLOG_PROCESS_EVERY_PAGE_LOAD one to get rid of a chunk of the timestamp checking.
@trace - If you activate the add-on on one of the sites - if you can then your main site (which is how I've been testing it), then go to the network admin area and list your feeds you should see an extra column:
the feedcheck column is not there. I have activated the feedcheck option but the feedcheck column is not displaying in either the single blog list or in the list in the network admin section.
I will dig into the config.php file and try the commenting that you have suggested.
The last thing I see in the rows is "next check". I will see if i can get you a screenshot.
what i am saying is...if i go into "edit feeds" on a single site...the feedcheck column is not displaying even though I have activated that option. and if I go to the feedlist on the network admin side of things - it's not there either.
just activated the feedcheck add- on on the main site (multi-site install) - the extra column now shows up in the network admin list -the extra column "feed check" is now there - it displays. Seems that you have to activate the add on from the main site for this to work. Now that the extra column is displaying.. I am seeing this message" Problem" in red font - for every feed in the list. So how do I check out what the "problem" is?
@msaizan - that means there is a conflict between the blog_id's stored in the table. Can you try the following and see if it fixes things on one feed.
1. Click Edit on the feed
2. Check that the "Add posts to" target is correct.
3. Click Update Feed.
This should set the feed status to Ok and fingers-crossed get things moving again, or at least be one of the steps towards getting things moving again.
ok - i went through steps 1,2 & 3 and the test feed is showing as "ok" now. I reset the time zone for that target back to the correct timezone - Chicago (CDT) because the feed has been processing when set to UTC-0. I will monitor to see if the feed starts auto processing correctly in the CDT timezone and i will post back here.
// In a multisite install will attempt to process feeds for all sites rather than just local ones
if(!defined('AUTOBLOG_FORCE_PROCESS_ALL')) define( 'AUTOBLOG_FORCE_PROCESS_ALL', true);
// Will check for feeds to process on every page load rather than using the limit defined above
if(!defined('AUTOBLOG_PROCESS_EVERY_PAGE_LOAD')) define( 'AUTOBLOG_PROCESS_EVERY_PAGE_LOAD', true);
?>
No, just the AUTOBLOG_FORCE_PROCESS_ALL for now - if that gets things going then good, if not then set the other one to true as well and see if that helps, but one at a time for now so we can see which one solved the problem.
Ok, realized you have to turn feed checks on in the MAIN blog / site for it to work. All feedcheck columns are green.
Feeds process when AUTOBLOG_FORCE_PROCESS_ALL is set to true. Can you clarify what this is doing? Not sure what a local vs non-local site is.
( // In a multisite install will attempt to process feeds for all sites rather than just local ones )
Also, not sure if this is relevant, all sites on our install using Auto Blog are pulling the same feed, which is an unmapped domain on the same install at blogwithfeed.domainname.com/feed/ .... not sure if this is relevant or not since it is not pulling a feed from an outside blog like say, cnn.com ....
I am going to try one more time with ONLY ' AUTOBLOG_FORCE_PROCESS_ALL' set to true. I think the test feed just hasn't had any new content - i got busy this afternoon though and couldn't stay on top of the logs. so i will watch the logs really carefully. will check back here.
We're seeing some weird behavior. We post one blog post in our source blog per day, which all of our clients have set up as a feed to import using autoblog. All clients are also set to import the feed using the "original post date", not the current date in the "set the date for new posts" section and are using UTC-7 in the general settings section of their site.
I noticed that yesterday our daily blog post was processed by all blogs and imported, but the date was wrong, it was 8/12, not 8/11. It turns out this occurred because I posted it at 18:15 on 8/11, and all the importing sites imported it and but added 7 hours to the time of the post making the import time 01:15 on 8/12, even though all were on identical time zones.
For example: When I look at the post for today that we published, the source blog where the original post was maded (UTC-7 time zone) shows a post time of 11:18 and blog importing the feed that ( UTC-7) shows the time stamp of 18:18, exactly 7 hours later despite being on the same time zone ...
i have duplicate content coming through and no tags in one of the test feeds - i have added tags in the form field for adding tags and i have ticked the box to "add any additonal tags" - alas... no tags.
At the moment I can't duplicate it, I've had it running on my test site since 3.5.4 was released with a number of feeds and am still getting all tags imported and correct timezones now.
Can you email through a couple of the feeds you see the most trouble with and I can put them in and see if I can spot anything then?
Every site on our install is importing the same feed, which is coming from a site on the same install. Are you testing with feeds that are coming from external WP installs or with feeds coming from a site on the same install as the site that is importing it?
I'm currently testing with 3 local sites (two same wp install, 1 same server different install) and 7 externals - some WP sites, twitter, google news and a few others.
Pop it through to contact@incsub.com and mark it for my attention and I'll add it in to this and a new install and see what it does for me.
Just a heads up. I have re-activated all my feeds so I have about 40+ feeds running on a single site in a multi-site install. For the most part I do have tags coming in. It's just one or two feeds that aren't adding tags - so I am thinking it has to do with the feeds themselves and not the plugin. Sometimes I am seeing duplicate content coming through the same feed - but again, I think it could be an issue with the feed itself. The bigger thing right now is I am still seeing the feeds running rather sluggish and a few are stuck. They aren't processing according to the timetable that I have assigned and a few do not process at all. I am going to re-set a cron job to see if can't speed things up. and I am also going to change AUTOBLOG_PROCESS_EVERY_PAGE_LOAD') to true - monitor that with all the feeds activated. I will do this one at a time - set every page load to true first - watch that for a while - and then re-set to false and try adding a cron job...i will report back here.
This is what I've figured out. If source feed blog is set to UTC-3 and it posts a blog at 12:00, other blogs on the install will show an import time of 15:00. Similarly, If source feed blog is set to UTC-7 and it posts a blog at 12:00, other blogs on the install will show an import time of 19:00..... So the source blog's time zone settings is what is determining how far off the importing feeds' times will be.
This means that if the source feed blog that is exporting the feed and the importing blog are both set at UTC-7 and the source blog posts a blog post at 12:00, the importing blog will STILL import the post with a time of 19:00 .....
If I import a feed from an external WP install on same server with UTC-6 at 12:00, the importing blog will show 18:00, so I can replicate the issue with external feeds as well.
Regarding tags, those just stopped working with latest version of autoblog, it worked in previous version.
@msaizan can you check the custom fields on a couple of the duplicate posts and have a look at the one named original_source. Are you seeing the same values in there?
Unfortunately, I stopped upgrading my autoblogs plugin. I never was able to get it to import the feeds with any version higher than 3.5.x and this thread is showing that I'm not the only one.
Not sure where this plugin went wrong, but I rolled back to version 3.4.1 and now my blog feeds are updating properly and on time. The features that are getting added in are nice, but if the core functionality causes headaches, I'll opt for a simpler version.
Barry - oddly enough... I don't have a custom fields/meta area! I am on Pagelines framework - (Platform Pro) and strangely there is no custom fields block in the post editor! I never noticed that before - i guess because i just haven't needed it - anyhoo seems like it disappeared in one of the theme upgrades. verrry odd.
disregard "bleeding issue". isolated the spillover issue.it only happened on 8/10/2011 - that was the day you had Tracy and I activate the feedcheck option. apparently the feed was pointing temporarily to the wrong target. whew.
I'm having problems with autoblog. My feeds are just disappearing.
I set them up, they work as they should but if I edit and save they decide to disappear. I then go through the same process of setting them up again and occasionally they just disappear. Is very frustrating... Can you help?
Welcome to WPMU DEV! This thread's gotten rather long and I'm worried your question is getting over-looked. Can you start up a new thread on this issue?
I'm also gonna go ahead and 'unsticky' this thread. If you are having any trouble just start up a new thread and we'll take a look.
Responses (74)
Member — 3rd August 2011 #
Just a heads up, this plugin and each update are still not showing up WPMU Dev Updates ...
Member — 3rd August 2011 #
We're are still not seeing any feeds process. We manually processed and "next check" time has come and gone and is in the past .... Since we have to manually, we've noticed that in the Network Admin section, the pre-existing issue with trying to check all feeds and process them all at once still exists. The only way to process feeds is to process each one by one ... checking all and clicking the "Process" button has no affect.
We also have a user who has processing and last checked stuck significantly in the future (tomorow, the 4th), so manually processing his feeds does nothing. Using the reset plugin and deleting the feed altogether and re-creating it also have no effect as the processing times again revert to the future ...
Member — 5th August 2011 #
Little help please? Anyone able to get feeds to process?
Developer — 6th August 2011 #
If you've got access to the database, can you check the wp_autoblog table and reset the lastupdated field to 0, and the nextcheck field to a timestamp of a few hours or a day ago:
This will help build a timestamp or tell you what date and time an existing timestamp represents.
http://www.unixtimestamp.com/index.php
Also, version 3.5.3 is out now, but it's only a fix for some non-multisite functions - will get the update notifications sorted, we're still not sure why it's ignore autoblog but we're getting closer.
Member — 6th August 2011 #
Every feed has it's own value for lastupdated, it sounds you are asking me to change a singular value though, is this correct? If so, I may not be looking in the right place. Since the feeds only run if we manually process them, all nextcheck times are in the past, they only get updated when we manually process. We are on 3.5.3.
The same issue where feeds do not process occurs for us on other multi-site installs as well.
Lifetime Member — 6th August 2011 #
Looks good
Member — 8th August 2011 #
i have updated to the latest version and I am still having to manually process my feeds as well.
Member — 8th August 2011 #
Help please?
Developer — 8th August 2011 #
There are only two places that determine whether a feed should be processed or not - the nextcheck field in the autoblog table and the autoblog timestamp that can be reset with the reset autoblog add-on.
The only thing I can think of is to remove those checks from your installs and see if the feeds process then, that way we can determine which part is causing the main problem.
I'll put together a replacement autoblogprocess file and upload it to here so you can test it if you want to and we'll see what happens.
I'm also going to put up a debug add-on that will run a check on the autoblog feed listings to make sure they are pointing to the correct places in every location (the plugin stores the target blog in two places now, so we need to make sure they are the same otherwise we'll get issues).
Member — 8th August 2011 #
ditto on the help please.
Developer — 8th August 2011 #
ditto on the response :)
Member — 8th August 2011 #
trackin ya Barry. Our posts crossed!
Member — 8th August 2011 #
I did find that two feeds among hundreds are processing correctly, the commonality between them is that both users have their website / blog time zone set to UTC-0 in the "General" settings ... everyone else has US based time zones so they are using settings other than UTC-0. Hopefully this can shed a little light on where to look when troubleshooting ...
Member — 8th August 2011 #
I can also confirm that after setting feeds that are not working to UTC-0, they begin processing successfully ...
Member — 8th August 2011 #
Tracy, are you saying that you changed your time zones from inside wordpress admin panel "settings"? If so, I am going to give that a whirl. I really need to get these feeds automating. I am burned out on manually turning them.
Member — 8th August 2011 #
Yes, dashboard > general settings.
Member — 8th August 2011 #
ok. i am going to take it for a spin. i'll keep you posted.
Developer — 8th August 2011 #
I had a thought last night and I have a sneaky suspicion that I know what's happening.
I'm going to make some changes and add a couple of config options today and get an update up for testing.
Member — 8th August 2011 #
Yeppers. Works for me too. When I change my settings to UTC + 0 - the feeds process correctly.
Developer — 9th August 2011 #
Just put 3.5.4 up - will put a new sticky on here shortly.
Updates are - new add-on, if you activate the Check Feed Entries add on, and go to the network admin area and view your feeds it will run a quick check for each one to make sure they are set up correctly.
I've also added some options to the config.php file, they are commented just above each entry so have a look, you can now control most aspects from there.
Ones to test on your installs would be setting AUTOBLOG_FORCE_PROCESS_ALL to true first and see if that does anything to get the feeds processing again, and then test the AUTOBLOG_PROCESS_EVERY_PAGE_LOAD one to get rid of a chunk of the timestamp checking.
Member — 10th August 2011 #
When trying to use this feed:
http://web-designers-norwich.co.uk/makefulltextfeed.php?url=www.techwatch.co.uk%2Fnews%2Finternet%2Ffeed%2F&what=auto&max=10&links=remove&exc=&submit=Create+Feed/
It processes the feed and says feed processed but no posts are made.
You can copy and paste the link into your browser and see that it is a valid rss feed.
I understand what you might think about the link but it is for testing purposes only. I will however be asking for permission to use this to pull info from some news sites so really would like this to work.
Ideas?
P.S It can be done as wp-robot pulls the content fine and before you say why not just use that.. it is too bulky and munches resources ;)
Cheers guys.
Member — 10th August 2011 #
Short note: Still not showing up in the WPMU Update notifications for me. Just happened to stumble onto this thread. Still on 3.5.1.
I also had all those auto process problems so I'll install and see if that fixes the auto processing.
Member — 10th August 2011 #
We are still seeing all feeds broken unless the user has their time zone set to UTC-0. We are also still unable to process all feeds manually by checking them all using the select all check box and then using the process button, we have to literally process each feed one by one by one.
Developer — 10th August 2011 #
@Trace - with 3.5.4? What details did you get from the feed checks add-on, did any of the config options work for you?
@TerryG - update notifications is fixed from 3.5.4 onwards
Member — 10th August 2011 #
ditto. all feeds still broken unless time zone is set to UTC-0 and can only manually process feeds one by one...
Developer — 10th August 2011 #
@Danny - can you enable debugging and see if it reports any errors? Can you show the details of your autoblog entry for that feed?
Developer — 10th August 2011 #
@maizan - ditto response.
Member — 10th August 2011 #
Yes, using 3.5.4.
Member — 10th August 2011 #
using 3.5.4 as well
Developer — 10th August 2011 #
@Trace - and?
Developer — 10th August 2011 #
@msaizan - ditto on response
Developer — 10th August 2011 #
Also can you give me as much detail about your setups as possible, such as method of activation (main site / single site/ network) etc...
Member — 10th August 2011 #
running multisite- the plugin is network activated.
Member — 10th August 2011 #
Barry: If you can explain how to use the feed checks, I will take a look. When I turn it on for a single blog and then go to the Network Admin section, nothing happens. What blog should this be turned on for? What should we be seeing?
Member — 10th August 2011 #
10-4. when I turn it on for a single blog and go to the network admin section, nothing there...nothing happens. I am not seeing anything different from previous versions. nothing there to configure in other words...
Developer — 10th August 2011 #
@msaizan -
@trace - If you activate the add-on on one of the sites - if you can then your main site (which is how I've been testing it), then go to the network admin area and list your feeds you should see an extra column:
Member — 10th August 2011 #
the feedcheck column is not there. I have activated the feedcheck option but the feedcheck column is not displaying in either the single blog list or in the list in the network admin section.
I will dig into the config.php file and try the commenting that you have suggested.
The last thing I see in the rows is "next check". I will see if i can get you a screenshot.
Member — 10th August 2011 #
what i am saying is...if i go into "edit feeds" on a single site...the feedcheck column is not displaying even though I have activated that option. and if I go to the feedlist on the network admin side of things - it's not there either.
Member — 10th August 2011 #
feedcheck add on is activated - but no extra columns.
Member — 10th August 2011 #
just activated the feedcheck add- on on the main site (multi-site install) - the extra column now shows up in the network admin list -the extra column "feed check" is now there - it displays. Seems that you have to activate the add on from the main site for this to work. Now that the extra column is displaying.. I am seeing this message" Problem" in red font - for every feed in the list. So how do I check out what the "problem" is?
Member — 10th August 2011 #
http://www.uploadscreenshot.com/image/419585/4278868
Developer — 10th August 2011 #
@msaizan - that means there is a conflict between the blog_id's stored in the table. Can you try the following and see if it fixes things on one feed.
1. Click Edit on the feed
2. Check that the "Add posts to" target is correct.
3. Click Update Feed.
This should set the feed status to Ok and fingers-crossed get things moving again, or at least be one of the steps towards getting things moving again.
Member — 10th August 2011 #
ok - i went through steps 1,2 & 3 and the test feed is showing as "ok" now. I reset the time zone for that target back to the correct timezone - Chicago (CDT) because the feed has been processing when set to UTC-0. I will monitor to see if the feed starts auto processing correctly in the CDT timezone and i will post back here.
Developer — 10th August 2011 #
@msaizan - set AUTOBLOG_FORCE_PROCESS_ALL in the config file to true as well, as I believe that this also fixes part of the problem.
Member — 10th August 2011 #
set both to TRUE - is this correct?
CODE BELOW THIS LINE:
// In a multisite install will attempt to process feeds for all sites rather than just local ones
if(!defined('AUTOBLOG_FORCE_PROCESS_ALL')) define( 'AUTOBLOG_FORCE_PROCESS_ALL', true);
// Will check for feeds to process on every page load rather than using the limit defined above
if(!defined('AUTOBLOG_PROCESS_EVERY_PAGE_LOAD')) define( 'AUTOBLOG_PROCESS_EVERY_PAGE_LOAD', true);
?>
Developer — 10th August 2011 #
No, just the AUTOBLOG_FORCE_PROCESS_ALL for now - if that gets things going then good, if not then set the other one to true as well and see if that helps, but one at a time for now so we can see which one solved the problem.
Member — 10th August 2011 #
ok. done. will monitor and check back in.
Member — 10th August 2011 #
Nope. Test feed won't process at timezone Chicago plus 'AUTOBLOG_FORCE_PROCESS_ALL', true);
Have set 'AUTOBLOG_PROCESS_EVERY_PAGE_LOAD', to TRUE
Member — 10th August 2011 #
Ok, realized you have to turn feed checks on in the MAIN blog / site for it to work. All feedcheck columns are green.
Feeds process when AUTOBLOG_FORCE_PROCESS_ALL is set to true. Can you clarify what this is doing? Not sure what a local vs non-local site is.
( // In a multisite install will attempt to process feeds for all sites rather than just local ones )
Also, not sure if this is relevant, all sites on our install using Auto Blog are pulling the same feed, which is an unmapped domain on the same install at blogwithfeed.domainname.com/feed/ .... not sure if this is relevant or not since it is not pulling a feed from an outside blog like say, cnn.com ....
Member — 10th August 2011 #
the test feed seems to be processing with the target's timezone set at Chicago and with both 'force process all' and 'every page load' set to true.
Member — 10th August 2011 #
I am going to try one more time with ONLY ' AUTOBLOG_FORCE_PROCESS_ALL' set to true. I think the test feed just hasn't had any new content - i got busy this afternoon though and couldn't stay on top of the logs. so i will watch the logs really carefully. will check back here.
Member — 11th August 2011 #
Test Feed is processing in correct time zone with ONLY '' AUTOBLOG_FORCE_PROCESS_ALL' set to true! Woot! :)
Member — 12th August 2011 #
We're seeing some weird behavior. We post one blog post in our source blog per day, which all of our clients have set up as a feed to import using autoblog. All clients are also set to import the feed using the "original post date", not the current date in the "set the date for new posts" section and are using UTC-7 in the general settings section of their site.
I noticed that yesterday our daily blog post was processed by all blogs and imported, but the date was wrong, it was 8/12, not 8/11. It turns out this occurred because I posted it at 18:15 on 8/11, and all the importing sites imported it and but added 7 hours to the time of the post making the import time 01:15 on 8/12, even though all were on identical time zones.
For example: When I look at the post for today that we published, the source blog where the original post was maded (UTC-7 time zone) shows a post time of 11:18 and blog importing the feed that ( UTC-7) shows the time stamp of 18:18, exactly 7 hours later despite being on the same time zone ...
Any feedback appreciated!
Member — 13th August 2011 #
i have duplicate content coming through and no tags in one of the test feeds - i have added tags in the form field for adding tags and i have ticked the box to "add any additonal tags" - alas... no tags.
Member — 14th August 2011 #
Our tags have broken with latest version as well and are not coming through to blogs importing using auto blog ... just a heads up.
Member — 17th August 2011 #
Help?
Developer — 17th August 2011 #
At the moment I can't duplicate it, I've had it running on my test site since 3.5.4 was released with a number of feeds and am still getting all tags imported and correct timezones now.
Can you email through a couple of the feeds you see the most trouble with and I can put them in and see if I can spot anything then?
Member — 17th August 2011 #
Every site on our install is importing the same feed, which is coming from a site on the same install. Are you testing with feeds that are coming from external WP installs or with feeds coming from a site on the same install as the site that is importing it?
What email can I email the feed to?
Developer — 17th August 2011 #
I'm currently testing with 3 local sites (two same wp install, 1 same server different install) and 7 externals - some WP sites, twitter, google news and a few others.
Pop it through to contact@incsub.com and mark it for my attention and I'll add it in to this and a new install and see what it does for me.
Member — 17th August 2011 #
Just a heads up. I have re-activated all my feeds so I have about 40+ feeds running on a single site in a multi-site install. For the most part I do have tags coming in. It's just one or two feeds that aren't adding tags - so I am thinking it has to do with the feeds themselves and not the plugin. Sometimes I am seeing duplicate content coming through the same feed - but again, I think it could be an issue with the feed itself. The bigger thing right now is I am still seeing the feeds running rather sluggish and a few are stuck. They aren't processing according to the timetable that I have assigned and a few do not process at all. I am going to re-set a cron job to see if can't speed things up. and I am also going to change AUTOBLOG_PROCESS_EVERY_PAGE_LOAD') to true - monitor that with all the feeds activated. I will do this one at a time - set every page load to true first - watch that for a while - and then re-set to false and try adding a cron job...i will report back here.
Member — 17th August 2011 #
This is what I've figured out. If source feed blog is set to UTC-3 and it posts a blog at 12:00, other blogs on the install will show an import time of 15:00. Similarly, If source feed blog is set to UTC-7 and it posts a blog at 12:00, other blogs on the install will show an import time of 19:00..... So the source blog's time zone settings is what is determining how far off the importing feeds' times will be.
This means that if the source feed blog that is exporting the feed and the importing blog are both set at UTC-7 and the source blog posts a blog post at 12:00, the importing blog will STILL import the post with a time of 19:00 .....
If I import a feed from an external WP install on same server with UTC-6 at 12:00, the importing blog will show 18:00, so I can replicate the issue with external feeds as well.
Regarding tags, those just stopped working with latest version of autoblog, it worked in previous version.
Member — 17th August 2011 #
i think my issue with the sluggish feeds could be related to what your reporting here Trace.
Member — 17th August 2011 #
Barry if you have better ideas about how to isolate this problem...do pass it along. direct me...
Member — 18th August 2011 #
feeds are moving aggressively when 'EVERY PAGE LOAD' is also set to TRUE.
but....i have got major duplications...like sometimes seven or more duplications of the same post content per turn.
what would be causing the feed content to duplicate? and is there anything I can do about that on my end?
Developer — 18th August 2011 #
@msaizan can you check the custom fields on a couple of the duplicate posts and have a look at the one named original_source. Are you seeing the same values in there?
Member — 18th August 2011 #
ok. I have deleted out all the duplicated posts so I will wait til it happens again. will check back in here in a bit.
Member — 18th August 2011 #
Barry are you referring to custom fields INSIDE the posts?
Member — 18th August 2011 #
Unfortunately, I stopped upgrading my autoblogs plugin. I never was able to get it to import the feeds with any version higher than 3.5.x and this thread is showing that I'm not the only one.
Not sure where this plugin went wrong, but I rolled back to version 3.4.1 and now my blog feeds are updating properly and on time. The features that are getting added in are nice, but if the core functionality causes headaches, I'll opt for a simpler version.
Developer — 18th August 2011 #
Strangely the core processing functionality has never changed since version 1.
@msaizan - if you click on the edit for the post then they will be listed under the Custom fields / meta area.
Member — 19th August 2011 #
I have a very weird issue cropping up now. I am on a mult-site install. The feed posts from one site - http://neworleansnews.gulfcoastrising.com are bleeding into another site http://2011hurricaneseason.gulfcoastrising.com.
Member — 19th August 2011 #
Barry - oddly enough... I don't have a custom fields/meta area! I am on Pagelines framework - (Platform Pro) and strangely there is no custom fields block in the post editor! I never noticed that before - i guess because i just haven't needed it - anyhoo seems like it disappeared in one of the theme upgrades. verrry odd.
Member — 19th August 2011 #
disregard "bleeding issue". isolated the spillover issue.it only happened on 8/10/2011 - that was the day you had Tracy and I activate the feedcheck option. apparently the feed was pointing temporarily to the wrong target. whew.
Member — 19th August 2011 #
I'm having problems with autoblog. My feeds are just disappearing.
I set them up, they work as they should but if I edit and save they decide to disappear. I then go through the same process of setting them up again and occasionally they just disappear. Is very frustrating... Can you help?
Sales & Support Lead — 22nd August 2011 #
Hiya @Me,
Welcome to WPMU DEV! This thread's gotten rather long and I'm worried your question is getting over-looked. Can you start up a new thread on this issue?
I'm also gonna go ahead and 'unsticky' this thread. If you are having any trouble just start up a new thread and we'll take a look.
Thanks everyone!
Become a member