Now Showing...

Hack, Fiddle, Hack, Scream

Well, I have spent the last two days hacking and fiddling with something called bbPress. What is it? Well it’s a forum add-on for Wordpress that can either be a stand-alone forum or can be integrated into WordPress. Having got my good friend JT to integrate and set it up and get the errors to stop it fell to me to stylise and customise it.

So what do I think? I’m torn. It is quite obviously not had the same amount of development go into it as WordPress. It is quite unpolished and there are several really frustrating things about it when you are trying to adjust things. There are too many things that are not controlled by the Theme but are held in other includes and function files.

On the other hand it does integrate with WordPress. It does work well once you get it going. It’s a nice, clean (if a little quirky in terms of the HTML it uses) forum. It lacks lots of the advanced features of packages like vBulletin but it is free and for simple discussion areas it’s fine.

If you want a simple forum it’s worth a look but don’t expect it to be all smooth sailing!

14 Responses to “Hack, Fiddle, Hack, Scream”

  1. Joe Says:

    Have you tried integrating ForumXP-MAC using Pearl-scripted java?
    If you ftp the files in MySQL you can reduce the render time to only one teraflop.
    Hope this helps.

  2. Owen Says:

    Crap - I haven’t been using the Pearl-scripted java. Instead I have been using C#-jabba and rerouting it through the WAN pipeline to streamline the XML output. Of course the side effect of that is that the core upstroke/downstroke processing ration has ben compromised due to excessive strain on the server ports.

    Dumkopf.

  3. Joe Says:

    Rookie mistake. Happens to us all. Last week I ran a C++++ script through my Linux sever link-up to access my IP Ports and instead of coding in 4-Tran, used html to process the codec. This, of course halved the download speed leading to increased shockwave flash inceptions. Next time, I’ll simply run it through basic using my commodore 16. Obvious really.

  4. Owen Says:

    Hmm, you used HTML to process the codec? What do you think about using the standards compliant xHTML? I read a white paper that highlighted the inherant technical dangers of using older technology to compensate for buffer overrun and how bandwidth limitations can be overcome just by using a simple system shunt to clear the cache and free up all redundant memory addresses (while simultaneously upping the sample rate from 56mbps to 128mbps). I am hindered more by the limitations of my hardware though. Shame.

  5. Joe Says:

    Ahh yes. quite quite. A common misconception. The current thinking is that the jahoobliay umbongo is much better placd to refuddle the kuquat rendang. Indeed, I red a blue paper that stateted five-fold more dodiddly baheemos were acheived using much less than five gib gib gaboor mahoony squat-squats.

    Have you found this to be the case?

  6. Owen Says:

    Have you tried switching it off then on again?

  7. Joe Says:

    I’d have to plug it in first.

  8. Nai T Says:

    will you please start talking in ‘girl’ now?!?!? Geeks! xx

  9. Owen Says:

    No.

  10. Joe Says:

    Ooh. Look at the pretty shoes and flowers. Girl enough?
    How about: “What do you mean, you just sat there and played computer games? Why isn’t the washing up done?”.

  11. Nai T Says:

    I liked the first comment best!! xxx

  12. Pete Says:

    Problem with ‘others’ code is that often they don’t know the first thing about CSS etc. The amount of times I’ve reskinned Joomla components and removed inline styles, is equivalent to the length of hair on Olly’s head.

    Incidentally, does it work on a Wii?

  13. Olly [he of the ludicrous hair] Says:

    Bloody hell Pete, that’s loads!

  14. Simon [also of stupid hair] Says:

    Get a hair cut Olly you tree hugging hippy :)

    PS SSX Blur is good fun Mr Clay, just got it

Leave a Random Thought

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>