Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Slashdot Fry Site On

posted by Krow on 01:19 PM August 3rd, 2001   Printer-friendly   Email story
Take a look at banjo if you want to see a site runnning fry (which is the 2.2 release of Slash). It should scale a bit farther then bender (even though bender does pretty damn well). It has a bunch of new fetures. Check out:

~username/ for user info

~username/journals/ for a user's journal

~username/discussions/ for a user's discussions

/ for the new discussion system (users can now create their own discussions)
There are a lot of new features to play around with now, including a new message system (so you can know when people respond to your comments/or when journal entries are added).
Have fun with it.
BTW there is always cvs for those of you who want to play with the code now. Expect a tarball release sometime in a couple of weeks.

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • by Anonymous Coward
    slashdotted already. thank rob for it.
  • I was feeling good and decided to CVS up to Fry (I was using Bender), and try it out.

    I updated all my Perl Libaries via CPAN, and then went and did a make && make install on fry.

    Things ain't working. I get this message:

    BEGIN failed--compilation aborted at /usr/local/slash/sbin/slashd line 24.

    Can't locate Schedule/ in @INC (@INC contains: /usr/local/lib/perl5/5.6.1/i386-freebsd /usr/local/lib/perl5/5.6.1
      /usr/local/lib/perl5/site_perl/5.6.1/i386-freebsd /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl/5.6.0/i386-freebsd /usr/local/lib/perl5/site_perl/5.6.0 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 /usr/local/lib/perl5/site_perl .) at /usr/local/slash/sbin/slashd line 24.
    BEGIN failed--compilation aborted at /usr/local/slash/sbin/slashd line 24.

    Any ideas? I didn't see anything in the INSTALL that was different, nor did I see any errors while doing make/make install.


    It's either on the beat or off the beat, it's that easy.
  • by Anonymous Coward
    I want to install Slashcode for the first time .. should I use the new version or the old? Will bug fixes in the new version be easy to install or is it safer (and easier) to just use the old version?
  • by Anonymous Coward
    This mailing feature is pretty cool, but I'd like to receive replies to my comments via ICQ. Would that be possible somehow to implement?
  • by Anonymous Coward
    ICQ already has this funtionality built in. Just send e-mail to <your_uin> (hopefully I got the right domain, if not you can find out how to do it at and it will appear in ICQ as a message.
  • Yes! First chance either I or pudge get I a module to interface with jabber will be added. What that happens messages to just about everything (but AOL) will be sent.

    You can't grep a dead tree.
  • by Anonymous Coward
    the rendering is still dog slow, the interface is horribly outdated (and i thought it looked ugly in 1998) and unintuitive. you guys need to get some usability experts to get rework the whole layout. i like the things that ubb does. maybe you guys could do something like that.
  • by Anonymous Coward
    UBB is a horrid, horrid program when it comes to UI. Further (and perhaps more relevantly), the interface is something that can be altered drastically by you. You'd be a fool to use the interface as is. (Not that it's particularly hideous or unintuitive. It's simply uninteresting and, more important, in use.)
  • If I had known the coding of Slash was going to be this half ass, I would have never used it for a production site. I started 2 years ago with Slash 1.0, and upgraded to 2.0 three weeks ago. It seems they dumped functionality for new features. Ohh great, a journaling system.. but about basic things that used to work, like header topics ($topics), page numbering in comments, archiving (just to name a few). Okay, well enough ranting. Just upsetting that I have to spend hours rewriting code just so my site can work again. I looked at fry, and page numbering still doesnt work!
  • by Anonymous Coward
    Yeah, you do have a valid point, but the software isn't ready yet for primetime. Fry looks like it will have more things fixed/working than Bender did.....
  • I do have a fix for the page numbering problem in Slash 2.0, quite simple really:

    Template ID: 41, linkCommentPages, misc, default

    startat => startat
    startat => start

    I think this is all I changed, if it doesnt work, let me know.
  • by Anonymous Coward

    btw it's

    but some direct connection would be better IMO

  • Please don't feed the trolls...
  • Go into your CPAN tool and install Schedule::Cron.
    The Bundle::Slash is not updated for fry yet.

    You can't grep a dead tree.
  • Ahhh.....


    What else is required to get Fry running from Bender?


    It's either on the beat or off the beat, it's that easy.
  • Word wrap isn't working on the index page if you choose light mode. Article pages seem fine.