Version: 1.00, by nevetS
Developer Last Online: Oct 2008
Version: 3.5.0 Beta 3
Rating:
Released: 07-06-2005
Last Update: 07-06-2005
Installs: 34
Uses Plugins Template Edits
No support by the author.
I just posted this over at vbWebmaster Forums. I'm all excited because this is my first plugin and I know pretty much nothing about vbulletin. I got the idea from Shawn's forum at Digital Point
I just put this together for 3.5 using carp.
Step 1) Add a custom profile field for the RSS link. In my setup it was field5.
Step 2) Edit your postbit template as follows:
Step 3) Create a new plugin. I named mine: Carp Configuration. Attach it to the "global_start" hook location.
Here is the code:
PHP Code:
require_once '/path/to/carp/carp.php';
CarpConf('cacheinterval',120);
/** You may want to set a cachepath specifically for your forum **/
CarpConf('cachepath','/where/you/want/your/cache/files/');
CarpConf('cacherelative',0);
/** You can omit the above two lines without a problem **/
CarpConf('cborder','');
CarpConf('poweredby','');
CarpConf('maxitems',1);
CarpConf('iorder','link');
Step 4) One more plugin. This one I called: Get Users Blog Entry
Attach this to hook location: postbit_display_start
That's it... away you go. If you don't have carp, you can check it out at: http://www.geckotribe.com/rss/carp/
I'm not sure if this will work with the free version, as I have the paid version.
I'm thinking about using grouper to set it up so I can parse atom files, but I don't know how important that will be.
Note: carp allows you to enter local paths and http paths for rss feeds. I've tried entering both in my user profile field successfully. You may want to disallow users from entering a local path just to be on the safe side. I don't have any code for that right now, but I'm sure there are some examples for field validation out there.
Carp has an option to store it's output in a variable ($carpoutput), but it didn't seem to work for me. That's why I used the ob_start and end_clean functions. If anybody has any feedback as to how this may be improved, I'm willing to listen.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Could you please be so kind to copy your instructions into a textfile and upload it to the modification. This is usefull so members can keep the instruction of installed modifications for later use when upgrading for example.
Could you please be so kind to copy your instructions into a textfile and upload it to the modification. This is usefull so members can keep the instruction of installed modifications for later use when upgrading for example.
The attached zip file contains the instructions per request.
No problem. I'm very impressed at how easy it is to build plugins in 3.5. It took me several hours to put this together, but I'm very new to vbulletin and I didn't know the in's and out's of anything.
In the future for this script, I'd like to add an installer that creates everything for you, but I don't quite know the best way for doing this yet and I'm going to have to add a function to search for the carp files and accepts some user input for location. I'm also not sure if I should just insert the code into the template or if I should just have the users do that themselves.
Before I go that far, I'm going to wait for any feedback about better ways to go about this. If there's a more performance friendly method, I should use it.
Carp is an caching RSS script. Which basically means it will look for a locally cached version fo the rss feed to display first and if one does not exist it will go out and grab the latest version online. The configuration above expires caches every two hours, so if you update your blog it can be up to two hours before the latest blog entry appears. If 10 different people have blogs configured and post in a thread it can mean that 10 different http queries need to go out to display the thread if it has not been viewed in a long time.
Another way to go about this is to set up a cron job to regularly update the cache files, but that could mean that every time it runs 150 http queries go out if you have 150 members with blog entries configured, and it very well could be the case that 50 of those members are not active posters.
These are all reasons to post the plugin here, though. As I get feedback, I can improve the script and everyone can benefit.
No problem. I'm very impressed at how easy it is to build plugins in 3.5. It took me several hours to put this together, but I'm very new to vbulletin and I didn't know the in's and out's of anything.
In the future for this script, I'd like to add an installer that creates everything for you, but I don't quite know the best way for doing this yet and I'm going to have to add a function to search for the carp files and accepts some user input for location. I'm also not sure if I should just insert the code into the template or if I should just have the users do that themselves.
Before I go that far, I'm going to wait for any feedback about better ways to go about this. If there's a more performance friendly method, I should use it.
Carp is an caching RSS script. Which basically means it will look for a locally cached version fo the rss feed to display first and if one does not exist it will go out and grab the latest version online. The configuration above expires caches every two hours, so if you update your blog it can be up to two hours before the latest blog entry appears. If 10 different people have blogs configured and post in a thread it can mean that 10 different http queries need to go out to display the thread if it has not been viewed in a long time.
Another way to go about this is to set up a cron job to regularly update the cache files, but that could mean that every time it runs 150 http queries go out if you have 150 members with blog entries configured, and it very well could be the case that 50 of those members are not active posters.
These are all reasons to post the plugin here, though. As I get feedback, I can improve the script and everyone can benefit.
Yes I would like to see some sort of change so that (If 10 different people have blogs configured and post in a thread it can mean that 10 different http queries need to go out to display the thread if it has not been viewed in a long time.) doesn't happen.