slashcode-development — This list is for development of slashcode, no install questions please.

[Slashcode-development] "Please change your password now!" message

[Dan S. <Da...@IN...>]

The message "Please change your password now!", as seen on the user
preferences page after first login, is stored in a funny place.  It is
hard-coded into the Apache::User module:

         $form->{returnto} = url2abs($newpass
            ? "$constants->{rootdir}/users.pl?op=edit" .
              "user&note=Please+change+your+password+now!"
            : $form->{returnto}
               ? $form->{returnto}
               : $uri
         );

Shouldn't this phrase be stored in a template?

Re: [Slashcode-development] extracols/extra story fields

[Nathan V. <na...@th...>]

Cool, thanks a lot!  Was my patch in the bugs section on sourceforge
useful?  It's the first time I've submitted one so I'm curious if I've
done it right.

What is the story_text table and how does it work?  Should I just look at
the schema and code in fry?

-n

On Wed, 13 Jun 2001, Brian Aker wrote:

> Nathan Vonnahme wrote:
> >
> > I didn't get a response back about this, does anyone have any thoughts?
> >
> > I fixed extracols support in slash 2.0.0 in order to get something working
> > for a client, and I'd like to know what the future plans are if extracols
> > has been dropped so I can let him know what will be involved.
> I added it back. It doesn't hurt us to have it there (since we just
> do a single lookup based on key on the column). It is now
> in the story_text table though (setUser() handles getting the right
> tables, and putting them together).
>
> So expect it to stick around.
> 	-Brian
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
>

Re: [Slashcode-development] extracols/extra story fields

[Brian A. <br...@ta...>]

Nathan Vonnahme wrote:
> 
> I didn't get a response back about this, does anyone have any thoughts?
> 
> I fixed extracols support in slash 2.0.0 in order to get something working
> for a client, and I'd like to know what the future plans are if extracols
> has been dropped so I can let him know what will be involved.
I added it back. It doesn't hurt us to have it there (since we just
do a single lookup based on key on the column). It is now
in the story_text table though (setUser() handles getting the right
tables, and putting them together).

So expect it to stick around.
	-Brian

[Slashcode-development] extracols/extra story fields

[Nathan V. <na...@th...>]

I didn't get a response back about this, does anyone have any thoughts?

I fixed extracols support in slash 2.0.0 in order to get something working
for a client, and I'd like to know what the future plans are if extracols
has been dropped so I can let him know what will be involved.

The subclassing thoughts are beside that main point.

Cheers,
nathan


On Fri, 8 Jun 2001, Nathan Vonnahme wrote:

>
> On Fri, 8 Jun 2001, Brian Aker wrote:
>
> > I wouldn't use extracols, it has been dropped in the development schema.
> > I would make use of getStory() setStory() and let data fall into the
> > param table.
>
> Where should I do that?  And how are you going to make the slashdot books
> section work without the extracols stuff?  It is, in theory at least, a
> good way to provide extensions to certain sections.
>
> What I'd really like to see is a Story module that I could subclass,
> making use of inheritance as much as possible.  The Story module could
> know how to print its own edit form, short/full display, etc.  That would
> be much cooler than the templates.
>
> > > I would guess that there is a performance penalty for doing this sort of
> > > thing in the templates, but there may not be, since the templates are
> > Probably isn't, but there is another issue to not do it. If you
> > ever want to move to another database you won't have the ability to
> > use the abstraction layer to save you porting time. Plus if directly
> > hit the DB, you may find that in the future your templates
> > will break because we made some schema change.
>
> Well, it does use the DB method sqlSelectMany... which is abstracted in
> theory.  I can't see any way of getting around referring to certain fields
> and tables in the database, though.  I was trying to do this in the
> templates to avoid having trouble managing changes to the perl modules or
> .pl files.
>
> Which brings up a big question that's been irritating me:  how do the
> templates really help the customization situation?  With slash 2 we can
> now make most of our changes in the templates, so the perl code is easy to
> upgrade because we haven't needed to mess with it.  But the templates go
> through significant revisions too so we have to manage a similar amount of
> change to upgrade.  It's actually more of a pain because I find writing
> perlish things in the templates awkward, and it would be easier to just
> edit the perl code and manage changes there anyway.
>
> I know that you have lots of other things on your mind than another big
> architecture shift, but what would be more useful and extensible, I think,
> is to use inheritance more.  Somehow my theme or plugin should be able to
> inherit from the standard one -- that way changes to the distribution
> could often be inherited by custom themes and plugins.
>
> Like...  I want a book reviews section and each story needs to have extra
> fields like ISBN nad stuff.  So I subclass the Slash::Story
> object using this sort of thing:
>
> package Slash::Story::BookReview;
> push @ISA, 'Slash::Story';
> sub display {
>   # copy Slash::Story's display sub here and modify it
> }
> sub display_edit_form {
>   $self->SUPER::display_edit_form;
>   # print extra field edit stuff here... second form?
> }
> sub save {
>   $self->SUPER::save();
>   # save extra fields here
> }
> sub display_submit_form {
>   # same thing, etc.
> }
>
> But most of the story's subs would stay the same so we'd just inherit them
> automatically and not have to redefine them.
>
> -n
>
>
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
>

[Slashcode-development] Installing extra plugins

[Alessio B. <al...@al...>]

I have a specific problem, part of a more general one.

I am distributing the Italian translation as a theme (slashcode-it), it
gets installed in themes/ alongside slashcode. When the user goes to
create a new site it will choose either slashcode or other themes, but
only one. Ok. I am copying everything from slashcode into slashcode-it
so it's a drop-in replacement.

We need to translate plugins, too, so when the user runs
install-slashsite it will be prompted with a list of available plugins,
for example Search, Journal, Search-Italian and Journal-Italian. The
problem is that he can choose which plugins he wants (or "all") but in
fact he should only choose one max between Search*, one max between
Journal* etc. If two "conflicting" plugins are selected, the second one
will try to symlink in htdocs and fail, and will perform some INSERTs on
the database with no predictable behaviour, depending on the state of
the database as altered by the previous plugin.

Do we have to relay on the user being smart enough (ehm...) not to
choose conflicting plugins? Is there any other solution?

-- 
Alessio F. Bragadini		al...@al...
APL Financial Services		http://village.albourne.com
Nicosia, Cyprus		 	phone: +357-2-755750

"It is more complicated than you think"
		-- The Eighth Networking Truth from RFC 1925

[Slashcode-development] [ slashcode-Patches-432214 ] Formatted date at bottom of some pages

[<no...@so...>]

Patches item #432214, was updated on 2001-06-10 01:34
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=432214&group_id=4421

Category: MAIN branch
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alessio Bragadini (alessio)
Assigned to: Nobody/Anonymous (nobody)
Summary: Formatted date at bottom of some pages

Initial Comment:
authors.pl, hof.pl and topics.pl show a simple
'localtime' string at the bottom of the page to show
the last update. This patch allows a formatted and
translated date by an extra call to timeCalc.


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=432214&group_id=4421

[Slashcode-development] The ACL debate conclusion

[Alvaro d. C. <ac...@ba...>]

El 09 Jun 2001 03:33:18 -0700, Brian Aker escribió:
> Alvaro del Castillo wrote:
> > and admin plugin rol. We can have an ACL that controls this. It could be
> > a good idea to test the ACL system with this simple plugin to learn the
> > possibilities of the ACL system ;-) If not, we can use the seclev
> > system. To activate a plugin you need to have more that 5000 or 10000.
> You know, I can not remember where we ended up with the debate on ACL's.
> Pudge, do you remember?

I can ;-) But the actual solution is different:

- A plugin for ACLs with the ACL functions
- A plugin AdminACL that use this library


Chris Nandor wrote:
> Yeah, I was thinking about something very similar at one point, and
think
> this is a nice idea.  I wonder, though, if maybe users_param would be
a
> better user of this?  So instead of:
I would keep it out of users_param, but use the same schema. 

> Or, alternatively, implement users_acl _as_ a param-style table.  The
> problem, of course, is that we could have dozens of types of
permissions,
> and it is easier to just insert a new value than it is to change the
schema
> each time you want to add a new one (and this would make it more
easily
> extensible via the admin interface, too).  Also, a table with a few
dozen
> fields could be slower and more bloated.
The param style table is actually pretty quick for look ups. 

If the schema was modified to resemble a param table and we had patches
for getUser() and setUser() I would probably be all for including it.

It might be nice also to have a seperate table which described param's
currently in use.
        -Brian

-- Alvaro

[Slashcode-development] An Event system for slashcode ... =?ISO-8859-1?Q?=BFMessages?= plugin?

[Alvaro d. C. <ac...@ba...>]

Hi!

About 15 days ago we started to develop an event system for slashcode.
The idea is that a user can receive and e-mail (irc/icq message in the
future) when something change in the slashcode system: a new story, a
new comment in a story, a new comment in a thread ...

We create two table, one to collect the events and other with the
subscription from the user yo the different events. The idea is that the
events are channels of information and the user can subscribe to those
channels with a filter, so the user can specify which kind of events and
in a kind of event, can use a filter to tell which evets of this kind
the user can get informed.

The main problem for this system is the scalability but with it, you can
get a information channel with the user closer so the user can obtain
more advantages from the services that you give.

I have downloaded the fry code and I have found a "Message" plugin that
it seems to walk in the same direction but it is undocumented. Can
somebody tells the objetive of this plugin?

Cheers

-- Alvaro

karma plugin Re: [Slashcode-development] [ slashcode-Patches-431439 ] Arepository for plugins

[shane <sh...@lo...>]

At 03:33 AM 6/9/2001 -0700, you wrote:
>Alvaro del Castillo wrote:
> > and admin plugin rol. We can have an ACL that controls this. It could be
> > a good idea to test the ACL system with this simple plugin to learn the
> > possibilities of the ACL system ;-) If not, we can use the seclev
> > system. To activate a plugin you need to have more that 5000 or 10000.
>You know, I can not remember where we ended up with the debate on ACL's.
>Pudge, do you remember?
>
> > > 2) With category there needs to be a table listing
> > > category (AKA so they actually make sense).
> > Yes. We can use the createSelect function in Slash and have this
> > categories in a table. Maybe plugins_params ;-) because I think that a
> > plugin will change the info related to it in the near version of
> > slashcode.
>This is why code_params was created :)
>Easy enough for plugins to add items for getDescriptions().
>
> > But I am not sure if you refere to this. Maybe you talk about the
> > changes in the plugin between different versions and the patch needed to
> > upgrade the plugin.
>Yep, I was talking about revisions.
>
> > > 5) RSS output so that people can use it in slashboxes.
> > Yes, this is wonderfull :-)
>Pretty much everything should have the ability to dump data via
>RSS by this point. There is a Slash::XML library that was written
>for this (its only in Fry right now though, I could add a CVS module
>though for people to be able to extract it and install on their
>own). About a minute's worht of work.
>
> > - Instalation instructions.
> > - The possibility to have comments about the plugins from other users
> > maybe using a slash story.
>Comments for items like this is a fry feature, you can't really do them
>well in Bender.
>
> > - The possibility for the user to give points/stars to the plugins
>Overall moderation system tied to anything in the system.
>Cliff, any thoughts on this? I would love to see someone take the
>karma system and turn it into a plugin that could be used with
>any item. Since moderation is now tied in Fry to discussions you
>might be better off doing a seperate moderation system that
>worked on entities in the database. AKA tie it to anything
>with a primary key.

Oh please! This would be so cool. With the comments system
being redone, and something like this, you could stick comments
on anything, as well as karma "ratings" (is ratings the correct
word?) on anything.

  Shane

Re: [Slashcode-development] [ slashcode-Patches-431439 ] Arepository for plugins

[Brian A. <br...@ta...>]

Alvaro del Castillo wrote:
> and admin plugin rol. We can have an ACL that controls this. It could be
> a good idea to test the ACL system with this simple plugin to learn the
> possibilities of the ACL system ;-) If not, we can use the seclev
> system. To activate a plugin you need to have more that 5000 or 10000.
You know, I can not remember where we ended up with the debate on ACL's.
Pudge, do you remember?

> > 2) With category there needs to be a table listing
> > category (AKA so they actually make sense).
> Yes. We can use the createSelect function in Slash and have this
> categories in a table. Maybe plugins_params ;-) because I think that a
> plugin will change the info related to it in the near version of
> slashcode.
This is why code_params was created :)
Easy enough for plugins to add items for getDescriptions().

> But I am not sure if you refere to this. Maybe you talk about the
> changes in the plugin between different versions and the patch needed to
> upgrade the plugin.
Yep, I was talking about revisions.

> > 5) RSS output so that people can use it in slashboxes.
> Yes, this is wonderfull :-)
Pretty much everything should have the ability to dump data via
RSS by this point. There is a Slash::XML library that was written
for this (its only in Fry right now though, I could add a CVS module
though for people to be able to extract it and install on their
own). About a minute's worht of work.

> - Instalation instructions.
> - The possibility to have comments about the plugins from other users
> maybe using a slash story.
Comments for items like this is a fry feature, you can't really do them
well in Bender.

> - The possibility for the user to give points/stars to the plugins
Overall moderation system tied to anything in the system. 
Cliff, any thoughts on this? I would love to see someone take the
karma system and turn it into a plugin that could be used with
any item. Since moderation is now tied in Fry to discussions you
might be better off doing a seperate moderation system that
worked on entities in the database. AKA tie it to anything
with a primary key.

	-Brian

Re: [Slashcode-development] [ slashcode-Patches-431439 ] A repository for plugins

[Alvaro d. C. <ac...@ba...>]

Hi!

El 08 Jun 2001 11:26:12 -0700, Brian Aker escribió:
> Here are some comments I had on slashcode about this:
> Good start but it needs a couple of things though. 

Sure, it is very basic but I have try to make it very clean and very
short so we can start to add new functionality very easily.

> 1) The ability for an admin to approve a plugin (AKA you just don't want
> everyone adding stuff willy nilly).

We have a field called active. Maybe this field can only be changed by
and admin plugin rol. We can have an ACL that controls this. It could be
a good idea to test the ACL system with this simple plugin to learn the
possibilities of the ACL system ;-) If not, we can use the seclev
system. To activate a plugin you need to have more that 5000 or 10000.
 
> 2) With category there needs to be a table listing 
> category (AKA so they actually make sense).

Yes. We can use the createSelect function in Slash and have this
categories in a table. Maybe plugins_params ;-) because I think that a
plugin will change the info related to it in the near version of
slashcode.

> 
> 3) Someway to list changes (so update can happen).

Ops, the actual interface let you change the info about a plugin if you
have introduce it. Has you seen this? Try to insert a new plugin and
then you will have to list. The general plugin in list and a little list
with the plugins that you have introduce. If you click in a plugin owned
by you, then the interface show you a form that let you change the
plugin info.

But I am not sure if you refere to this. Maybe you talk about the
changes in the plugin between different versions and the patch needed to
upgrade the plugin.

> 
> 4) Someway to have ownership, so that only the editor can make changes. 

It is now in the plugin. If your slash user has introduce the plugin you
can edit it.

> 
> 5) RSS output so that people can use it in slashboxes.

Yes, this is wonderfull :-)

> 
> What else do others see a need for, aka what would make this the cat's
> meow?

- Instalation instructions.
- The possibility to have comments about the plugins from other users
maybe using a slash story.
- The possibility for the user to give points/stars to the plugins

Cheers


-- Alvaro


>       -Brian
> 
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
> 

Re: [Slashcode-development] (no subject)

[Nathan V. <na...@th...>]

On Fri, 8 Jun 2001, Brian Aker wrote:

> I wouldn't use extracols, it has been dropped in the development schema.
> I would make use of getStory() setStory() and let data fall into the
> param table.

Where should I do that?  And how are you going to make the slashdot books
section work without the extracols stuff?  It is, in theory at least, a
good way to provide extensions to certain sections.

What I'd really like to see is a Story module that I could subclass,
making use of inheritance as much as possible.  The Story module could
know how to print its own edit form, short/full display, etc.  That would
be much cooler than the templates.

> > I would guess that there is a performance penalty for doing this sort of
> > thing in the templates, but there may not be, since the templates are
> Probably isn't, but there is another issue to not do it. If you
> ever want to move to another database you won't have the ability to
> use the abstraction layer to save you porting time. Plus if directly
> hit the DB, you may find that in the future your templates
> will break because we made some schema change.

Well, it does use the DB method sqlSelectMany... which is abstracted in
theory.  I can't see any way of getting around referring to certain fields
and tables in the database, though.  I was trying to do this in the
templates to avoid having trouble managing changes to the perl modules or
.pl files.

Which brings up a big question that's been irritating me:  how do the
templates really help the customization situation?  With slash 2 we can
now make most of our changes in the templates, so the perl code is easy to
upgrade because we haven't needed to mess with it.  But the templates go
through significant revisions too so we have to manage a similar amount of
change to upgrade.  It's actually more of a pain because I find writing
perlish things in the templates awkward, and it would be easier to just
edit the perl code and manage changes there anyway.

I know that you have lots of other things on your mind than another big
architecture shift, but what would be more useful and extensible, I think,
is to use inheritance more.  Somehow my theme or plugin should be able to
inherit from the standard one -- that way changes to the distribution
could often be inherited by custom themes and plugins.

Like...  I want a book reviews section and each story needs to have extra
fields like ISBN nad stuff.  So I subclass the Slash::Story
object using this sort of thing:

package Slash::Story::BookReview;
push @ISA, 'Slash::Story';
sub display {
  # copy Slash::Story's display sub here and modify it
}
sub display_edit_form {
  $self->SUPER::display_edit_form;
  # print extra field edit stuff here... second form?
}
sub save {
  $self->SUPER::save();
  # save extra fields here
}
sub display_submit_form {
  # same thing, etc.
}

But most of the story's subs would stay the same so we'd just inherit them
automatically and not have to redefine them.

-n

Re: [Slashcode-development] [ slashcode-Patches-431439 ] A repository for plugins

[Brian A. <br...@ta...>]

Here are some comments I had on slashcode about this:
Good start but it needs a couple of things though. 
1) The ability for an admin to approve a plugin (AKA you just don't want
everyone adding stuff willy nilly).

2) With category there needs to be a table listing 
category (AKA so they actually make sense).

3) Someway to list changes (so update can happen).

4) Someway to have ownership, so that only the editor can make changes. 

5) RSS output so that people can use it in slashboxes.

What else do others see a need for, aka what would make this the cat's
meow?
	-Brian

Re: [Slashcode-development] (no subject)

[Brian A. <br...@ta...>]

Nathan Vonnahme wrote:
> You might look into the patch on the sourceforge bugs page to fix
> extracols support, but it won't exactly do what you want.  It might be
> useful to study, though, since it is doing something similar.
I wouldn't use extracols, it has been dropped in the development schema.
I would make use of getStory() setStory() and let data fall into the
param table.

> [%
> USE Slash;
> 
> # args are: columns, tables, where, other
> sth = Slash.db.sqlSelectMany(
>         'guide.sid, title, section',
>         'stories, guide',
>         "stories.sid = guide.sid AND guide_parent_sid = '$story.sid'",
>         'ORDER BY title'
> );
I have been wondering when it would cross someone's mind that they
can do that.

> Slash::DB has a mockery of documentation in it, you usually have to read
> the code in Slash::DB::MySQL to figure out what the methods do and how to
> call them.
Yeah, I stubbed it out and never did more then a few pieces of it. Time
:)

> I would guess that there is a performance penalty for doing this sort of
> thing in the templates, but there may not be, since the templates are
Probably isn't, but there is another issue to not do it. If you
ever want to move to another database you won't have the ability to
use the abstraction layer to save you porting time. Plus if directly
hit the DB, you may find that in the future your templates
will break because we made some schema change.

	-Brian

Re: [Slashcode-development] (no subject)

[Nathan V. <na...@th...>]

On Thu, 7 Jun 2001, John Bafford wrote:

> Hi all,
>
> I'm trying to coax slash into displaying story-related information
> that isn't stored in the stories table. I was hoping to be able to

> Is this possible at all? If not, is there a way to do a query
> directly from the template system? It seems like that's possible, but
> there doesn't seem to be much in the way of documentation for the
> template syntax.

You might look into the patch on the sourceforge bugs page to fix
extracols support, but it won't exactly do what you want.  It might be
useful to study, though, since it is doing something similar.

There are very good docs for the template markup at
  http://www.template-toolkit.org/docs/default/index.html

You can access any of the Slash::DB methods within the templates with the
Slash.db object after you've USEd Slash.
(a real working example):

[%
USE Slash;

# args are: columns, tables, where, other
sth = Slash.db.sqlSelectMany(
	'guide.sid, title, section',
	'stories, guide',
	"stories.sid = guide.sid AND guide_parent_sid = '$story.sid'",
	'ORDER BY title'
);

story.extras.child_links = [];

WHILE (c = sth.fetchrow_hashref);
	story.extras.child_links.push( Slash.linkStory({
		link    => c.title,
		sid     => c.sid,
		section => c.section,
	}) );
END; # end while c

IF story.extras.child_links;
	SET story.extras.child_links_lis =
story.extras.child_links.join("<li>");
	SET story.relatedtext = "$story.relatedtext
	<li> $story.extras.child_links_lis";
END;
%]


Slash::DB has a mockery of documentation in it, you usually have to read
the code in Slash::DB::MySQL to figure out what the methods do and how to
call them.

I would guess that there is a performance penalty for doing this sort of
thing in the templates, but there may not be, since the templates are
cached and compiled just like the perl.  But it is certainly more awkward
using the Template directives, I think (witness the goofy string
concatenation in the last three lines of the example).

The server error logs provide useful debugging output if you make syntax
errors in your templates.

Good luck,
nathan
-- 
Nathan Vonnahme             na...@th...
senior web developer        third sector technologies
http://enteuxis.org/nathan  http://thethirdsector.com

[Slashcode-development] [ slashcode-Patches-431439 ] A repository for plugins

[<no...@so...>]

Patches item #431439, was updated on 2001-06-08 09:58
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=431439&group_id=4421

Category: MAIN branch
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alvaro del Castillo (acs2)
Assigned to: Nobody/Anonymous (nobody)
Summary: A repository for plugins

Initial Comment:
This plugin implements a system to have a common place
to put
the reference to slashcode plugins, yes, a repository
for slashcode
plugins. We have to find the best place to put it,
maybe in http://slashcode.com/plugins.pl.

This is the first version so it have some bugs sure ;-)

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=431439&group_id=4421

[Slashcode-development] (no subject)

[John B. <ds...@zo...>]

Hi all,

I'm trying to coax slash into displaying story-related information 
that isn't stored in the stories table. I was hoping to be able to 
just change the query in getStory(), however, it seems that it's 
going through the query result cache, and I can't tell if there's any 
way that I can join the story table to something else without 
bypassing the story cache altogether.

What I'm trying to do right now is display a submission comments 
field that we've added to the submissions table, but I will likely 
need to pull from other sources with more complex relationships than 
a simple "left join submissions using(subid)".

Is this possible at all? If not, is there a way to do a query 
directly from the template system? It seems like that's possible, but 
there doesn't seem to be much in the way of documentation for the 
template syntax.

Thanks,

-John

-- 
John Bafford
ds...@zo...
http://www.dshadow.com/

[Slashcode-development] [ slashcode-Patches-431012 ] Patch to have date in language of choice

[<no...@so...>]

Patches item #431012, was updated on 2001-06-07 05:19
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=431012&group_id=4421

Category: MAIN branch
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alessio Bragadini (alessio)
Assigned to: Nobody/Anonymous (nobody)
Summary: Patch to have date in language of choice

Initial Comment:
This patch allows to have dates returned in a language
other than English. It does so by calling
Date::Manip::DateInit inside Slash::Utility::timeCalc.
The language is set using a new entry in the vars
table, called datelang. The value most be in a format
recognized by Date::Manip e.g. Italian, English,
German, etc. Only the languages supported by
Date::Manip can ofcourse be used.

It may run into trouble if the database engine doesn't
return date in English format, something that is not
very common and I believe not supported at all on
MySql. In this case, you would just have to set a
different default language. You could, ofcourse, put
extra code to handle this situation.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=431012&group_id=4421

[Slashcode-development] [ slashcode-Patches-430731 ] Slachcode hardcoded operations name

[<no...@so...>]

Patches item #430731, was updated on 2001-06-06 09:33
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=430731&group_id=4421

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alvaro del Castillo (acs2)
Assigned to: Nobody/Anonymous (nobody)
Summary: Slachcode hardcoded operations name

Initial Comment:
With this patch you can translate the name of the
operations that appears in the buttons of some pages,
the only thing that
at the moment can't be translated I think.



----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=430731&group_id=4421

[Slashcode-development] [ slashcode-Patches-428502 ] Localise PerlAccessHandler

[<no...@so...>]

Patches item #428502, was updated on 2001-05-29 16:30
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=428502&group_id=4421

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Kevin Tam (glorat)
Assigned to: Nobody/Anonymous (nobody)
Summary: Localise PerlAccessHandler 

Initial Comment:
PerlAccessHandler Slash::Apache::User

performs modifications on the Apache->request object 
that appears to render it unusable for mod_perl 
scripts outside Slash that use mod_perl and CGI. 
Specifically, CGI.pm will not handle POST requests if 
the request passses through that handler.

My workaround for this was to make sure the handler is 
only used for Slash's scripts and the change is as 
simple as

    <Location ~ "^/(([^/]*)\.pl)?$">
    PerlAccessHandler Slash::Apache::User
    PerlLogHandler Slash::Apache::Log
    </Location>

I also move the LogHandler in the config so that Slash 
doesn't log requests to my other scripts (but it will 
miss logs to Slash's .html .shtml etc. files). 
However, crucially, my other mod_perl app runs with 
Slash quite happily now that the PerlAccessHandler 
isn't in the way.

Here is the diff for bin/install-slashsite if it helps

--- install-slashsite   Wed May  9 19:02:34 2001
+++ install-slashsite-patch     Tue May 29 22:14:39 
2001
@@ -377,7 +377,9 @@

     SlashVirtualUser $opts{'u'}

+    <Location ~ "^/(([^/]*)\.pl)?$">
     PerlAccessHandler Slash::Apache::User
+    </Location>
     PerlLogHandler Slash::Apache::Log

     # this directive will redirect non-logged-in 
users to




----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=428502&group_id=4421

[Slashcode-development] [ slashcode-Patches-428387 ] email submissions in slash 1.x (upload)

[<no...@so...>]

Patches item #428387, was updated on 2001-05-29 11:14
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=428387&group_id=4421

Category: MAIN branch
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: email submissions in slash 1.x (upload)

Initial Comment:
okay, if I upload the file it should work better than 
pasting it...

Re:  <a href="http://slashcode.com/article.pl?sid=
01/05/23/2312221&mode=nested&threshold=">
this question at slashcode.com</a>

email pending submissions in slash 1.x

Cron it with 'quiet' as the first arg. 



----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=428387&group_id=4421

[Slashcode-development] [ slashcode-Patches-428381 ] email pending submissions in slash 1.x

[<no...@so...>]

Patches item #428381, was updated on 2001-05-29 10:43
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=428381&group_id=4421

Category: MAIN branch
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: email pending submissions in slash 1.x

Initial Comment:
Grr, sourceforge won't let me log in using IE5 Mac, 
the only browser that works with my OS (X)....

Cron it with 'quiet' as the first arg.

#!/usr/bin/perl

# by na...@th...

# run once a day, with a glass of water.
# usage:  email_new_submissions.pl [quietflag] 
[email] [subjectline]
# by default sends mail to all the authors in yer 
authors table.

use vars '%I';
use lib '..';
use Slash;
*I = getSlashConf();

my $usage = "usage:  $0 [quiet] [email] 
[subjectline]\n" ;

my $QUIET = 0;
if ($ARGV[0] =~ m/quiet/i) {
        shift @ARGV;
        $QUIET = 1;
}

my @to;
my $subject = $ARGV[2] || "$I{'sitename'} 
submissions";

if ($ARGV[1]) {
        push @to, $ARGV[1];
}
else {
        # get the authors to whom we should send 
mail...
        my $authors = sqlSelectMany(
                "email", 
                "authors", 
                "NOT ISNULL(email)"
        );
        while (my $a = $authors->fetchrow()) {
                push @to, $a;
        }
}

# this'll select all non-approved submissions that 
were submitted in the last 24 hours.
my $where = "del=0 AND time > 
DATE_SUB(NOW(), INTERVAL 1 DAY)";  

my ($count) = sqlSelect('count(*)', 'submissions', 
$where);

if ( $count > 0 ) {
        my $body = "$count new submission". 
($count>1?'s':'') . " today:\n";

        my $newsubs = sqlSelectMany(
                "name, subj, section, story", 
                "submissions", 
                $where
        );

        # put them into $body
        while ( my ($name, $subj, $section, $story) = 
$newsubs->fetchrow() ) {
                my $first50 = join ' ', (split m/\s+/, 
$story)[0..49];
                $body .= "\n" . '-' x 60 . "
Subject:  $subj
Submitted by:  $name
Section:  $section
First 50 words:  $first50
";
        }

        my $baseurl = $I{rootdir} || "http://
$I{basedomain}";
        $body .= '-' x 60 ."\nGo to $baseurl/admin.pl to 
post or delete.";

        foreach (@to) {
                sendEmail($_, $subject, $body);
                print "I just sent mail to $_\n" unless 
$QUIET;
        }

        print "and here's the gist of it:
Subject: $subject

$body
        " unless $QUIET;

}
else {
        print "No new submissions; not sending mail.\
n" unless $QUIET;
}


__END__

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=428381&group_id=4421

Re: [Slashcode-development] ¿Where to put the plugins?

[shane <sh...@lo...>]

At 09:43 AM 5/26/2001 +0200, you wrote:
>Hi!
>
>After two weeks of hard work, in Barrapunto.com we have converted all
>our new functionality to plugins. Now is time to show it to the
>community and receive some feedback. But, =BFwhere is the best place to
>put the plugins? =BFMaybe in the Sourceforge page as patches? =BFAn anno=
unce
>in slashcode.com? I think that in the near future we are going to need
>something like the GIMP Plugin Registry.
>
>About the plugins, I think that the PLUGIN file need another info: the
>daemon you need to put with slashd that the plugins needs.
>
>Bye for now guys ;-)

Personally, I'm waiting till slash2.2 comes out before I release any=20
plugins. The slashd is being redone for 2.2, which forces all plugins to =
be=20
redone to accomdate. Which is fine, because the new slashd system sounds=20
much improved. (see fry in CVS for the gory details).

  Shane

[Slashcode-development] [ slashcode-Patches-427976 ] Apache::Request control de HTTP params

[<no...@so...>]

Patches item #427976, was updated on 2001-05-28 08:37
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=427976&group_id=4421

Category: MAIN branch
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alvaro del Castillo (acs2)
Assigned to: Nobody/Anonymous (nobody)
Summary: Apache::Request control de HTTP params

Initial Comment:
This patch modifies the way slashcode 2.0.0 handle the
params received from the HTML Forms. The actual way
doesn't permit to have multivalue params or
ENCTYPE="multipart/form-data" forms.

The changes are minimal and this way is closer to the
way slashcode 1.0 do the work in a better way in my own
opinion.

Also, in the from HASH is stored also a pointer to the
Apache::Request created with the request from the user
so you can access it and use the Apache::Request
interface which is powerfull and simple from your
plugins.

If you have any doubt about the patch, please contact
me at ac...@ba.... You have to patch two files:

Slash/Utility.pm
Slash/Apache/User.pm



----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=304421&aid=427976&group_id=4421

[Slashcode-development] =?ISO-8859-1?Q?=BFWhere?= to put the plugins?

[Alvaro d. C. <ac...@ba...>]

Hi!

After two weeks of hard work, in Barrapunto.com we have converted all
our new functionality to plugins. Now is time to show it to the
community and receive some feedback. But, ¿where is the best place to
put the plugins? ¿Maybe in the Sourceforge page as patches? ¿An announce
in slashcode.com? I think that in the near future we are going to need
something like the GIMP Plugin Registry.

About the plugins, I think that the PLUGIN file need another info: the
daemon you need to put with slashd that the plugins needs.

Bye for now guys ;-)

-- Alvaro