From: Alvaro d. C. <ac...@ba...> - 2001-04-21 08:09:18
|
On 20 Apr 2001 14:26:15 -0400, Chris Nandor wrote: > At 19:31 +0200 2001.04.20, Alvaro del Castillo wrote: > >I have spent some days to migrate our modified database to slash 2.0. > >With the slash1toslash2 script all seems to be migrated well but in my > >installation, Debian Potato, the version of MySQL 3.22.32 doesn't > >support the MySQL command: > > > >CREATE newstories SELECT * FROM stories > > Ack. Well, realize two things: > > * Slash 2.2 will almost certainly require MySQL 3.23 > * Upgrading from 3.22 to 3.23 is very very easy (in my experience, and in > the words of others) Ops, it's a pity. I, as a developer, can migrate easily to MySQL 3.23 but thinks in users who want to run slashcode but they must use it with a distribution. Actually, yo can use it with Debian Potato, a very stable and widely used distribution. And we are working in making Debian packages for all the software needed to install slashcode-2.0 as a Debian package. I know that other people around slashcode are working in the same task. The next stable version for Debian will appear in the end of this year I think. But I can make some test and maybe we can generate Debian Potato packages for this MySQL version. > > Of course, if you are using Debian packages and don't want to change that, > you're kinda stuck until Debian comes out with a 3.23 package (which maybe > they have ... ?). Yes, sure. Maybe the slash 2.2 version will be published when we have a new version of Debian. And slashcode can't be limited for a distribution. But we must work to make slashcode more and more easy to use it with distributions and packages ;-) > > > >The solution is easy. Not destroy the table and use: > > > >INSERT INTO newstories SELECT * FROM stories > > That sounds OK to me. I'll look into it. > > > > >I am playing now with the templates and its customization for sections. > >It works quite well. It's fantastic to change the feel of a section > >creating a template for it. > > Yeah! I did a lot of the work setting up the template system, but even I > was kinda blown away when I first started using it to customize > http://use.perl.org/. I wanted a common copyright notice, so I created a > "useperlcopyright" template and put a few INCLUDE directives in the > templates, and boom! I really like the system we've come up with, it's > turned out better than I imagined, so far. Yes. In our slashcode modified, each user can have her own section. Think about it. Each user can control the templates for her section. We use ACLs for this. We are going to need a tool to edit the templates in the web and test the results ;-) > > > >But there is a problem. The template-tool doesn't work right. When you > >use: template-tool -s index;index;gnome it updates the > >index;index;default !!! :-( > > template-tool gets its information not from the filename, but for the > information embedded in the template. Chances are the section in the file > is labelled "default". Please confirm that this is the case. Thanks, Nop, I know it. In the template I change the section to gnome. So the template name was index;index;gnome and the section into the file was gnome. And when I save it with "template-tool -u slash2 -s index:index;gnome" the tool updates the index;index;defautl template. I have said it, you guys have done great work with slashcode. Bye -- Alvaro > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |