Keep Up-to-Date with BOPIT

12th Aug 2007 stk

Plug-in and Skin Developers

Right about now, you're probably wishing that you could add this type of functionality to your skins and plug-ins. Well, you can! We built BOPIT with developers in mind.

The first thing you need to do is to request a login for BOPIT, just grab one of us on the forums or requet one in the comments to this post. This login will give you access to our special blogs which control the BOPIT files, allowing you to easily maintain the version information for your plugins and skins.

Creating / Maintaining version information

The post screen for both the (b) Plugins and (b) Skins is exactly the same, so I'll just talk you through one of them, for skins you need to do a tad more work which I'll explain at the end. The first thing you're going to notice is that the post screen is pretty different from the normal post screen, this is just to make it easier for you to enter the required information.

List of fields and what they're for ( see screenshot ) :

  1. Name : This is the name of your skin / widget / plugin and is shown in the users BOPIT list (a), this can be any name you care to choose
  2. Version : This is the version of the skin / plugin / widget that the zipfile contains and is shown in the users BOPIT list (b), this field is kinda important ;)
  3. Code : This is your plugin/widget $code and is needed to enable BOPIT to connect version information to the correct plugin, for skins you need to make one up ( see below ).
  4. Notes : This is a swift one liner ( text only ) to explain why the version information was added to BOPIT, this is shown in the users BOPIT list (c) IF they have your skin / plugin / widget installed and it's out of date
  5. Description : This is a brief description of your skin / plugin / widget which is shown on the version information post ( screenshot 3 ). Please note : it must be valid xhtml strict, otherwise we'll be a tad miffed when you break our skin. Also note that we don't have auto-p installed so you have to add those tags yourself.
  6. Homepage : This is the link to your skin / plugin /widget homepage, it's shown in the users BOPIT list (d) and allows users to read up on your skin / plugin / widget before they decide to try it
  7. Support page : This is a link to your skin / plugin / widget support page, it can be the same page as the homepage or the forum thread if you provide support there. Again this is shown on the users BOPIT list (e) and allows them to easily find support.
  8. Download link : This should be a direct link to the zipfile, it's shown in the users BOPIT list (f) and allows the user to easily download the zip
  9. Categories : These are the b2evolution versions that your skin / plugin / widget supports for the zip file that you have linked to.

Different zips for different evo versions

If you have different versions of a skin / plugin / widget for different versions of b2evolution, like the weather plugin which has a 1.10.x version and a 2.x version, then you need to make two posts, one for each zip file, as long as your skin / plugin / widget code remains constant then BOPIT will link them all together when displaying available versions ( example : download the weather plugin ) to the user. You can also use this feature on your skin / plugin / widgets home/support page by linking to the BOPIT blog with the code as a search param


download the <a href="" title=" see all available versions of the weather plugin ">weather plugin</a>

Updating version information

If and when your skin / plugin / widget version changes, maybe you've added an enhancement, or fixed a bug, or whatever, you just need to edit the relevant bopit post to amend the version number to the new version number, and change the note to reflect the change, and hit save. All the relevant BOPIT files will be automatically updated and the changes will be seen by users immediately in their BOPIT list. Easy as huh?

Enabling your skins

Whilst we can automate the plugins side of things it requires a smidge more work on your part if you wish to add versioning to your skins. Basically you'll need to add an XML file to your skin folder which will contain the relevant BOPIT information. As we haven't got any supported skins yet we haven't decided on the final construct of the file, so if you're a skin designer give us a shout and we'll talk to you about the kind of information / functionality you'd like the file to support


If you have any questions regarding BOPIT and how to use it then just leave a comment and we'll try and answer them as best we can. If you wish to have a BOPIT login then let us know and we'll set you one up ;)

  1. Introduction
  2. Installation
  3. Developers ( revised )


Seems like a lot of crap to go through for such a simple thing, why don't plugin devs just add a $bopit_update_xml_url variable to their plugins, which the bopit plugin looks for, and then uses.
08/13/07 @ 02:25
1) All plugin devs would need to amend their code to suit the plugin - this way they don't
2) The plugin would have to make multiple server calls to check if the plugins are up to date - this way it doesn't
3) You'd only be able to check installed plugins - this way you can see plugins you don't even have installed

08/13/07 @ 07:21
Comment from: EdB
May I suggest a field for "reason"? Like "Error with gijdyboodle fixed by snargulating the rectoplasm" or "cosmetic clean-up, not critical".

Hey your cool greyn lines aren't greyn down here. They're greyn in the corners but an extremely pale shade of grey when they are horizontal or vertical.

Back on track: so if a plugin can work all the way back to 0862 I would make an xml file called "version_0_8.xml" with whatever plugin I had for back then. I would then need to duplicate that plugin in each successive version it works in, or no?

PS your textareaa doesn't have a scroll bar.
01/14/08 @ 00:57
Hi EdB
The eventual goal for bopit is to have an area where plugin/skin developers can maintain their own entries, this would probably be a slightly modified blog where the categories are the various evo versions so you just need to tick all the right boxes. We'd then use the blog posts to create/update the various xml files that allow bopit to work it's magic and we'd be able to use the same blog as an "available plugins / skins " section on this blog.

Once we finish off tarting up this new skin and correcting all the currently dead links then I'll have time to play as I'd like to get it finished off.

Thanks for the heads up at the lack of scrollbar, that's one that I hadn't noticed it's corrected now ;)

01/14/08 @ 10:42
Comment from: EdB
Your contact form failed for an unhandled disp type. I have an xml file for ya at
01/20/08 @ 09:22
Hi EdB,
I didn't even know we had a contact form :P I've added your plugins to BOPIT so they should show in your admin area by the time you read this.

We have a whole new cool system for maintaining the files, at least we have one whilst the plugin isn't going through one of it's random moments of disablement .... gotta track down what makes that happen.

If you login ( your username's edb, god knows what you picked as a password ) and meander over to the "plugins" blog you'll see the BOPIT entries for the plugins, editing the posts edits the files. *IF* you get a normal post screen then it means the BOPIT controller plugin is going through a moment of doubt so you just need to hit the "plugins install" tab and convince it that it should be enabled.

01/20/08 @ 10:27
Comment from: EdB
One thing at a time! Up on the developers page (p3 yah?) the words "give us a shout" are linked to which I took to be a contact form.

I'm also seeing something funny with the YouTube plugin. It told me I had an old version and that I should upgrade even though I was pretty sure I had the latest and greatest. So I upgraded followed the link and grabbed the zip and unzipped it and uploaded it and it's still telling me my copy is old.

Something about it coming from a mac perhaps? I've seen some "funny" stuff happen with zips from macs - usually "all lines appear to be on one line" in a file editor.

That was two things? Now I'll see if god knows what my password was :)
01/20/08 @ 18:47
bugger, I really need to update the developers notes, shit has waaaaay moved on beyond that .... and the contact list is fubar'd :p

I had hassle last time with the youtube versions, I'll work on curing it ..... once I stop the controller plugin from randomly disabling itself ( rapidly turning into a huge pita ).

I spoke to god earlier, he said he was fuck'd if he could remember your password and hopes that your profile email is correct so you can do the whole "I'm a dumbass, send me a forgotten password link" routine ..... or I could just change it to the password of your choice? O:-)

01/20/08 @ 23:02
Comment from: EdB
Yeah I'm logged in here now, but didn't really know what to do. Saw the empty o instead of the solid spot but ... no X to kill it and re-install it, and no "two spots on a stick" to engage and disengage.

BTW after I found your "login or register" link it took me to site, which does a wonderful job of breaking the back button.

Wish I could help you with your plugin problem, but as you know I can barely plugin a toaster without issue :/
01/21/08 @ 01:11
I decided to do it the easy way and run a check on each blog hit, if the plugins disabled it just re-enables it in the database. I still need to work out why it disables though. It's all good fun though huh?

I've changed your group permissions in admin, you should now have the ability to play with the plugins.

I really need to go through all the widgets and correct the placeholder links before your back button sues us for negligence :P

01/21/08 @ 09:16
Comment from: ednong
you need to update the Readme.html in the version 2.3 of your plug in for b2evo V 2.x

And did you take a look to your website in konqueror?
02/23/08 @ 01:33
I don't think I've ever updated that readme :p

Is that a subtle hint that I need to reboot and check in konqueror ? :p

02/24/08 @ 08:17
I'm the creator of the DNS Anti-spam trackback plugin, the wikipedia links plugins, and blogalaxia tags plugins, and would like to enter into this wonderful BOPIT world. Mainly because I want to keep up to date with my own plugins versions (how is that for a forgetful person?), because the idea sounds cool and I just want to give it a try. In Gallery2 the plugin updates are really automatic from the admin area, and this BOPIT doesn't provide quite that functionality, but it is good enough for me anyways. So, how do I get the key to the kingdom?
02/28/08 @ 08:10
Hi Austriaco,
It is actually possible to get BOPIT to automatically upgrade/install plugins directly from admin but it would require one of the following

1) PHP running as the user ( suexec ) : this is ideal
2) Wide open permissions for the plugins folder ( 0777 ) : Never going to happen

As to getting access to the heady world of BOPIT I just created you a user, you should have an email arriving shortly ;)

02/28/08 @ 09:25
Skins Fields:

Theme/Skin Name: MySkin-001
Version Number: (must be X.X.X) example: 12.12.12
Author: ME!
License: CC-BY-SA; GNU FDL; or whatever
Last Updated: 2008-04-01 (YEAR-MM-DD)
Description: blah blah blah

Upgraded by: (optional)
Ported By: (optional)
Original Design by: (optional)


04/03/08 @ 16:43
Hmmm, that's certainly a starting point. I'll have a ponder and see what I can come up with ;)

04/04/08 @ 17:11
Comment from: )(H)(
in my admin>tools>am boopit got
Fatal error: Class 'Plugins_no_DB' not found in /home/inkcdro/public_html/plugins/am_bopit_plugin/_am_bopit.plugin.php on line 114
clicking on tab.
Any reasons?
12/11/08 @ 22:06
Last time that happened it's because somebody download a very old version, make sure you have the latest version ( 2.5 I *believe* )

12/14/08 @ 09:02
Comment from: )(H)(
right. uploaded 2.5. works. tnx
12/16/08 @ 20:58
Comment from: ednong
I just downloaded the newest BOPIT in version 2.6.1. I'm using b2evo in version 2.4.6 with BOPIT in version 2.5

I deinstalled the old version, removed the folder and put the new one BOPIT into the same place. Then I reloaded and tried to install the new version of BOPIT. And get this error:

Parse error: parse error, unexpected '=', expecting ')' in /home/www/webnumber/html/blogs/plugins/am_bopit_plugin/_am_bopit.plugin.php on line 274

I don't know. Tried to downloade again and upload to my webspace. Same thing. Why?
04/11/09 @ 21:33
I'm guessing you're using php4.x, can you see if this version works for you ( ) ?

04/13/09 @ 08:03

This post has 1 feedback awaiting moderation...

Comments are closed for this post.