Menu
▾
▴
slashcode-development
|
From: Alvaro d. C. <ac...@ba...> - 2001-04-20 17:58:22
|
Hi! 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 The solution is easy. Not destroy the table and use: INSERT INTO newstories SELECT * FROM stories 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. I have created index;index;gnome for example and it controls now the HTML rendering of the index for this section. 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 !!! :-( The solution for now is to save another time index;index;default. This time template-tool creates a new template for it :-) I have no time now to do the bug report and publish a patch. Maybe tomorrow when I continue the great playing. Have a good weekend ;-) -- Alvaro |
|
From: Dave H. <da...@ho...> - 2001-04-20 18:11:09
|
Alvaro del Castillo <ac...@ba...> writes: > Hi! > > 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: If you can do it, I'd heartily recommend moving to MySQL 3.23. Just all round better. -- Dave Hodgkinson, http://www.hodgkinson.org Editor-in-chief, The Highway Star http://www.deep-purple.com Interim CTO, web server farms, technical strategy ---------------------------------------- |
|
From: Alvaro d. C. <ac...@ba...> - 2001-04-21 08:10:15
|
On 20 Apr 2001 19:03:31 +0100, Dave Hodgkinson wrote: > Alvaro del Castillo <ac...@ba...> writes: > > > Hi! > > > > 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: > > If you can do it, I'd heartily recommend moving to MySQL 3.23. Just > all round better. Ok, I will take this suggestion and spent some time takeing a look at it ;-) Thanks -- Alvaro > > -- > Dave Hodgkinson, http://www.hodgkinson.org > Editor-in-chief, The Highway Star http://www.deep-purple.com > Interim CTO, web server farms, technical strategy > ---------------------------------------- > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |
|
From: Chris N. <pu...@po...> - 2001-04-20 18:27:35
|
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) 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 ... ?). >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. >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, -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
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 > |
|
From: Chris N. <pu...@po...> - 2001-04-23 14:32:39
|
At 10:00 +0200 2001.04.21, Alvaro del Castillo wrote:
>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.
I dunno. We asked several times on the lists and on the web site if anyone
had a problem with going to 3.23, and not one person said they did, that I
recall.
>Actually, yo can use it with Debian Potato, a very
>stable and widely used distribution.
Yeah. Since packages and RPMs are available, and even upgrading from
source is very easy AFAICT, those are all good signs.
>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.
For Slash 2.0, yes. For Slash 2.2, it probably just won't work. You will
almost surely need 3.23.
>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 ;-)
Well, at the very least, since Slash 2.0 will be finalized soon and will be
stable and will get all the bugfixes and will work (does work) fine with
MySQL 3.22, the worst case is we tell people to use Slash 2.0.x until their
packages/dist are upgraded to use MySQL 3.23.
>> >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 never seen this before, and don't know how it could be the case. In
Slash::Install::readTemplateFromFile, it just does:
for(qw| name page section lang seclev description title |) {
chomp($val{$_}) if $val{$_};
}
And then in Slash::DB::setTemplate(), it just passes the data along.
The only thing I can figure is that maybe you have some bad newlines (maybe
some CRLFs instead of plain CRs, or maybe some extra spaces or other
characters at the end of the __section__ line?) so that the section was not
defined, which would make it default to "default".
--
Chris Nandor pu...@po... http://pudge.net/
Open Source Development Network pu...@os... http://osdn.com/
|
|
From: Art G. <agi...@i-...> - 2001-04-23 14:56:02
|
Chris,
Actually, I've seen this behavior as well. I've been poking around the source and can't figure it out, but it definitely happens:
cp header;misc;default header;misc;art
<edit header;misc;art so that __section__ is now 'art' instead of 'default'>
template-tool -u slash -s header;misc;art
-> Preparing to insert header using filename header;misc;art
-> updated template header;misc;art tpid 4
Instead of creating a new entry in the db, it updates tpid '4'; the 'default' template.
I've tried using the -S art switch, too, but it always updates the existing template, instead of creating a new one.
Art
On Mon, Apr 23, 2001 at 10:31:23AM -0400, Chris Nandor wrote:
> At 10:00 +0200 2001.04.21, Alvaro del Castillo wrote:
> >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.
>
> I dunno. We asked several times on the lists and on the web site if anyone
> had a problem with going to 3.23, and not one person said they did, that I
> recall.
>
>
> >Actually, yo can use it with Debian Potato, a very
> >stable and widely used distribution.
>
> Yeah. Since packages and RPMs are available, and even upgrading from
> source is very easy AFAICT, those are all good signs.
>
>
> >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.
>
> For Slash 2.0, yes. For Slash 2.2, it probably just won't work. You will
> almost surely need 3.23.
>
>
> >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 ;-)
>
> Well, at the very least, since Slash 2.0 will be finalized soon and will be
> stable and will get all the bugfixes and will work (does work) fine with
> MySQL 3.22, the worst case is we tell people to use Slash 2.0.x until their
> packages/dist are upgraded to use MySQL 3.23.
>
>
> >> >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 never seen this before, and don't know how it could be the case. In
> Slash::Install::readTemplateFromFile, it just does:
>
> for(qw| name page section lang seclev description title |) {
> chomp($val{$_}) if $val{$_};
> }
>
> And then in Slash::DB::setTemplate(), it just passes the data along.
>
> The only thing I can figure is that maybe you have some bad newlines (maybe
> some CRLFs instead of plain CRs, or maybe some extra spaces or other
> characters at the end of the __section__ line?) so that the section was not
> defined, which would make it default to "default".
>
> --
> 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
---end quoted text---
|
|
From: Chris N. <pu...@po...> - 2001-04-23 15:42:21
|
Thanks Art, I found the problem, and will be committing a fix shortly. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X