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

Re: [Slashcode-development] variable table names

[Chris N. <pu...@po...>]

At 18:09 -0600 2000.11.20, Jason Richey wrote:
>replace all (EEK!) occurrences of explicit table names with lookups
>	within the Bender code.  From what I can tell, all occurences
>	are within the Slash/DB subtree (Are there any hidden
>	elsewhere?).

No.  All are in Slash::DB.

I don't know if this would be a good idea or not, but it is certainly
something to consider.  I suppose if this table were read in at the
beginning and the mappings cached, the overhead shouldn't be too
significant, except on startup.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] variable table names

[Jason R. <ja...@ar...>]

I've been looking into writing a module for Bender that would allow
table names to be specified by the site admin.  I think
that the following would be a usable setup for such a thing:

add a table "tables" to the sql database of the slashsite
	this table would be the only table that is required to exist
	within this database.  It would contain mappings from 
	table names to actual table locations.  Hypothetically,
	all other tables could be moved to different databases.

add a module that exports a lookup function for the tables

replace all (EEK!) occurrences of explicit table names with lookups
	within the Bender code.  From what I can tell, all occurences
	are within the Slash/DB subtree (Are there any hidden
	elsewhere?).

add functionality to edit values inside the "tables" table (something
	like what has been done with the "vars" table)

------

	Any Input?  I don't know if specifying a full table name
(database.table) is a problem for any of the perl database handling
routines.  I know that it works in MySQL from command-line.  Is there
any performance loss for operating on multiple databases from within
the same script?  I don't see why there would be. I'm looking for some
criticism here, please.  

Thanks in advance,

Jason Richey


Brian Aker wrote:

> Jason Richey wrote:
> > 
> > My company runs several sites based on the slashdot code.  We find it
> > very useful.  However, we would find it more useful if we could have
> > the sites share the same users (and user-related) tables.  I was
> > thinking of changing the code to support such a thing by adding
> > another slashdotrc.pl type file (maybe tablesrc.pl) that maps table
> > handles to table names, then changing the rest of the code to
> > reference table handles instead of the hard-coding that is used now.
> > 
> > I don't know if this would be something that you feel would be a nice
> > "feature" for the slashcode or not, but I would be willing to make a
> > patch that does it if you guys express some interest.  Let me know if
> > I am way off base here.
> Its an excelent patch, but it would get lost in the conversion to
> Bender. Support for this type of Module in Bender would be welcomed
> though. 
> 
> 	-Brian
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/mailman/listinfo/slashcode-development

-- 
"Jason C. Richey" <ja...@ar...>

Re: [Slashcode-development] variable table names

[Chris N. <pu...@po...>]

At 19:04 -0600 2000.11.10, Jason Richey wrote:
>I'm a little confused about where site configuration information is
>being kept in Bender.  Would somebody please point me in the right
>direction?

The vars table.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] latest commits

[Chris N. <pu...@po...>]

I committed my changes to make SSL work (really minor things, basically
making default URLs begin with //example.com/ instead of
http://example.com/, and some changes to Slash::redirect()).

I added some additional fixes to various things.  Pat, the template editor
seems to work fine.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Bender: mod_perl / mod_php / Apache incompatibilities

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

Steve Linberg wrote:
> 
> Folks,
> 
> Any idea whether any ground is being gained on the mod_perl / mod_php
> problems of the current Slash tree?  I had to remove php from my server to
> get Slash working, which isn't a big loss for me but I have some clients
> that are going to be a bit steamed.
Are you referring to the mod_perl and PHP4 issue where one of the them
is causing apache to core?
It is a bit out of our scope :)

	-Brian

[Slashcode-development] Slash and SSL

[Chris N. <pu...@po...>]

OK, I got my local bender setup working simultaenously with SSL.  Here's
the essence of it:

* This will only work for ports 80 and 443, and all on the same hostname.

* This will only work if httpd yours have the same hostname.

* Set some vars.  Make absolutedir what rootdir normally is (it should be
this by default), remove "http:" from the front of rootdir and imagedir.
Now they are relative to whatever protocol you are using, which is the key
here.

* Configure your httpd.conf (assuming SSL is already set up*).  I did mine
like this:

NameVirtualHost s1.pudge.net:80
NameVirtualHost s1.pudge.net:443

Then I for this block:

<VirtualHost s1.pudge.net:80>

I changed to:

<VirtualHost s1.pudge.net:80 s1.pudge.net:443>


And then I added my site-specific SSL configs there:

<IfDefine SSL>
SSLEngine on
SSLCipherSuite ALL:!ADH:!EXP56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key
</IfDefine>



* I used mod_ssl.  I got OpenSSL and built and installed it, got Apache
1.3.14 and unpacked it, then got and configured mod_ssl (which patched the
Apache tree).  Then I got the latest mod_perl (1.24_01 needed) and did the
following:

  perl Makefile.PL APACHE_SRC=../apache_1.3.14/src DO_HTTPD=1 USE_APACI=1 \
    PERL_MARK_WHERE=1 EVERYTHING=1 APACHE_PREFIX=/usr/local/apache
    ADD_MODULE=headers,ssl,rewrite SSL_BASE=/usr/local/ssl/

Then I ran a make.  Then I went to the apache dir and did "make
certificate", ran make install, then went back to the mod_perl to run make
instalkl for good measure.

And that is most of it there.  I added the global SSL configs to my
httpd.conf, and ran `apachectl startssl`.  I'll bang on it some more, but I
think that none of this requires any further changes to the Slash source,
just the few configs in the vars table.

There are probably little bugs, but we'll squash them as we go along.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] Bender: mod_perl / mod_php / Apache incompatibilities

[Steve L. <st...@si...>]

Folks,

Any idea whether any ground is being gained on the mod_perl / mod_php 
problems of the current Slash tree?  I had to remove php from my server to
get Slash working, which isn't a big loss for me but I have some clients  
that are going to be a bit steamed.
  
I understand that this is not a Slash issue per se, but I know there are  
folks out there that would like to be able to use Slash on php-enabled    
servers, so I thought I'd ask if there's any irons in the fire on this    
issue.
  
Cheers,
  
Steve Linberg

-- 
Steve Linberg, Chief Goblin 
Silicon Goblin Technologies 
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle. 

Re: [Slashcode-development] variable table names

[Jason R. <ja...@ar...>]

I hate to sound like an idiot, but...

I'm a little confused about where site configuration information is
being kept in Bender.  Would somebody please point me in the right
direction?

I'm walking through the code, trying to figure the best way to
implement such a thing.  Unfortunately, I have very little experience
with mod_perl, so I get confused too quickly.

Jason Richey

Jason Richey wrote:

> I appreciate the response...  I'll look into writing such a thing for Bender.
> 
> Jason C. Richey
> 
> Brian Aker wrote:
> 
> > Its an excelent patch, but it would get lost in the conversion to
> > Bender. Support for this type of Module in Bender would be welcomed
> > though. 
> > 
> > 	-Brian
> > _______________________________________________
> > Slashcode-development mailing list
> > Sla...@li...
> > http://lists.sourceforge.net/mailman/listinfo/slashcode-development
> 
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/mailman/listinfo/slashcode-development

-- 
"Jason C. Richey" <ja...@ar...>

Re: [Slashcode-development] variable table names

[Jason R. <ja...@ar...>]

I appreciate the response...  I'll look into writing such a thing for Bender.

Jason C. Richey

Brian Aker wrote:

> Its an excelent patch, but it would get lost in the conversion to
> Bender. Support for this type of Module in Bender would be welcomed
> though. 
> 
> 	-Brian
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/mailman/listinfo/slashcode-development

Re: [Slashcode-development] variable table names

[Eric D. <eri...@ja...>]

Um, thats a great idea. I too would be interested in such a thing. But,
maybe there is an easier way?

Two ideas.

1. Have one user database's users table be the main userbase, and change
the other sites SQL stuff to reference slash.users instead of their
internal users table. That might work......

2. Perhaps modify the users.pl so when you make changes and stuff, it
updates all the related sites's databases (ie: you have users table in
all the sites, and have the code update the user info across the board.)

Ideas just off the top of my head. But I think a Bender module would be
better and hopefully we all can start using Bender instead of Slash 1.0.9
real soon? ;-)



Jason Richey wrote:

> My company runs several sites based on the slashdot code.  We find it
> very useful.  However, we would find it more useful if we could have
> the sites share the same users (and user-related) tables.  I was
> thinking of changing the code to support such a thing by adding
> another slashdotrc.pl type file (maybe tablesrc.pl) that maps table
> handles to table names, then changing the rest of the code to
> reference table handles instead of the hard-coding that is used now.
>
> I don't know if this would be something that you feel would be a nice
> "feature" for the slashcode or not, but I would be willing to make a
> patch that does it if you guys express some interest.  Let me know if
> I am way off base here.
>
> --
> "Jason C. Richey" <ja...@ar...>
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/mailman/listinfo/slashcode-development

--
<version 2.0.0>
<tag>
Not tonight, dear.  I have a modem.
</tag>

Re: [Slashcode-development] variable table names

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

Jason Richey wrote:
> 
> My company runs several sites based on the slashdot code.  We find it
> very useful.  However, we would find it more useful if we could have
> the sites share the same users (and user-related) tables.  I was
> thinking of changing the code to support such a thing by adding
> another slashdotrc.pl type file (maybe tablesrc.pl) that maps table
> handles to table names, then changing the rest of the code to
> reference table handles instead of the hard-coding that is used now.
> 
> I don't know if this would be something that you feel would be a nice
> "feature" for the slashcode or not, but I would be willing to make a
> patch that does it if you guys express some interest.  Let me know if
> I am way off base here.
Its an excelent patch, but it would get lost in the conversion to
Bender. Support for this type of Module in Bender would be welcomed
though. 

	-Brian

[Slashcode-development] variable table names

[Jason R. <ja...@ar...>]

My company runs several sites based on the slashdot code.  We find it
very useful.  However, we would find it more useful if we could have
the sites share the same users (and user-related) tables.  I was
thinking of changing the code to support such a thing by adding
another slashdotrc.pl type file (maybe tablesrc.pl) that maps table
handles to table names, then changing the rest of the code to
reference table handles instead of the hard-coding that is used now.

I don't know if this would be something that you feel would be a nice
"feature" for the slashcode or not, but I would be willing to make a
patch that does it if you guys express some interest.  Let me know if
I am way off base here.

-- 
"Jason C. Richey" <ja...@ar...>

[Slashcode-development] getSearch* methods

[Chris N. <pu...@po...>]

Did they disappear from MySQL.pm ?

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] postmodes stuff

[Chris N. <pu...@po...>]

OK, so postmodes is moved into code_param.  These modes were used for
stripByMode, and were text modes.  Now there are numbers.

We now have seven functions (all exported from Slash::Utility) in addition
to stripByMode: strip_attribute(), strip_code(), strip_html(),
strip_nohtml(), strip_literal(), strip_plaintext(), strip_extrans().

Where stripByMode took arguments STRING, MODE, NOWHITEFIX, the others take
STRING, NOWHITEFIX (since MODE is done automatically), and each of these
functions just calls stripByMode.

stripByMode is NOT still there.  Instead, use the function you want to do
the function you want.  If you get passed a postmode, then call
strip_mode().  That is:

   print strip_literal($sometext);

   print strip_mode($someothertext, $form->{posttype});

Also, these 8 functions are available as filters in templates:

   [% FILTER strip_nohtml %][% form.data %][% END %]

Let me know any questions you have about this.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Template Toolkit

[Chris N. <pu...@po...>]

Also, I am changing the slashDisplay syntax.  Instead of having a bunch of
flags, it will be a hashref, like:

  my $foo = slashDisplay('hof-data', $hashref, { Return => 1, Nocomm => 1 });

However, if all you want is the Return flag set, you can still do:

  my $foo = slashDisplay('hof-data', $hashref, 1);

So there are really two syntaxes:

  slashDisplay(NAME, DATA, OPTIONS)
  slashDisplay(NAME, DATA, RETURN)

Right now, three options are recognized: Return, Nocomm, and Section.
Section allows you to specify a specific section (such as "tacohell"), no
section (the special text "NONE"), or let it use whatever current section
you happen to be in (the default).

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] Re: [Slashcode] unifed logon for multiple slash sites ? (fwd)

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

Chris Nandor wrote:
> An admin is not tied in the same way as a user.  You cannot (now) easily
> log in across sites with a single admin login, because it works with a
> "session" cookie instead of a uid/password cookie.  That session cookie
> will expire, and is stored in the database.
That has changed in bender. If you wrote a library to pull from a slash
site
other then the default, you would gain the seclev from the site that
you pulled from.

I imagine that at some point in the near future the user methods will
become
their own library (I keep seeing this as being helpful for sites that
want to keep one set of logins/user info for all users). This will be
fairly trivial to do, its just not at the top of this list.

> >2. also tried creating different aids  to logon with for each slash
> >site... but does not help..
> Yeah, hrm.  The session cookie would get overwritten, since they all share
> a cookiedomain, so you could only be logged in as admin to one at a time.
> Well, we might be able to take care of this in Bender.  We are working on
> that code right now.  Krow, how do sessions work now, in Bender?  Do we
> still have them at all?
Sessions still exist but they are really only used to track when admins
last used the site and the current title of what they are working on.

Under bender you have one account, your seclev determines your privs. If
you
have a seclev >= 99 then you are an author. The admin.pl page determines
who
is displayed based on 1) if you have any stories posted 2) your seclev
is above >=99.

	-Brian

[Slashcode-development] Template Toolkit

[Chris N. <pu...@po...>]

There is a Release Candidate for Template Toolkit 2.00 available from
http://www.template-toolkit.org/.  It doesn't appear to require any
changes, but if there are significant changes, I will pass them along (or
if any of you find them, you can pass them along).  I have one change to
make to Slash::Display (we no longer need to explicitly require
Template::Stash), but that will wait until 2.00 is released and everyone
can then upgrade.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] Re: [Slashcode] Release of Bender

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

shane wrote:
> 
> At 12:44 PM 10/24/2000 -0700, you wrote:
> >This is the first alpha release of the next major version of Slash.
> >It is broken. It is very cool, though, so please test it if you are
> >so inclined, but don't use it in production.
> >It features nifty things like theme support, an API for the database,
> >framework to begin Oracle and PostgreSQL support, a new template
> >system, a better install, structure for third party modules, and
> >better support for hosting multiple slash sites.
> >You can find it here:
> >ftp://ftp.slashdot.org/pub/slash/slash-1.1.0-bender.tar.gz
> 
> Has the Bundle::Slash been updated
> with the perl modules that Bender needs?

Look at the file, INSTALL.bender for install instructions.
	-Brian

[Slashcode-development] Release of Bender

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

This is the first alpha release of the next major version of Slash. 
It is broken. It is very cool, though, so please test it if you are 
so inclined, but don't use it in production.
It features nifty things like theme support, an API for the database, 
framework to begin Oracle and PostgreSQL support, a new template 
system, a better install, structure for third party modules, and 
better support for hosting multiple slash sites.
You can find it here: 
ftp://ftp.slashdot.org/pub/slash/slash-1.1.0-bender.tar.gz

	-Brian

Re: [Slashcode-development] test ?

[Steve L. <st...@si...>]

On Tue, 24 Oct 2000, Chris Nandor wrote:

> Hello?

Hello.

-- 
Steve Linberg, Chief Goblin 
Silicon Goblin Technologies 
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle. 

[Slashcode-development] test ?

[Chris N. <pu...@po...>]

Hello?

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] tailslash

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

Syntax change for tailslash. 
The first argument is now a DBIx::Password virtual username.

It also now works with bender and should install itself correctly.

	-Brian

[Slashcode-development] Bender

[Chris N. <pu...@po...>]

LEELA: We're going to deliver this crate like professionals.
FRY: Aww, can't we just dump it in the sewer and say we delivered it?
BENDER: Too much work!  I say we burn it, then *say* we dumped it in the sewer!

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

[Slashcode-development] Installing bender on debian

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

At the moment the Makefile is setup to install under
Redhat 6.x. To install under Debian, Solaris or RedHat 7.0
you will want to:
make install INIT=/etc

	-Brian