Slash

eduslash@... (Tom Utley) writes:

> Every day in my daily stats message I get a list of 12 random
> users created "yesterday" yet it reports users that have been
> in the system for quite some time. Are my users not marked
> correctly or is this just a bug in the stats message?

That's really just a bug (my bug) but it doesn't hurt much so
I haven't gotten around to fixing it...

are these formkeys imported from your 1.0 site? If so, I wouldn't bother 
importing them. If they're old formkeys, especially ones that haven't 
been used for a final successful submission of a form, then nuke them.

I wrote a lot of this code, and even though I haven't messed with it in a 
while, I think this will work for you.

regards,

Patrick

On 
Thu, 24 Apr 2003, Nathaniel Irons wrote:

> I'm setting up Slash 2.2.6 on Mac OS X Server, and converting data
> from a 1.0 site. It's gone fine, and I've been attending to template
> problems for the last few days. Yesterday, I started seeing "invalid
> form key" errors, all the time, from every form that uses form keys.
> 
> The only definition of an "invalid" form key I can find is from
> docs/formkeys.txt:
> 
>     * invalid - the formkey is invalid because they are trying
>     to submit with a key that hasn't even been issued
> 
> This does not appear to be true in my case. As soon as I generate the
> page containing a formkey in its hidden field, I can retrieve the
> corresponding record from the database. All the formkeys currently in
> my database follow this format:
> 
> mysql> select * from formkeys where formkey = 'MHSiEb5i4H'\G
> *************************** 1. row ***************************
>        formkey: MHSiEb5i4H
>       formname: users
>             id:
>        idcount: 0
>            uid: 9855
>           ipid: 5d0739dc4467d34c1241e1b4d3483892
>       subnetid: 0eb1ccf00e8105eee74c91b80be44ad0
>          value: 0
>        last_ts: 0
>             ts: 1051135294
>      submit_ts: 0
> content_length: 0
> 1 row in set (0.00 sec)
> 
> I don't know if any of the above is unusual. I can trigger this
> problem from multiple form names, multiple uids, and multiple
> ipid/subnetid combinations. Of course, I've tried stop/starting apache
> and slashd. 
> 
> I have a disposable Mac OS X 10.2.5 machine on which I set up Slash
> 2.2.6 as a dry run -- I returned to it when the formkey problem
> appeared, and it was exhibiting the same symptoms. I was unable to
> recreate the formkey errors after re-running install-slashsite, after
> importing a database dump from before the problems appeared, or after
> importing a database dump from after the problems appeared.
> 
> I expect this means I can reinstall slash and re-import my data on the
> main server to get back to work. I'd much prefer to understand the
> glitch and make sure it doesn't come back. Thanks for any assistance.
> 
>   -nat
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Slashcode-general mailing list
> Slashcode-general@...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
> 

-- 
Patrick Galbraith
Senior Software Developer
pgalbraith@...
patg@... capttofu@...

On Thu, Apr 24, 2003 at 04:39:31PM -0700, Patrick Galbraith wrote:

> are these formkeys imported from your 1.0 site? If so, I wouldn't bother 
> importing them. If they're old formkeys, especially ones that haven't 
> been used for a final successful submission of a form, then nuke them.

slashd is periodically deleting formkeys, as it should -- when I first
noticed the problem on the soon-to-be-production server, the only
formkeys in the database were the ones generated by me since the
problem had begun. No formkeys are coming across from the 1.0 data.

The problem seems to be tied up in the definition of an invalid
formkey. As I said, as soon as I request comments.pl, the formkey
embedded in the HTML form has been properly created in the
database. Can "invalid formkey" indicate anything other than absence
from the database?

I haven't tried to step through the code, but if you can't put your
finger on the problem, I guess that's next. If you have any
suggestions on where to start looking, I'd appreciate it.

Thanks, 

  -nat

** Reply to message from "Evan Erwin" <evan@...> on Sun, 20
Apr 2003 00:50:16 -0400

Hi Evan,

Yes, the fix is already checked into CVS - I got a response from Jamie
soon after I reported the fix.

George

> Let's hope they implement that fix into slash permanently...
> 
> Evan

gac@... (George Clark) writes:

> Is this telling me that Perl is actually not finding the
> modules,  or that there is something wrong with the module so
> that it might be found, but is not accepted by perl for some
> reason.   Or is it something within the Slash installation
> that might be triggering this?  I have no idea where to look
> next.

It just means Slash::Test didn't include that module.

Here's your output:

> # perl -MSlash::Test=wapav -le 'print $INC{"Slash/Admin.pm"}'
> /usr/local/share/perl/5.8.0/Slash/Admin.pm
> # perl -MSlash::Test=wapav -le 'print $INC{"Slash/Events.pm"}'
> 

And here's mine, on my test site:

> $ perl -MSlash::Test=slash -le 'print $INC{"Slash/Admin.pm"}'
> /usr/local/share/perl/5.6.1/Slash/Admin.pm
> $ perl -MSlash::Test=slash -le 'print $INC{"Slash/Events.pm"}'
> 

Why would a module not be included?  Slash::Test runs through your
list of _installed_ plugins, and calls getObject() on each one.
getObject() does a "require" of each module.  So if a plugin
isn't installed in your site, it won't get imported.

If I specifically tell Perl to go find a module, it finds it,
no problem, and I bet the same would be true for your site:

> $ perl -MSlash::Events -MSlash::Test=slash -le 'print $INC{"Slash/Events.pm"}'
> /usr/local/share/perl/5.6.1/Slash/Events.pm

** Reply to message from Jamie McCarthy <jamie@...> on Fri, 18
Apr 2003 12:18:04 -0400

Hi Jamie,

> Why would a module not be included?  Slash::Test runs through your
> list of _installed_ plugins, and calls getObject() on each one.
> getObject() does a "require" of each module.  So if a plugin
> isn't installed in your site, it won't get imported.

Hmmm.  Okay,  so this proves that it is not a path problem - as you
suggest, tell perl to find the module and it worked fine on my system.   
And if I add the -MSlash::Email onto the "Dumper" test,  that now works
as well.

~$  perl -MSlash::Email -MSlash::Test=wapav -le 'print Dumper
getObject("Slash::Email")'
$VAR1 = bless( {
                 '_dbh' => bless( {}, 'DBIx::Password' ),
                 'virtual_user' => 'wapav'
               }, 'Slash::Email' );

But fails without it. 

~$  perl -MSlash::Test=wapav -le 'print Dumper getObject("Slash::Email")'
$VAR1 = undef;

So the problem appears to be related to either to my plugin list,  or the
getObject() "require" is failing for some reason.  The email plugin is in
the table, so I guess that it comes down to an issue with the getObject.

+----------+----------------------+-------+--------------------------------------------------------------------+
| param_id | name                 | value | description
         |
+----------+----------------------+-------+--------------------------------------------------------------------+
|       26 | plugin               | Email | "Allows users to email text
versions of articles to someone else." |
|       27 | plugin_Email_symlink | 1     | Email plugin files installed
symlink |
+----------+----------------------+-------+--------------------------------------------------------------------+

The site plugins seem to be set okay ... Any suggestions on how to debug
getObject, or why it's not finding the plugin?  (And I need to do this on
a live system - I've been unable to recreate the issue on my test system
- works fine there.   The problem came about after I migrated my
production system to Debian.)    I expect that getObject in
Environment.pm gets called quite a bit - I doubt that it would be a good
idea to add "print" statements.    Would it be okay to insert errorLog
calls in the getObject routine to determine where it is failing and to
trace the steps along the way?

I'll keep pluggin away to try to get to the bottom of this - and maybe
I'll learn a bit more about perl along the way.

Thanks again for the help .

George

** Reply to message from Jamie McCarthy <jamie@...> on Fri, 18
Apr 2003 12:18:04 -0400

Hi Jamie,

I added a bunch of errorLog calls for brief window and ran the test on my
production system.

Here is where things fail in getObject.

        if (!$data->{nocache} && $objects->{$class, $vuser}) {
                errorLog(" we've been here before ");
                # we've been here before, and it didn't work last time ...
                # what, you think you can try it again and it will work
                # magically this time?  you think you're better than me?
                if ($objects->{$class, $vuser} eq 'NA') {
                        errorLog(" returning undef because of NA");
                        return undef;

Error in library:main:-e:1:class = Slash::Email

Error in library:main:-e:1: we've been here before

Error in library:main:-e:1: returning undef because of NA

Any more ideas on what this is telling me?

Thanks,
George

** Reply to message from "George Clark" <gac@...> on Fri, 18
Apr 2003 21:13:32 -0400

I'm going to call it quits for the weekend ... but, a bit more
information.

I added one more bit of debug code to dump out the hash table when NA is
found.

It appears that the hash table has been previously loaded, from apache
maybe???  Slash::Email was indeed in the table, set to NA,  and the
Slash::Test never actually tried to load it, because it was already in
the cache.   So without disabling the cache, I can't determine why it is
set to NA.   I put debug code in Environment.pm to display the first time
it issues the "eval" - and it never tries.  So somehow that hash table
was previously built.

I tried shutting down Apache, and the hash table is still fully populated
????

Here is a piece of the dump

Error in library:main:-e:1: Slash::Messages wapav =
Slash::Messages=HASH(0x8f90010)
Error in library:main:-e:1: Slash::FAQ wapav = NA
Error in library:main:-e:1: Slash::Email wapav = NA
Error in library:main:-e:1: Slash::Journal wapav =
Slash::Journal=HASH(0x8fb4774)

And  this is from the Slash::Test class,  and I never attempted to load
any of these classes, except for Slash::Email.

Sorry to express my ignorance, but where the heck is this stuff cached?  
I knew better <g>  but I just rebooted,  and still, the dump of that
table when running the Slash::Test Dumper test has the module already in
the Hash table,  already set to NA.

Thanks,
George

** Reply to message from "George Clark" <gac@...> on Fri, 18
Apr 2003 22:35:39 -0400

I ran the test specifying nocache:

 perl -MSlash::Test=wapav  -le 'print Dumper getObject("Slash::Email",
{nocache => false} )'
Error in library:main:-e:1:Slash/Email.pm did not return a true value at
(eval 83) line 3.

Turns out Email.pm does not end with the   

1;

that all the other perl modules end with.   HumanConf.pm appears to have
the same problem.

I added a 1;  as the last line of Email.pm and the problem is FIXED!   

George

On Wed, 2003-04-16 at 18:15, George Clark wrote:
>  - A story with multiple topics,  topics other than the first listed
> topic are not found using the topic search.  This seems to be happening
> on slashdot as well as my local installation.  
Yep, this will be added in the future.

>  - Stories (using the default slashcode templates) only show a single
> topic, not multiples, even though the multiple topics show up in the URL.
This is fixed in CVS. The slashcode dispStory template did not have support in it for this, it does now.


> a Bug Report, or is it a known issue?
Sure, put in a bug report about search if you wish to track it.

	-Brian
-- 
_______________________________________________________
Brian "Krow" Aker, brian@...
Slashdot Senior Developer
Seattle, Washington
http://krow.net/
http://askbrian.org/
_______________________________________________________
You can't grep a dead tree.

On Wednesday 02 April 2003 13:32, Patrick Galbraith wrote:
> Check out the Page plugin - it can do this an more... ;) It's an
> alternative index page and gives you the option of just displaying the
> titles and no paragraph or vice versa, as well as displaying stories for
> each topic in separate parts of the page.
>
> (shameless plug - I wrote it when I worked for OSDN for the Foundries and
> it's now used on the dev channels website). I know that there have been
> even further enhancements to it by krow and the rest of the team.

Speaking of the page plugin. Has anyone been able to get to use page.pl as the 
script for the index section of your site with current cvs?

I tried - I can routinely get it to work under a section of a site. But just 
not the index. No errors or anything that I could find. Looking at the src 
the templates being called are still name;index;default.

Any suggestions?

Thanks, 
 Shane

On Wed, 2003-04-02 at 15:58, shane wrote:
> Speaking of the page plugin. Has anyone been able to get to use page.pl as the 
> script for the index section of your site with current cvs?
devchannel.org and a few other OSDN sites do.

> I tried - I can routinely get it to work under a section of a site. But just 
> not the index. No errors or anything that I could find. Looking at the src 
> the templates being called are still name;index;default.
name;page;default

The name of the page is "page", aka page.pl. Make sure you also update
the section information so that the default handler is page.pl.

	-Brian
-- 
_______________________________________________________
Brian "Krow" Aker, brian@... 
Slashdot Senior Developer
Seattle, Washington
http://krow.net/
http://askbrian.org/
_______________________________________________________
You can't grep a dead tree.

On Wednesday 02 April 2003 18:59, Brian Aker wrote:
> On Wed, 2003-04-02 at 15:58, shane wrote:
> > Speaking of the page plugin. Has anyone been able to get to use page.pl
> > as the script for the index section of your site with current cvs?
>
> devchannel.org and a few other OSDN sites do.
>
> > I tried - I can routinely get it to work under a section of a site. But
> > just not the index. No errors or anything that I could find. Looking at
> > the src the templates being called are still name;index;default.
>
> name;page;default
>
> The name of the page is "page", aka page.pl. Make sure you also update
> the section information so that the default handler is page.pl.

Yes, I realize that the name of the template being called *should* be 
name;page;defaut when the default handler is changed to page.pl.

But it hasn't been.  After the switch to page.pl , when I restart apache, and 
then hit the site, and look at the html src, it's still 

start template: ID 131, fancybox;misc;default 

which is exactly what I was referring to in the initial message to the 
listserv (sorry, should've been more clear)

mysql> select * from sections where section='index';
+----+---------+----------+-------+------+-------+-----+----------+-----------+
| id | section | artcount | title | qid  | issue | url | hostname | 
cookiedomain | index_handler | writestatus | type      | rewrite | 
last_update    | defaultdisplaystatus | defaulttopic | defaultsection | 
defaultsubsection | defaultcommentstatus |
+----+---------+----------+-------+------+-------+-----+----------+--+
| 15 | index   |       15 | Index | NULL |     0 |     |          |              
| page.pl       | dirty       | collected |    3600 | 20030403004427 |                    
0 |            1 | articles       |                 0 | enabled              
|

Any suggestions?

Thanks,
 Shane

On Wed, 2003-04-02 at 16:48, shane wrote:
> Yes, I realize that the name of the template being called *should* be 
> name;page;defaut when the default handler is changed to page.pl.
> 
> But it hasn't been.  After the switch to page.pl , when I restart apache, and 
> then hit the site, and look at the html src, it's still 
> 
> start template: ID 131, fancybox;misc;default 
Right, the way it works is this:
1) First check to see if a specific page name exists.
2) Then check using "misc" for the page name.
So at this point it is defaulting to misc.


> mysql> select * from sections where section='index';
> +----+---------+----------+-------+------+-------+-----+----------+-----------+
> | id | section | artcount | title | qid  | issue | url | hostname | 
> cookiedomain | index_handler | writestatus | type      | rewrite | 
> last_update    | defaultdisplaystatus | defaulttopic | defaultsection | 
> defaultsubsection | defaultcommentstatus |
> +----+---------+----------+-------+------+-------+-----+----------+--+
> | 15 | index   |       15 | Index | NULL |     0 |     |          |              
> | page.pl       | dirty       | collected |    3600 | 20030403004427 |                    
> 0 |            1 | articles       |                 0 | enabled              
> |
> 
> Any suggestions?
That looks good, I still suspect that its a page naming issue. 

	-Brian
-- 
_______________________________________________________
Brian "Krow" Aker, brian@... 
Slashdot Senior Developer
Seattle, Washington
http://krow.net/
http://askbrian.org/
_______________________________________________________
You can't grep a dead tree.

On Wednesday 02 April 2003 19:36, Brian Aker wrote:
> On Wed, 2003-04-02 at 16:48, shane wrote:
> > Yes, I realize that the name of the template being called *should* be
> > name;page;defaut when the default handler is changed to page.pl.
> >
> > But it hasn't been.  After the switch to page.pl , when I restart apache,
> > and then hit the site, and look at the html src, it's still
> >
> > start template: ID 131, fancybox;misc;default
>
> Right, the way it works is this:
> 1) First check to see if a specific page name exists.
> 2) Then check using "misc" for the page name.
> So at this point it is defaulting to misc.
>
>[...sql output ripped]
> >
> > Any suggestions?
>
> That looks good, I still suspect that its a page naming issue.

Page naming issue? I guess I don't understand. Is it a bug? Is it something 
that I've configured wrong or not config'd?

Because it's still calling all the templates index;index;default , etc. It 
doesn't seem like it's ever calling page.pl. It seem like it's ignoring the 
indexhandler when currentsection eq 'index'. Though, for any section that 
I've created, that's other then 'index', it'll work just fine and page.pl 
will be run.

Thanks,
 Shane

On Wed, 2003-04-02 at 17:06, shane wrote:
> Page naming issue? I guess I don't understand. Is it a bug? Is it something 
> that I've configured wrong or not config'd?
I suspect its template names.

> Because it's still calling all the templates index;index;default , etc. It 
> doesn't seem like it's ever calling page.pl. It seem like it's ignoring the 
> indexhandler when currentsection eq 'index'. Though, for any section that 
> I've created, that's other then 'index', it'll work just fine and page.pl 
> will be run.
Does http://sitename.com/page.pl  work?

And what sort of message is freshenup giving when it goes over the
section (just set the section and restart slashd to make sure it runs).

	-Brian
-- 
_______________________________________________________
Brian "Krow" Aker, brian@... 
Slashdot Senior Developer
Seattle, Washington
http://krow.net/
http://askbrian.org/
_______________________________________________________
You can't grep a dead tree.

On Wednesday 02 April 2003 20:04, Brian Aker wrote:
> On Wed, 2003-04-02 at 17:06, shane wrote:
> > Page naming issue? I guess I don't understand. Is it a bug? Is it
> > something that I've configured wrong or not config'd?
>
> I suspect its template names.
>
> > Because it's still calling all the templates index;index;default , etc.
> > It doesn't seem like it's ever calling page.pl. It seem like it's
> > ignoring the indexhandler when currentsection eq 'index'. Though, for any
> > section that I've created, that's other then 'index', it'll work just
> > fine and page.pl will be run.
>
> Does http://sitename.com/page.pl  work?

yes.

http://www.lottadot.com/page.pl

> And what sort of message is freshenup giving when it goes over the
> section (just set the section and restart slashd to make sure it runs).



tail -100
Subroutine _make_cchp_file redefined at 
/usr/local/slash/site/www.lottadot.com/t                                   
asks/freshenup.pl line 182.
Subroutine _read_and_unlink_cchp_file redefined at 
/usr/local/slash/site/www.lot                                   
tadot.com/tasks/freshenup.pl line 206.
Subroutine galLog redefined at 
/usr/local/slash/site/www.lottadot.com/tasks/last                                   
logins_task.pl line 72.
"my" variable $backupdb masks earlier declaration in same scope at 
/usr/local/sl                                   
ash/site/www.lottadot.com/tasks/relocount_run_count.pl line 20.
Thu Apr  3 02:02:17 2003 processed 
/usr/local/slash/site/www.lottadot.com/tasks;                                    
28 successful (adminmail.pl calleria_task.pl clean_blobs.pl daily.pl 
daily_arch                                   ive.pl daily_forget.pl expire.pl 
flush_formkeys.pl freshenup.pl galleria_task.pl                                    
lastcommentstask.pl lastlogins_task.pl message_delete.pl message_delivery.pl 
ne                                   w_headfoot.pl new_motd.pl 
open_backend.pl p2f_cheesy.pl p2f_hof_topics.pl refres                                   
h_authors_cache.pl refresh_uncommon.pl relocount_run_count.pl rss_submit.pl 
run_                                   moderatord.pl run_portald.pl 
set_recent_topics.pl spamarmor.pl zoo_run_people_lo                                   
g.pl); 0 failed
Thu Apr  3 02:02:18 2003 first task will be freshenup.pl in -1 secs
Thu Apr  3 02:02:18 2003 freshenup.pl forked; new_headfoot.pl 1s late
Thu Apr  3 02:02:20 2003 [freshenup.pl] begin (26035)

that didn't show much. so i ran it by hand:

[root@... logs]# runtask -u lottadot freshenup.pl
Thu Apr  3 02:02:44 2003 runtask freshenup.pl begin
Thu Apr  3 02:02:48 2003 runtask index.pl virtual_user=lottadot ssi=yes 
section='index' bytes=69359
Thu Apr  3 02:02:48 2003 runtask freshenup.pl end:  (ran in 4.42s)

and got a boatload of errrors. Some of them:

Thu Apr  3 02:03:37 2003 [freshenup.pl] index.pl virtual_user=lottadot ssi=yes 
section='index' bytes=69359
Thu Apr  3 02:03:42 2003 [freshenup.pl] index.pl virtual_user=lottadot ssi=yes 
section='articles' bytes=6444
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31,
 main line 39
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31, main lin
e 39
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31,
 main line 39
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31, main lin
e 39
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31,
 main line 39
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31, main lin
e 39
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display.pm:204:Failed 
templat
e lookup on 'storylink;page[misc];default[default]', callers: Slash::Page line 
309, Slash::Page line 179, Slash::Di
splay line 233
Which was called 
by:Slash::Page:/usr/local/lib/perl5/site_perl/5.6.1/Slash/Page.pm:309:Failed 
template lookup on 's
torylink;page[misc];default[default]', callers: Slash::Page line 309, 
Slash::Page line 179, Slash::Display line 233
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'storylink;page[misc];default[default]', 
callers: Slash::Display line 233, Slash::Pag
e line 309, Slash::Page line 179
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'storylink;page[misc];default[default]', callers: 
Slash::Display line 233, Slash::Page line 30
9, Slash::Page line 179
Error in 
library:Slash::Display::Provider:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Slash/Display/Provider.pm
:81:Failed template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31,
 main line 39
Which was called 
by:Template::Context:/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Template/Context.pm:133:Faile
d template lookup on 'topicbar;page[misc];index[default]', callers: 
Slash::Display line 233, main line 31, main lin                        e 39
Thu Apr  3 02:03:48 2003 [freshenup.pl] page.pl virtual_user=lottadot ssi=yes 
section='index' bytes=60858

mysql> select tpid,name from templates where page='page';
+------+----------------+
| tpid | name           |
+------+----------------+
|  322 | index          |
|  356 | data           |
|  357 | storyTitleOnly |
+------+----------------+
3 rows in set (0.01 sec)

So something's defintely going on w/ slashd/freshenup...

here's the links that should show the page plugin as index:

<URL: http://www.lottadot.com/index.shtml >

<URL: http://www.lottadot.com/ > 

and if you were to login:

<URL: http://www.lottadot.com/index.pl >

<URL: http://www.lottadot.com/page.pl >

Thanks,
 Shane