Menu
▾
▴
slashcode-development — This list is for development of slashcode, no install questions please.
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(29) |
Dec
(101) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(90) |
Feb
(101) |
Mar
(173) |
Apr
(141) |
May
(38) |
Jun
(28) |
Jul
(14) |
Aug
(7) |
Sep
(3) |
Oct
(7) |
Nov
(15) |
Dec
(9) |
| 2002 |
Jan
(2) |
Feb
(5) |
Mar
(11) |
Apr
|
May
(4) |
Jun
(6) |
Jul
(7) |
Aug
(12) |
Sep
(8) |
Oct
(1) |
Nov
(4) |
Dec
(7) |
| 2003 |
Jan
(7) |
Feb
(1) |
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
(19) |
Aug
(4) |
Sep
(8) |
Oct
(30) |
Nov
(25) |
Dec
(22) |
| 2004 |
Jan
(6) |
Feb
(12) |
Mar
|
Apr
(2) |
May
|
Jun
(10) |
Jul
(18) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2005 |
Jan
(8) |
Feb
(4) |
Mar
(6) |
Apr
(5) |
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
|
| 2006 |
Jan
(9) |
Feb
(6) |
Mar
(11) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Chris J. <jo...@nm...> - 2003-11-04 12:15:42
|
On Mon, 3 Nov 2003, Shane wrote:
> I *believe* a while back I submitted a bug report because deleting
> topics wasn't working.
> You may want to look at the SF bugs list and see what happened with it.
>
> Shane
>
>
Based on my poking in the mysql database it looks like add and
delete topics is working fine.
I'm considering instrumenting admin.pl to see what's going on at
this point.
--------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |God stand between you and harm in all the empty
Charlestown, MA., 02129 USA |places where you must walk. old Egyptian blessing
--------------------------------------------------------------------------------
|
|
From: Shane <sh...@lo...> - 2003-11-03 19:48:10
|
I *believe* a while back I submitted a bug report because deleting topics wasn't working. You may want to look at the SF bugs list and see what happened with it. Shane On Nov 3, 2003, at 1:05 PM, Chris Johnson wrote: > On Mon, 3 Nov 2003, Chris Johnson wrote: > >> I did find out that I can delete and recreate the topic. Hm, is >> there are particular table that I should look in to find the relation >> between topics and sections? >> >> > > Found it, section_topics. And there is a proper map between the > section and the topic. I'm confused. This used to work. > > ----------------------------------------------------------------------- > -------- > Chris Johnson |Internet: jo...@nm... > Systems Administrator |Web: > http://www.nmr.mgh.harvard.edu/~johnson > NMR Center |Voice: 617.726.0949 > Mass. General Hospital |FAX: 617.726.7422 > 149 (2301) 13th Street |Fifty percent of all doctors graduated in > the > Charlestown, MA., 02129 USA |lower half of the class. Observation > ----------------------------------------------------------------------- > -------- > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development > |
|
From: Chris J. <jo...@nm...> - 2003-11-03 19:05:57
|
On Mon, 3 Nov 2003, Chris Johnson wrote:
> I did find out that I can delete and recreate the topic. Hm, is
> there are particular table that I should look in to find the relation
> between topics and sections?
>
>
Found it, section_topics. And there is a proper map between the
section and the topic. I'm confused. This used to work.
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |Fifty percent of all doctors graduated in the
Charlestown, MA., 02129 USA |lower half of the class. Observation
-------------------------------------------------------------------------------
|
|
From: Chris J. <jo...@nm...> - 2003-11-03 18:52:56
|
I did find out that I can delete and recreate the topic. Hm, is there are particular table that I should look in to find the relation between topics and sections? ------------------------------------------------------------------------------- Chris Johnson |Internet: jo...@nm... Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson NMR Center |Voice: 617.726.0949 Mass. General Hospital |FAX: 617.726.7422 149 (2301) 13th Street |Life stinks. If you're very lucky, sometimes Charlestown, MA., 02129 USA |it stinks a little less. Me ------------------------------------------------------------------------------- |
|
From: Chris J. <jo...@nm...> - 2003-11-03 17:40:47
|
On Mon, 3 Nov 2003, Clifton Wood wrote:
> On Monday 03 November 2003 07:09, Chris Johnson wrote:
>
> > Ok, restarted apache which is set up to not do caching but
> > may be doing a little in memory. Also made sure slashd was
> > running but restarted it anyway. No joy. The New article page
> > still does not see the new topic I added, which is in the topics
> > table in the database. It does show the section I added.
> > Something is still weird. Any suggestions?
>
> For your new topic, are the proper sections checked on the
> right?
>
> Topics can be unique to sections, so if you've created a topic
> and it doesn't belong to one of the sections on the main page,
> then it WON'T show. This is by design. As a test, make sure
> all sections on the right are checked, and then see if you can
> see the topic.
>
> - Cliff
>
>
The aproriate sections are checked which means the database knows
about them. I know about unsectioned topics.
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |"Reality is merely an illusion, albeit a very
Charlestown, MA., 02129 USA | persistant one." Albert Einstein
-------------------------------------------------------------------------------
|
|
From: Clifton W. <cl...@sl...> - 2003-11-03 17:09:56
|
On Monday 03 November 2003 07:09, Chris Johnson wrote: > Ok, restarted apache which is set up to not do caching but > may be doing a little in memory. Also made sure slashd was > running but restarted it anyway. No joy. The New article page > still does not see the new topic I added, which is in the topics > table in the database. It does show the section I added. > Something is still weird. Any suggestions? For your new topic, are the proper sections checked on the right? Topics can be unique to sections, so if you've created a topic and it doesn't belong to one of the sections on the main page, then it WON'T show. This is by design. As a test, make sure all sections on the right are checked, and then see if you can see the topic. - Cliff |
|
From: Chris J. <jo...@nm...> - 2003-11-03 12:10:05
|
On Wed, 29 Oct 2003, Cliff wrote:
> On Tuesday 28 October 2003 12:54, Chris Johnson wrote:
> > On Fri, 24 Oct 2003, Cliff wrote:
> > > OK, so assuming you haven't touched anything, it looks like
> > > templates have spontaneously lept out of your database
> > > because that's what those errors mean.
> > >
> > > See if you can find the following templates and reload
> > > them onto your site using template-tool:
> > >
> > > sections_summary;misc;default
> > >
> > > See if that at least makes things better.
> >
> > The sections_* templates are supposed to be generated by a
> > task I put in almost a year ago. Very strange. I've got the
> > tassk running again. And the errors are gone from the log. No
> > clue how it happened.
> >
> > On another note, are there delays in updating templates or
> > delays in showing them? Should they be distributed around the
> > entire database immediately? I'm seeing differences in sections
> > blocks where there shouldn't be any after my task runs. And the
> > task is running without errors now. I have it writing it's own
> > log and it is finding what it's supposed to.
>
> This depends on the settings in your 'vars' table. There are caching
> variables in there that determine how long webservers wait until
> they refresh their caches from the database. The easy way to fix
> this is to restart your apache servers, as this then makes sure you
> are using the latest data from cache.
>
> This does NOT affect the tasks, however, as the tasks make their
> own connection to the database. However, if slashd isn't running,
> then the tasks don't run either. There have been problems with
> slashd bombing out when the database hiccups, and these
> can be minimized by using "/etc/init.d/slashd keepalive" at
> periodic intervals.
>
> - Cliff
>
Ok, restarted apache which is set up to not do caching but may be
doing a little in memory. Also made sure slashd was running but
restarted it anyway. No joy. The New article page still does not see
the new topic I added, which is in the topics table in the database.
It does show the section I added. Something is still weird. Any
suggestions?
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |Survival, all by it self, isn't worth it.
Charlestown, MA., 02129 USA | Me
-------------------------------------------------------------------------------
|
|
From: Shane <sh...@lo...> - 2003-10-31 01:34:54
|
restart apache, ie apachetcl stop && sleep 10 && apachectl start that'll do it. anytime you make a major change (ie sections/topics/vars) you either need to stop/start apache, or wait for all the apache processes to die so they'll load in the fresh data. On Oct 30, 2003, at 12:17 PM, Chris Johnson wrote: > Anybody have a tutorial of the slash caching? I reinstalled > slash and recreated my task (which works by the way). I just created > a section which showed up immediately. The I created a topic that > didn't. Itt's in he Topics page but doesn't show when I dd a new > story. I'm confused. I know it's there because it's in the mysql > topics table. I've run into problems like his before and believe it > to have something to do with caching, which I'd like very much to > either turn off or shorten drasticly, unless someone has a better > idea. > > Thank much. > > ----------------------------------------------------------------------- > -------- > Chris Johnson |Internet: jo...@nm... > Systems Administrator |Web: > http://www.nmr.mgh.harvard.edu/~johnson > NMR Center |Voice: 617.726.0949 > Mass. General Hospital |FAX: 617.726.7422 > 149 (2301) 13th Street |"The two most abundant things in the > Universe > Charlestown, MA., 02129 USA | are hydrogen and stupidity." Harlan > Ellison > ----------------------------------------------------------------------- > -------- > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development > |
|
From: Chris J. <jo...@nm...> - 2003-10-30 18:17:47
|
Anybody have a tutorial of the slash caching? I reinstalled
slash and recreated my task (which works by the way). I just created
a section which showed up immediately. The I created a topic that
didn't. Itt's in he Topics page but doesn't show when I dd a new
story. I'm confused. I know it's there because it's in the mysql
topics table. I've run into problems like his before and believe it
to have something to do with caching, which I'd like very much to
either turn off or shorten drasticly, unless someone has a better
idea.
Thank much.
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |"The two most abundant things in the Universe
Charlestown, MA., 02129 USA | are hydrogen and stupidity." Harlan Ellison
-------------------------------------------------------------------------------
|
|
From: Chris J. <jo...@nm...> - 2003-10-28 17:55:27
|
On Fri, 24 Oct 2003, Cliff wrote:
> OK, so assuming you haven't touched anything, it looks like
> templates have spontaneously lept out of your database
> because that's what those errors mean.
>
> See if you can find the following templates and reload
> them onto your site using template-tool:
>
> sections_summary;misc;default
>
> See if that at least makes things better.
>
> - Cliff
>
>
The sections_* templates are supposed to be generated by a task I
put in almost a year ago. Very strange. I've got the tassk running
again. And the errors are gone from the log. No clue how it
happened.
On another note, are there delays in updating templates or delays
in showing them? Should they be distributed around the entire
database immediately? I'm seeing differences in sections blocks where
there shouldn't be any after my task runs. And the task is running
without errors now. I have it writing it's own log and it is finding
what it's supposed to.
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |I'm continually amazed by mankind's seemingly
Charlestown, MA., 02129 USA |infinite capacity for stupidity. Me
-------------------------------------------------------------------------------
|
|
From: Clifton W. <cl...@sl...> - 2003-10-28 17:50:24
|
On Wednesday 22 October 2003 20:19, Clifton Wood wrote: > Here's the initial patch. It's been a while since I've done this > so I hope I have it all in the first go. Of course, that didn't work. So here is round 2. This patch is against CVS, so if you've already installed this, you'll have to go back to the CVS code and then repatch. Sorry about that, but I didn't think to preserve the original files. - Cliff New patch is attached. If this patch appears more than once, I apologize. Kmail is acting wonky. |
|
From: Chris J. <jo...@nm...> - 2003-10-25 16:20:29
|
On Thu, 23 Oct 2003, Cliff wrote:
> On Thursday 23 October 2003 11:29, shane wrote:
> > On Wednesday 22 October 2003 20:19, Clifton Wood wrote:
> >
> > Installed the patch - thanks for the log mod - getting this:
> >
> > [Thu Oct 23 15:26:16 2003] [error] Can't use an undefined value as
> > an ARRAY reference at
> > /usr/local/lib/perl5/site_perl/5.8.0/i686-linux/Slash/DB/Utility/D
> >ebug.pm line 202.
> >
> > any suggestions? here's what's in the site's .conf:
> >
> > PerlModule Slash::DB::Utility::Debug
> > SlashDebugSQL "index.pl"
> >
> > SlashDebugSQLLog "/tmp/log"
> >
> > Shane
>
> Weird. I'm not getting that, but I've added more code to that routine
> to hopefully cut down on the fatal errors that can occur. I'll
> send another patch to the list when I've done some more testing.
>
> Thanks for trying it out.
>
> - Cliff
>
>
Funny you should mention that. Remember I'm new here and there
are lots of logs. The only mod I made was to install a task but that
was last January and it was working. However I did find this after
plowing through the slashd.log and it seems to have just started.
Fri Oct 24 00:03:02 2003 new_headfoot.pl begin
Error in library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Slash/D
isplay/Provider.pm:81:Failed template lookup on 'sections_summary;misc[misc];default[defaul
t]', callers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Which was called by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Co
ntext.pm:133:Failed template lookup on 'sections_summary;misc[misc];default[default]', call
ers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Error in library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Slash/D
isplay/Provider.pm:81:Failed template lookup on 'sections_summary;misc[misc];articles[defau
lt]', callers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Which was called by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Co
ntext.pm:133:Failed template lookup on 'sections_summary;misc[misc];articles[default]', cal
lers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Error in library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Slash/D
isplay/Provider.pm:81:Failed template lookup on 'sections_summary;misc[misc];ts1[default]',
callers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Which was called by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Co
ntext.pm:133:Failed template lookup on 'sections_summary;misc[misc];ts1[default]', callers:
Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Error in library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Slash/D
isplay/Provider.pm:81:Failed template lookup on 'sections_summary;misc[misc];features[defau
lt]', callers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Which was called by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Co
ntext.pm:133:Failed template lookup on 'sections_summary;misc[misc];features[default]', cal
lers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Error in library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Slash/D
isplay/Provider.pm:81:Failed template lookup on 'sections_summary;misc[misc];Optical[defaul
t]', callers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Which was called by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Co
ntext.pm:133:Failed template lookup on 'sections_summary;misc[misc];Optical[default]', call
ers: Slash::Display line 228, Slash::Utility::Anchor line 159, main line 42
Fri Oct 24 00:03:02 2003 new_headfoot.pl end (0.16s; freshenup.pl in 58s)
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |Life n, a disease with 100% mortality.
Charlestown, MA., 02129 USA | Me
-------------------------------------------------------------------------------
|
|
From: Cliff <cl...@sl...> - 2003-10-24 18:57:34
|
OK, so assuming you haven't touched anything, it looks like templates have spontaneously lept out of your database because that's what those errors mean. See if you can find the following templates and reload them onto your site using template-tool: sections_summary;misc;default See if that at least makes things better. - Cliff On Friday 24 October 2003 13:28, Chris Johnson wrote: > Funny you should mention that. Remember I'm new here and > there are lots of logs. The only mod I made was to install a task > but that was last January and it was working. However I did find > this after plowing through the slashd.log and it seems to have > just started. > > > Fri Oct 24 00:03:02 2003 new_headfoot.pl begin > Error in > library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i3 >86-linux/Slash/D isplay/Provider.pm:81:Failed template lookup on > 'sections_summary;misc[misc];default[defaul t]', callers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Which was called > by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Tem >plate/Co ntext.pm:133:Failed template lookup on > 'sections_summary;misc[misc];default[default]', call ers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Error in > library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i3 >86-linux/Slash/D isplay/Provider.pm:81:Failed template lookup on > 'sections_summary;misc[misc];articles[defau lt]', callers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Which was called > by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Tem >plate/Co ntext.pm:133:Failed template lookup on > 'sections_summary;misc[misc];articles[default]', cal lers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Error in > library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i3 >86-linux/Slash/D isplay/Provider.pm:81:Failed template lookup on > 'sections_summary;misc[misc];ts1[default]', callers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Which was called > by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Tem >plate/Co ntext.pm:133:Failed template lookup on > 'sections_summary;misc[misc];ts1[default]', callers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Error in > library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i3 >86-linux/Slash/D isplay/Provider.pm:81:Failed template lookup on > 'sections_summary;misc[misc];features[defau lt]', callers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Which was called > by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Tem >plate/Co ntext.pm:133:Failed template lookup on > 'sections_summary;misc[misc];features[default]', cal lers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Error in > library:Slash::Display::Provider:/usr/lib/perl5/site_perl/5.6.1/i3 >86-linux/Slash/D isplay/Provider.pm:81:Failed template lookup on > 'sections_summary;misc[misc];Optical[defaul t]', callers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Which was called > by:Template::Context:/usr/lib/perl5/site_perl/5.6.1/i386-linux/Tem >plate/Co ntext.pm:133:Failed template lookup on > 'sections_summary;misc[misc];Optical[default]', call ers: > Slash::Display line 228, Slash::Utility::Anchor line 159, main > line 42 Fri Oct 24 00:03:02 2003 new_headfoot.pl end (0.16s; > freshenup.pl in 58s) > > > ------------------------------------------------------------------ >------------- Chris Johnson |Internet: > jo...@nm... Systems Administrator |Web: > http://www.nmr.mgh.harvard.edu/~johnson NMR Center > |Voice: 617.726.0949 > Mass. General Hospital |FAX: 617.726.7422 > 149 (2301) 13th Street |Life n, a disease with 100% > mortality. Charlestown, MA., 02129 USA | Me > ------------------------------------------------------------------ >------------- |
|
From: Cliff <cl...@sl...> - 2003-10-24 15:45:37
|
On Thursday 23 October 2003 11:29, shane wrote: > On Wednesday 22 October 2003 20:19, Clifton Wood wrote: > > Installed the patch - thanks for the log mod - getting this: > > [Thu Oct 23 15:26:16 2003] [error] Can't use an undefined value as > an ARRAY reference at > /usr/local/lib/perl5/site_perl/5.8.0/i686-linux/Slash/DB/Utility/D >ebug.pm line 202. > > any suggestions? here's what's in the site's .conf: > > PerlModule Slash::DB::Utility::Debug > SlashDebugSQL "index.pl" > > SlashDebugSQLLog "/tmp/log" > > Shane Weird. I'm not getting that, but I've added more code to that routine to hopefully cut down on the fatal errors that can occur. I'll send another patch to the list when I've done some more testing. Thanks for trying it out. - Cliff |
|
From: Chris J. <jo...@nm...> - 2003-10-24 14:15:40
|
Hi,
Fairly new to slash. Been running 2.2.6 for a year, haven't done
much with it, what to start. Did modify a task for it. Used to work.
Yesterday I defined a new section and associated two topics with
it. Or so I thought.
Started poking in the mysql database today. The sections table
has the section I defined. The topics table does not have the topics.
I posted an article which was accepted but the stories table knows
nothing about it.
Any clues here?
I've also noted that when I added my task there seemd the be huge
delay on information propogated around the system, like on the order of
a day.
Very odd behavior. Help appreciated.
-------------------------------------------------------------------------------
Chris Johnson |Internet: jo...@nm...
Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson
NMR Center |Voice: 617.726.0949
Mass. General Hospital |FAX: 617.726.7422
149 (2301) 13th Street |Life, a bad idea who's time is past.
Charlestown, MA., 02129 USA | Me
-------------------------------------------------------------------------------
|
|
From: Clifton W. <cl...@sl...> - 2003-10-23 03:01:38
|
Here's the initial patch. It's been a while since I've done this so I
hope I have it all in the first go.
This should be patchable against the latest Slash version in CVS
although it *may* (no guarantees) work for earlier T_ and R_
tags.
To use, do the following. In your conf files, add:
PerlModule Slash::DB::Utility::Debug
SlashDebugSQL "<name of packages or files>"
So:
PerlModule Slash::DB::Utility::Debug
SlashDebugSQL "Slash::Search admin.pl"
Should dump all SQL executed by the Search plugin or the Admin
script.
At shane's request, I've added the following directive:
SlashDebugSQLLog "/path/to/sql/log"
Which does just about what you'd expect. If the log
isn't specified, SQL is dumped to your error logs.
Enjoy and let me know if any bugs unexpectedly
slap you around.
Patch is attached.
- Cliff
PS - Please note that the PerlModule and SlashDebug* directives
only need to appear once in your conf files.
|
|
From: Ralph D. <ra...@ma...> - 2003-10-22 03:40:53
|
>Another question is how many topics you are planning on >having. Cliff, I need around fifty topics in the early stages, I think. Obviously, distinguishable colors run out at some point, so there are diminishing returns in the purely visual realm. If the number of topics grows beyond a hundred or so, the distinguisable colors start repeating. But I would really like to be able to handle even more topics... and I must admit I'm unclear how that number could affect the performance, given that database access must be nearly constant up to a much larger number than that, no? (Obviously I don't know enough to know!) >...I honestly see a real easy way to do what is >necessary, but I'm not sure how well it would affect performance. With sections or with topics? To me, topics would be more logical, and I also have a very good use for sections that is (as the book suggests) orthogonal to the topics. >If I can code something up that looks like it will work, during my >spare time, I'll send what I have out to the list. Thank you. That's very generous, even to consider doing so. In case you don't get that far, please give me a preview of your concept. I'm furiously studying the template documentation, and I guess I'll have to bite the bullet and become a real Perl person, too. Sigh... But it's all worth it, I think, to be able to use this impressive system. And if I have to (mildly) fork my version by adding a field or another table, I'm really not all that concerned right now. Based on past experience, I'll probably want to "start over" at some point down the road anyway (if this whole thing works out) and at that time I could incorporate the latest SlashCode revs. Regards, Ralph |
|
From: Cliff <cl...@sl...> - 2003-10-20 20:11:28
|
On Monday 20 October 2003 07:17, shane wrote:
> > The key point - and I apologize for not making this clear before
> > - is that I need to mix colors on the main page. Each Story must
> > be assigned to a grouping which has its own color.
>
> Are the colors random? Do they need to always be the same given
> topic __n___? Are they shown by story # {1..n}? Need more info
> here.
>
> > What would it take to mix colors on the main page, with
> > different story colors right there, depending on each story's
> > Section - or Topic - or something?
>
> That's the question - what do you want it to depend on? That
> affects what/where you'd have to change in the src and/or
> templates.
Another question is how many topics you are planning on
having. To be honest, I don't think using sections
to do this would be the right way to go, since you'll have
to pull the section colors for *each story* for any container
sections you'll be displaying, not to mention that the
section colors are loaded into the $user object auto-magically
by Slash, so to use sections, you'd have to fight the existing
code to make it work (means more chance for unexpected
bugs).
Sections are another thing that I'm not so sure people have
a good grasp on yet. Sections recently changed around to formalize
some of those features that had rapidly evolved in Slash. A section
can be a 'container' type or it can be a "collection" (type ==
'collected'). The index page is an example of a "collection"
section, as it "collects" stories from other specified secitons.
'container' types are sections like Slashdot's YRO, and Ask Slashdot.
They only "contain" stories of a specific genre.
So your color changes really need only apply to the "collected"
type of section. I honestly see a real easy way to do what is
necessary, but I'm not sure how well it would affect performance.
If I can code something up that looks like it will work, during my
spare time, I'll send what I have out to the list.
- Cliff
|
|
From: Cliff <cl...@sl...> - 2003-10-20 18:51:52
|
On Monday 20 October 2003 07:01, shane wrote:
> There's only one thing I think I'd change - Make it dump to it's
> own logfile, something like
> /{installdir}/sites/sitename/logs/sql.log. But that's debateable
> since I've not seen what you've done, obviously.
Good idea, but that would take a lot more work. I might try and
fit it in while I formalize what I have. I'll send to a patch
sometime, today.
Basically, I'm just performing a whole bunch of checks and
printing to STDERR. I guess that could be diverted to a file,
easily enough.
Let me give it some thought.
- Cliff
|
|
From: Ralph D. <ra...@ma...> - 2003-10-20 17:28:48
|
Shane, I want each story on the index page to be colored by either its Topic (best solution) or by its Section (okay solution). The colors are not supposed to be random or anything like that. It's like having topic icons. I just want topic colors instead. Or else section colors, but on the index page. Regards, Ralph |
|
From: shane <sh...@lo...> - 2003-10-20 11:33:41
|
On Saturday 18 October 2003 21:57, Ralph Dratman wrote:
> Thanks to Cliff and Shane for comments about the color changes by Topic.
>
> Unfortunately, I don't have any funding for a plugin at the moment.
> Maybe later, if things work out with the site.
>
> As I think about this color requirement, I realize that I may have
> been wrong to assume that I need Topic colors. Although Topics seem
> logical for what I have in mind, I guess I should consider using
> Sections since they already can have colors associated with them.
>
> Why do Section colors currently show up only when one is actually
> browsing within a particular section, rather than when sections are
> mixed into the main area?
They're not mixed.
When you look at the index page of most slash-based websites, it shows stories
and slashboxes. The stories it shows are the latested N (depending on
users_index.maxstories), and depending on whether or not the latest stories
are marked as 'show in section only'.
So when the index page is generated, that is actually generating the page for
'section=index'.
When you click on a story that's in a 'stories' section, then you're viewing
any templates that are marked as section=stories, and that's where you get
your cosmetic changes.
> The key point - and I apologize for not making this clear before - is
> that I need to mix colors on the main page. Each Story must be
> assigned to a grouping which has its own color.
Are the colors random? Do they need to always be the same given topic __n___?
Are they shown by story # {1..n}? Need more info here.
> What would it take to mix colors on the main page, with different
> story colors right there, depending on each story's Section - or
> Topic - or something?
That's the question - what do you want it to depend on? That affects
what/where you'd have to change in the src and/or templates.
Shane
|
|
From: shane <sh...@lo...> - 2003-10-20 11:07:40
|
On Saturday 18 October 2003 07:18, Cliff wrote:
> Recently, I've been working on a more formal way of debugging
> the SQL associated with Slash sites that I happen to run. This
> came from me being sick and tired of having to navigate error
> logs after adding a "print $sql" to Slash::DB::Utility::prepare and
> trying to find the SPECIFIC SQL statement I wanted in the
> logs.
>
> Sooo... I hacked Slash::Apache and Slash::DB::Utility
> to provide a new Apache configuration directive for Slash:
>
> SlashDebugSQL "<space separated list of packages or scripts>"
>
> So. If I was looking for SQL associated for Search and for admin.pl,
> I'd add the following to my Apache conf:
>
> SlashDebugSQL "Slash::Search admin.pl"
>
> And ONLY the SQL from those files would be sent to the error
> logs.
nice.
> Note, that this is NOT designed for use on production servers
> (please!), this is for testing machines only, and uses a custom
> version of DB/Utility.pm to do its magic. I have yet to figure out
> how to roll this into Slash so that it is as unnoticeable as possible
> in a production environment. It's one of the reasons I haven't
> made a formal patch yet. If anyone has any ideas as to how I
> can alias Slash::DB::Utility::_prepare to one of two different subs
> depending on a boolean conditional, please let me know. I have
> ideas, I'm just not sure how well they work in practice and am still
> working at it.
>
> So would others be interested in me continuing work on formalizing
> this?
Yes
>Or would care for their own personal version of my changes?
Yes :) Please send me a patch.
There's only one thing I think I'd change - Make it dump to it's own logfile,
something like /{installdir}/sites/sitename/logs/sql.log. But that's
debateable since I've not seen what you've done, obviously.
Shane
|
|
From: Ralph D. <ra...@ma...> - 2003-10-19 09:04:30
|
Thanks to Cliff and Shane for comments about the color changes by Topic. Unfortunately, I don't have any funding for a plugin at the moment. Maybe later, if things work out with the site. As I think about this color requirement, I realize that I may have been wrong to assume that I need Topic colors. Although Topics seem logical for what I have in mind, I guess I should consider using Sections since they already can have colors associated with them. Why do Section colors currently show up only when one is actually browsing within a particular section, rather than when sections are mixed into the main area? The key point - and I apologize for not making this clear before - is that I need to mix colors on the main page. Each Story must be assigned to a grouping which has its own color. What would it take to mix colors on the main page, with different story colors right there, depending on each story's Section - or Topic - or something? Regards, Ralph |
|
From: Cliff <cl...@sl...> - 2003-10-18 15:46:27
|
On Saturday 18 October 2003 07:15, shane wrote: > On Saturday 18 October 2003 00:46, Ralph Dratman wrote: > >[...] > >I would like to associate a > > COLOR with each TOPIC. I want this color to be used for the > > title bar of each story for that topic. > > > > Leaving aside the various implementation details, the obvious > > way to accomplish this is to add a color field to the topic > > table. > > I think that's how I'd do it to. However, how would you handle it > when a story has multiple-topics associated with it? That's easy. Just use the topic associated with the story, as that is the official one. Here's something that will really bake your noodle: What if topic colors can vary by section. I think a better idea would be to use a separate table, that way this functionality can be limited to a plugin and not stomped on by the changes you'd need to implement it in core Slash. - Cliff |
|
From: shane <sh...@lo...> - 2003-10-18 12:33:36
|
On Saturday 18 October 2003 00:46, Ralph Dratman wrote: >[...] >I would like to associate a > COLOR with each TOPIC. I want this color to be used for the title bar > of each story for that topic. > > Leaving aside the various implementation details, the obvious way to > accomplish this is to add a color field to the topic table. I think that's how I'd do it to. However, how would you handle it when a story has multiple-topics associated with it? |
