The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
rss bot
hi, i want the rss bot to check for new update all 24 or 48 hours. The problem is, in the settings dropdown i only can choos 12 hours as maximum. What could I do to change that to 28 hours?
2.) I noticed that there seems to be a problem, if I use 4 rss bot, posting from 4 different sources. Each of the bots is using a own nickname. If they all post, it doesnt work, nothing happens but if I deactiveate 3 of the bots, the one left, is working. Whats wrong there? thank you for any help |
#2
|
|||
|
|||
If you edit file admincp/rssposter.php, around line 363 is the end of the list of choices:
Code:
36000 => construct_phrase($vbphrase['x_hours'], 10), 43200 => construct_phrase($vbphrase['x_hours'], 12), ), $feed['ttl']); If you want, you can add some lines to that, like: Code:
36000 => construct_phrase($vbphrase['x_hours'], 10), 43200 => construct_phrase($vbphrase['x_hours'], 12), 86400 => construct_phrase($vbphrase['x_hours'], 24), 172800 => construct_phrase($vbphrase['x_hours'], 48), ), $feed['ttl']); (The first number is the number of seconds in that many hours). I looked at the rss poster code and it looks like that's the only change you should have to make, but I haven't actually tried it. As for your second issue, I think some feeds contain something that causes an error in the rss poster code and it crashes, so the other feeds don't get processed. I helped someone a few months ago with a similar problem, but I never heard back from him to know if it worked. Maybe later I'll have a chance to dig it up and see what the fix was. |
#3
|
|||
|
|||
Hey kh99 Great thank you so much. I will try that and if you find a Solution for the other, that would be awesome Thank you for your help
|
#4
|
|||
|
|||
Ok it looks like this:
Quote:
Thank you |
#5
|
|||
|
|||
Ok, you would also need to edit file includes/class_dm_rssfeed.php and find this around line 162, and add the lines in red:
Code:
switch ($ttl) { case 518400: // every 144 hours case 345600: // every 96 hours case 432000: // every 120 hours case 259200: // every 72 hours case 172800: // every 48 hours case 86400: // every 24 hours case 43200: // every 12 hours case 36000: // every 10 hours Apparently when the code was written, someone felt it was important to make sure that value could only be set to one of the "official" values. I'll look for that other code to see if the fix helps you. |
#6
|
|||
|
|||
Didn't help, sorry that is really weird and I dont understand why vbulletin gives my only minutes values.
|
#7
|
|||
|
|||
Quote:
As for the other issue, What I told the guy is this: In file includes/cron/rssposter.php, around line 453, I made this change (add the curly brace in red, delete the one in blue on the last line): Code:
} if (!empty($feeds)) { // update lastrun time for feeds $vbulletin->db->query_write(" UPDATE " . TABLE_PREFIX . "rssfeed SET lastrun = " . TIMENOW . " WHERE rssfeedid IN(" . implode(', ', array_keys($feeds)) . ") "); } } I don't remember the reasoning behind it, and I don't know exactly what your problem is, so I don't know if this will fix it. But I think it had something to do with the fact that if a feed has a problem, the original code will just keep trying that feed over and over. This change makes it update the feed check time so that it will cycle through the other feeds instead of getting stuck on one. |
#8
|
|||
|
|||
OK, the (hopefully last) problem is that the field in the database where the time is saved is a "smallint" which only holds up to 65535. So if you really want to do this, you can modify the rssfeed table in the database and change the ttl field to be mediumint (or int if you think you'll ever want a value greater than 90 days or so).
|
#9
|
|||
|
|||
Thanks for the advice , I would add MySQL code:
Quote:
I am now 24 and 48 hours at options. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|