Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Slash 0.9.4 Weekend

posted by CaptTofu on 10:12 AM March 18th, 2000   Printer-friendly   Email story
With the release of Slash 0.9.4 the other day, I'm sure that many of you are working with the code this weekend. I'm wondering how many of you have downloaded the latest release, and what sort trials and tribulations have you experienced? Of those of you who upgraded, how did that work out?
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.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • 1. PERL_SECTIONS is already included if you follow the installation instructions.

    3. It looks like you gave Mail::Sender bad configuration data. Open the file it says has a problem and try to fix it.

    It looks like you simply didn't install the DBD::mysql driver properly. Did you use RPMs or something? Try reinstalling from the source.

  • As to the light versions, it is needed, because if we don't have light versions, the regular versions are used automatically.
  • Just one note for now. I don't have all the answers, but thanks much for all of the feedback, and we will look into it all for the next release. Without further ado ...

    10. This is relatively easy to "fix". Go to dailyStuff and add something like:

        $I{dbh}->do('LOCK TABLES users READ, authors READ, users_comments WRITE');
        my $uids = $I{dbh}->selectall_arrayref('select uid from users,authors where aid=nickname')
            or die $I{dbh}->errstr;
  • More ...

    1. This apparently has never worked. You can see $commentstatus being passed into Slash::printComments(), but it is never used there. It is on our TODO list now, but we won't get to it right now.

    2. Seems related to your cookie problems, mentioned in the other post.

    3. I don't see this behavior. Can you go through an exact series of events, so we can replicate it?

    4. It seems to be working for Slashcode.com, though I will check back tomorrow and see. Perhaps dailyStuff is not running for some reason? It changes daily through that. Check logs/slashd.log for error messages.

    5. That is exceedingly odd. Fixed.

    6. For the unspecified lameness filter, we use Compress::Zlib to check how well some text is compressed. If the text compresses extremely well, then we say it is lame (usually it is someone pasting the same text over and over again, or just typing 'asdasdasdasd', or something). Can you think of any text we could put in there for that error?

    For the all numbers, yeah, that's a funny one. Doesn't matter too much, I guess, but we'll try to come up with a better regex or better error text.

    7. Yes, I've noticed it. Maybe I'll whip up something to fix that soon. I'll just need to design different blocks to replace them (which for light mode shouldn't be too hard :).

    8. Fixed. I found out what the fix is: "All Authors" and "All Topics" needed to be added to the authors and topics tables (with no aid or tid). It should be in the next release.

    9. OK, I added some code to Slash.pm, etc. to facilitate this, along with a variable in slashdotrc.pl (authors_unlimited) to turn the unlimited moderation on and off.

    10. Yes, same problem with Quick Links. Fixed.

    11. No, if the block is empty, then the box around it is not drawn. In Slash::portalBox(), you can see the line:

            return unless $title && $contents;

    12. I dunno if it is worth changing, but perhaps.

    13. Added some more text to the block.

    14. Your help is greatly appreciated, thanks!

  • by Anonymous Coward
    I downloaded the code and had some problems while creating the tables, i had to split the biggest .sql files in 5 parts and then and only then it worked. Didn't touched the file, just splitted it... 093 worked fine.
  • Here are some things I've seen which didn't seem right, some things I'd like to see, and other musings (in no particular order)...

    1)If stories are posted as 'read only' or 'comments disabled' you can still post comments to them.

    2) Sometimes when I log into the admin page and select a link such as 'blocks', I get kicked back out to the login page. I can't get back in until I go to a different page and then back to the login page. This only happens occasionally and I haven't figured out how to recreate it.

    3) Enter 'first post' as the subject of a comment and hit 'preview', you get lameness filter, but hit 'submit' and it just takes you to a preview page with no lameness filter message.

    4) Seems my 'random block' slashbox doesn't update, it's been the same thing since I fired up .9.4

    5) If I go to the topics page and select 'recent topics', the page that comes up has part of the header but the rest of the page is blank. No messages in error_log or slashd.log

    6) Enter a comment with a string of letters and you get and unspecified lameness filter, enter a string of numbers and you get the "Please don't use so many caps.." filter.

    7) On the light version of the index page, most of the table elements are removed, but it still has the 'story_link' block and 'story_trailer' block elements, which create an unnecessary and incongruous table around the 'Read More.." link.

    8) When you select the 'older stuff' link from the main menu it takes you to submit.pl, which forces you to select a topic and author for the search. There should be (default) options in the search for 'All Topics' and 'All Authors'.

    9)Moderation for authors. My biggest wish. Authors (at least ones of a certain security level) should have unlimited ability to moderate comments. Seems odd that I can delete comments, but not moderate them. I know I can create a user and give him a bunch of points, but it's a hassle to have to log out and back in, plus then I'm subject to the same limitations as a regular user (an administrator should be able to moderate the same comment repeatedly if necessary)and my extra points disappear if slash is restarted.

    10)The 'uptime' slashbox is turned off for some reason so it won't show in the configuration choices. You need to go into sectionblocks and give it a title and set portal=1.

    11)When I have the 'top 10 comments' slashbox selected in preferences it never shows up on the main page. I don't have any high rated comments to go in it, but shouldn't at least an empty box show up?

    12) When you reply to a comment, on the 'post comment' page the title bar of the comment you are replying to is printed twice. You can change it so the top one says something like "You are commenting on..." by going to line 309 of comments.pl and changing " $reply->{subject}" to whatever you want that first bar to say.

    13) the newusermsg block is missing some variables to insert the site name and url path into the email that goes out.

    14) I've spent so much time goofing around with slash I'm getting grade B Carpal Tunnel Syndrome.

    grnarrow

  • 1. Installation Instructions for mod_perl = PERL_SECTIONS=1 is required for the code to work.

    2. Installing on a pre-existing system with PHP3 is a bitch and a half.

    3. After 8 hours of work on this (less 3 hours to go see a movie this afternoon) slashd is not starting. Getting following error:

    bash-2.03# /etc/slashd start
    Unquoted string "gme" may clash with future reserved word at /usr/local/lib/perl/site_perl/5.005/Mail/Sender.co nfig line 5.
    install_driver(mysql) failed: Can't load '/usr/local/lib/perl5

  • In response to your comment #2, this is because you previously logged out and some hidden form field to that effect is still lying around. To recreate this, logout and then try to login at the form which it takes you to. One way to get by this is to reload the page.

    One other thing is that if there is only a single article (like thats ever going to happen) there will be a strange left arrow on the article page. The right arrow is only displayed if ther is a next article but the left arrow is always displayed. This is only cosmetic but can be easily fixed.

    Finally, I noticed was that the pollbooth route in Slash.pm is missing the end angle bracket on the hidden field. This can have really mild but irritating effects on the display of the poll choices (i.e. not the correct font color).

  • I couldn't get the instructions to migrate the old database to work, so I had to junk it and start over. This is probably more due to my lack of SQL ability than anything else (though I'm learning fast with the help of a new book).

    Setting 'cookiedomain' in slashdotrc.pl to anything other than 'cookiedomain => '',' resulted in not setting any cookies ever. I guess this is why it's the default setting :-)

  • >3. I don't see this behavior. Can you go through an exact series of events, so we can replicate it?

    This doesn't happen on slashcode.com, but I double checked and it does occur on my site (I haven't altered my filter code in any way). If I enter a comment with the subject 'first post' and put whatever in the comment body, then hit the 'preview' button, the page that returns shows the preview block including the lameness filter message and the 'what you you want, a medal?' message. Now if I enter the same stuff, but hit the 'submit' button instead of 'preview', the page that comes back shows the preview block, but has no lameness filter message, and no 'what you want.." message.

    It's not a real big deal, I just thought it might be confusing for the user who is trying to submit but seems to be caught in a loop of previewing because they don't realize they tripped a filter. This is the only difference in behavior between 'submit' and 'preview' I have found after trying many different filters.

    >4. It [random box] seems to be working for Slashcode.com,

    Seems I was just confused, no surprise there. The random box is selected by choosing 'rand' on the customization page. I was chosing 'Semi-Random Box'. I haven't figured out what that one does. Could it just be a leftover of an old version of code? If so, I'll delete that one and change the title of the 'rand' box to 'Semi-Random Box'.

    >6. For the unspecified lameness filter, we use Compress::Zlib ...

    It's not the unspecified lameness filter message for a string of letters that bothers me, it was the 'don't use caps' message for a string of numbers. A user would find that confusing. An unspecified filter message would be better (of course an accurate specific message is always best).

    >7. Yes, I've noticed it. Maybe I'll whip up something to fix that soon. I'll just need to design different blocks to replace them...

    I don't think the light version need new blocks, it just needs to have those blocks removed when the page is constructed. All they do is build a table around the 'read more..' links.

  • I think 0.9.4 is the best release so far..
    -- Hillie
    --
    -- Hillie
  • by Anonymous Coward
    Yes, it is pretty swish! What I need now is some kind of rough documentation to get me going. I'd like to customise my site more and understand what I am actually doing :)

    Does anything like this exist I wonder?

    One thing I'd like to do is disable moderation for the time being, is this possible?

    Mike

    mike at dent dot org