Slashcode

I'm using cronolog for my apache logs, and I really, really like it. I'd like to be able to use it on the slash logs as well, which become large and cumbersome over time with many sites running on a server. How do you all handle your logs? What do you use for log rotation? How long do you keep logs? Is anyone using cronolog, or something like it with slash?

Hi, I'm looking for a way to grab remote RDF and post them as stories. portald seems only to handle blocks.

I'm aware of the elixus.org, and the RSS2Story plugin in their patch of slashcode, but I can't get the plugin installed, and it seems to be left unfinished.

So is there any other way to do this?

I want to start using MySQL 4.1 to take advantage of the new Spatial extensions in MySQL to further enhance my plugin. I saw the recent story referring to using MySQL 4, but no direct mention of experience with versions 4+. Any tips or recommendations? Should I make the upgrade only on my development box, or is using 4+ okay. Any experience with 4.1, which is alpha?

I'm in the process of setting up a intranet Slash 2 site for a company.

With the aid of the Crow Book I've got everything installed and with the L'n'F that they want, and we are in the process of adding some initial content and getting the blocks running the way they want.

However, we're having problems getting section-specific quick links blocks to work. Example: I have a section called legal, and a block called legal_qlinks which has different links to index_qlinks. index_qlinks shows up on the homepage as I expect, but nothing is displayed in the right "frame" if I click no the section title under an article.

What am I doing wrong? The Crow Book (page 127) suggests that this should work.

I have comps for a site I want built in Slash. While I have worked with Movable Type, building Slash templates is a whole different beast. I need someone to help me convert my comps into a functioning Slash site. If you have these skills, please drop me a line with your rates and scheduling availability. You can see what the site will look like here.
--
Markos