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

[Slashcode-development] css - is this possible

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

As it stands now, the css in slash-cvs is based on certain criteria,  
mainly:

user.currentsection, user.currentpage

What's css.theme intended use for?
How does one control what 'theme' the user is currently using?

What I am trying to figure out is this: let's say we have a yearly  
office party. We normally use a virtual url such as tld/party to  
point to tld/parties/party2006 or last year's tld/parties/party2005.  
That's done through mod_rewrite.

This party lets staffers and our outside vendors register to attend.  
The vendors pay to attend, so some of their registration is through ssl.

To process all this we created a slash::party plugin, which has  
party.pl. our entry in the css table points the css.page to 'party'.

Each year we  want this page's cosmetics to be unique. So we created  
a topic 'party', made it a nexus, created a skin with url party.tld  
and associated the skin with the topic 'party' nexus. i create new  
templates too: header\;party\;party, footer\;party;\party and index 
\;party\;party

So everyone hits the url and it looks sweet and everyone pays and  
registers through party.pl.

However, 2007 runs around. We create a 2007 item in slash::party's  
data, and we enter the event and misc information into the plugin's  
data so people can sign up to attend the event.

Only one catch - for historical, and search-engine value, management  
wants the 2006 pages to stay up on the website, and they don't want  
it's cosmetics to change.

Yet, 2007 will look entirely different from 2006.

There'in lies my problem/question. what's the best soln' for  
something such as this?

Most places just create /parties/party2006.asp or party2006.html.  
Since the registration process is interactive, we can't get away with  
doing it in html (if we could, we could control the style sheet used  
in each year's html, simple enough).

I suppose we could also use templates, ie /parties/party2006.tmpl  
since the correspondeing templates files are used to process the  
'body', and we can embed template-logic within each .tmpl to deal  
with the application process. however, i think the header and footer  
for a .tmpl are pulled from the templates html-header, linkrel,  
header and footer. So this may not work.

if party has a $constants->{default_year}, and someone hits party.pl? 
y=2006 I was considering maybe I could use the css.theme to match to  
'2006' so a different style sheet will be chosen?

that _might_ work if only the stylesheet has changed. if the html w/ 
in the templates needed to change, then the nexus would somehow have  
to change with the given year such that the skin would match to  
another skin, would would pull another set of templates out of the db.

So there's my big question. I've been mulling this around in my mind  
for a while now, trying to figure out the "best implementation  
method" that still fits within slash's API. Any suggestions appreciated.

  Shane

Re: [Slashcode-development] Another question: Moving to MySQL 5 or Stay with 4.1?

[Fred M. <fr...@ta...>]

shane wrote:
> 
> On Jan 20, 2006, at 5:50 PM, Fred Moyer wrote:
> 
>> On Fri, 20 Jan 2006, Eric Dannewitz wrote:
>>
>>> to get the slash stuff moved over? Is there any advantage to  running 
>>> Mysql 5 over 4.1? Any thing I should watch out for?
>>
>> I run taperfriendlymusic.org on Slashcode.  At one point the drive  
>> filled up and Mysql truncated two tables in the slash database,  that 
>> was using 3.2x.  I don't know if that is the case with 4.1 or  5 but 
>> you might want to
>> watch out for it.
> 
> huh? How does you letting your hard drive fill up have anything to do  
> with *anything* else? that's like saying "well I've got a server, and  
> it's HD filled up, and then things didn't work quite right" Well,  
> that's a shocker ;) Things are going to break if the filesystem's  full, 
> especially *database* servers!

I assume you use Slash because you have a lot of traffic, right?  That 
traffic generates logfiles, which take disk space.  You can argue that 
"Well you should have bought more hard drives", or "You should have a 
system ships the logs offsite".  Which I agree with but when you run a 
high traffic site based purely on donations, things are not always ideal 
and you make do with what you have.  People link to your site, and 
overnight you can generate several gigs of logfiles.  And also you have 
users uploading music, sometimes 10 or 20 gigs a night.

In my case, the Slash installation lost both the formkeys and access_log 
tables when the drive filled up.  Do you think it's good behavior for 
database servers to drop tables when they fill up?  Would it be good 
behavior for a filesystem to delete files when the filesystem fills up?

I"m not trying to nitpick Slashcode here or assign blame.  Slashcode has 
done really good things for myself and the music community I run.  I'm 
sharing my experience of an edge case that I've run into.  I suspect 
it's a Mysql issue and does not have anything to do with Slashcode, but 
I wanted to give you a heads up regarding my experience.

Good luck,

- Fred

Re: [Slashcode-development] Another question: Moving to MySQL 5 or Stay with 4.1?

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

On Jan 20, 2006, at 5:50 PM, Fred Moyer wrote:

> On Fri, 20 Jan 2006, Eric Dannewitz wrote:
>
>> to get the slash stuff moved over? Is there any advantage to  
>> running Mysql 5 over 4.1? Any thing I should watch out for?
>
> I run taperfriendlymusic.org on Slashcode.  At one point the drive  
> filled up and Mysql truncated two tables in the slash database,  
> that was using 3.2x.  I don't know if that is the case with 4.1 or  
> 5 but you might want to
> watch out for it.
>
> HTH,
>
> Fred

huh? How does you letting your hard drive fill up have anything to do  
with *anything* else? that's like saying "well I've got a server, and  
it's HD filled up, and then things didn't work quite right" Well,  
that's a shocker ;) Things are going to break if the filesystem's  
full, especially *database* servers!

  Shane

Re: [Slashcode-development] Another question: Moving to MySQL 5 or Stay with 4.1?

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

On Jan 20, 2006, at 4:30 PM, Eric Dannewitz wrote:

> Thanks to Blake for the script about the email bounces!

I second that :)

>
> Another question. I potentially have to rebuilt my server that my  
> slash sites run on. I'm wonder what the best way to move the MySQL  
> database is. The server is currently running FreeBSD 4.11 with  
> MySQL 4.1.14. I'm thinking of running FreeBSD 5.3 with MySQL 5.  
> Should a dump of the database be just fine to get the slash stuff  
> moved over?

The data? One would think so. However, did you read the changelog of  
"what's changed" documentation on MySQL's website for migrating from  
v4 to v5? If not, you should. That would give you a lot of insight.

And heck, you can always put mysql5 on another box, or the same box  
(not running w/ tcpip access in a different location on the file  
system) and try a db create and db import of the data from your slash  
site(s).

I'd guess it'd work. However, I haven't read any of the MySQL 5 docs  
yet, so...

> Is there any advantage to running Mysql 5 over 4.1? Any thing I  
> should watch out for?

I'm sure there are! However, again, did you read the mysql v5 info?  
http://www.mysql.com/ . Off the top of my head, it's got stored  
procedures, triggers and views. No full-text-query with innodb, but I  
recall read somewhere that's coming eventually.

>
> Thanks in advance.

 From what I've heard mention, someone from the OSTG group has been  
cleaning things up in the slashcode source (cvs version) to work with  
MySQL5.

When will it be done? I don't know, never been told - but I would  
guess "when it's done", sometime this winter/spring.

So - If I were you, I'd grab the latest-stable MySQL 4.1x, install it  
and use it, for now, if it's a production site that's gotta be  
stable. If you're "just testing" then install v5 and give it a test  
runthrough and be sure to email the slashcode-dev list so everyone  
can hear how it went :)

  Shane

Re: [Slashcode-development] Mail Transport Agent`

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

On Jan 20, 2006, at 2:39 PM, Richard Walker wrote:

> How do I configure my slashcode installation to send email?  I am
> running kernel 2.6.8-2-386 debian.  I ran dselect and started to
> install sendmail but then I got a bunch of conflicts and simply backed
> off.   What is one to do?

rather then retype it , have a read in the FAQ: http:// 
slash.lottadot.com/faqster.pl?op=view&fid=1#q92

Re: [Slashcode-development] Another question: Moving to MySQL 5 or Stay with 4.1?

[Fred M. <fr...@ta...>]

On Fri, 20 Jan 2006, Eric Dannewitz wrote:

> to get the slash stuff moved over? Is there any advantage to running Mysql 5 
> over 4.1? Any thing I should watch out for?

I run taperfriendlymusic.org on Slashcode.  At one point the drive filled 
up and Mysql truncated two tables in the slash database, that was using 
3.2x.  I don't know if that is the case with 4.1 or 5 but you might want to
watch out for it.

HTH,

Fred

[Slashcode-development] Another question: Moving to MySQL 5 or Stay with 4.1?

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

Thanks to Blake for the script about the email bounces!

Another question. I potentially have to rebuilt my server that my slash 
sites run on. I'm wonder what the best way to move the MySQL database 
is. The server is currently running FreeBSD 4.11 with MySQL 4.1.14. I'm 
thinking of running FreeBSD 5.3 with MySQL 5. Should a dump of the 
database be just fine to get the slash stuff moved over? Is there any 
advantage to running Mysql 5 over 4.1? Any thing I should watch out for?

Thanks in advance.

[Slashcode-development] Mail Transport Agent`

[Richard W. <lea...@gm...>]

How do I configure my slashcode installation to send email?  I am
running kernel 2.6.8-2-386 debian.  I ran dselect and started to
install sendmail but then I got a bunch of conflicts and simply backed
off.   What is one to do?

tx

Richard

Re: [Slashcode-development] Script to disable headlines?

[Blake C. <li...@li...>]

Funny you should ask, I *just* wrote this thing that seems to do a decent 
job. It dropped my bounces from around 600 to about 20.

First, this is a really bad way to harvest emails, but it catches most of 
them. I run qmail, so this works for for me, no idea how you'd do it 
elsewhere

grep \<.*\> 
/home/vpopmail/domains/0/lisnews.com/btcarver/Maildir/.Bounces/cur/* | sed 
's/ *(.*)//; s/>.*//; s/.*[:<] *//' | sort | uniq >emails.txt

Then this just opens that file and reads the emails. I think it should work 
on any other slash databases.

---------------------
#!/usr/bin/perl
use DBI;
$dbh = 
DBI->connect("dbi:mysql:database=database;host=localhost;user=user;password=password")
    or die "Couldn't connect to database: $DBI::errstr\n";

open (EMAILS, "emails.txt");
while ($email = <EMAILS>) {
    chomp($email);
 print "\n$email\n";
 $sql = "select uid from users where realemail like '%$email%'";
 print $sql;
 $sth = $dbh->prepare($sql);
 $sth->execute ||
    die "Doh";
 $RecordData = $sth->fetchrow_hashref();
 $uid = $RecordData->{'uid'};
 if($uid) {
           foreach($uid)
             {
              print "\ndeleted $uid\n";
              $sql = "delete from users_messages where uid = $uid and (code 
= 1 or code = 0)";
              $sth = $dbh->prepare($sql);
              $sth->execute ||
               die "Doh";
             }
           }
                          }



--------------
Blake Carver
LISNews.org
Librarian & Information Science News
http://www.lisnews.org

----- Original Message ----- 
From: "Eric Dannewitz" <eri...@ja...>
To: <sla...@li...>
Sent: Thursday, January 19, 2006 11:27 AM
Subject: [Slashcode-development] Script to disable headlines?


> Does anyone have a perl script to set email address not to receive email? 
> I have a lot of email address that bounce when my slash site sends out 
> daily stories, and I'd like an easy way to set these addresses to not 
> receive the daily headlines.
>
> Thanks
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-development
>
> 

[Slashcode-development] Script to disable headlines?

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

Does anyone have a perl script to set email address not to receive 
email? I have a lot of email address that bounce when my slash site 
sends out daily stories, and I'd like an easy way to set these addresses 
to not receive the daily headlines.

Thanks

[Slashcode-development] mysql 5

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

Anyone tried it yet?

I haven't got around to it, so I'm curious whether you've run into  
any problems with Slash and it. I would think there'd be no issues,  
but ya never know.

  Shane

[Slashcode-development] questions about latest changes (css/imagedir)

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

why the need for the new 'css_use_imagedir' var?

why the change from htdoc={path}/stylesheet.css to  css={path}/ 
stylesheet.css? for the installer's handling of the insert into the  
css table?

  Shane

Re: [Slashcode-development] Recreating all old articles

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

On Oct 28, 2005, at 2:38 PM, Alex McLintock wrote:

> If I want to recreate all my old static articles what is the best  
> way of doing that?
>
> (Sorry this is not *precisely* a development question. I am not  
> sure what other list is active)
>
> Alex

make them all dirty. there's a script up on lottadot that'll do that  
for you. have a look on http://slash.lottadot.com/

  shane

[Slashcode-development] Recreating all old articles

[Alex M. <al...@ow...>]

If I want to recreate all my old static articles what is the best way of 
doing that?

(Sorry this is not *precisely* a development question. I am not sure 
what other list is active)

Alex

Re: [Slashcode-development] css_types?

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

On Oct 27, 2005, at 2:25 PM, Tim Vroom wrote:

> After talking to you online I'll just add the text and link to the  
> FAQ you
> added since that covers all the possibilities well.
> [...]
> user_theme is one of the last css types called so basically would  
> allow a user
> to override a site's look and feel.  Right now this is used for  
> simpledesign,
> and lowbandwidth types.
>
> You could for instance add a preference that allowed a user to set  
> their
> sitewide theme to one of 5 choices.  Right now the theme selection in
> getCSS() in MySQL.pm checks for a user's simpledesign preference
> and picks a css file based on that, or if that's not set falls back  
> to $user->{css_theme};
>
> If you had a preference which updated that, you could have user  
> selected
> themes, simpledesign being one option, that's currently controlled  
> by a different
> preference.
>
> The skeleton is there to allow for such things, however we may need  
> to separate
> out simpledesign into its own thing if we want to allow for both  
> simpledesign, and
> a user_theme to be triggered at the same time.

Oh, very cool. Talk about skinning the skins :)

Now all we need is a method for users to supply their own css, and  
save that as a byte-limitted txt field such that when they hit the  
site it'd pull that push it is to the end of the css-list. Hence, the  
user html trumping the base/plugin/theme css.

I don't if that's where all this was headed. I'm just rambling. But  
I'd think with /.'s geek traffic it'd be like an easy or lite way to  
do a greasemonkey effect.

  Shane

Re: [Slashcode-development] css_types?

[Tim V. <tv...@va...>]

After talking to you online I'll just add the text and link to the FAQ you
added since that covers all the possibilities well.

http://slash.lottadot.com/faqster.pl?op=view&fid=2#q110
--------------------------------------------------------
If the plugin's css file is to be shown only when your plugin's perl 
script is run (ie plugin.pl) then you should create the plugin with 
type='page'.

If the plugin's css file is to be shown when another script is run, then 
it should still be 'page'.

If the plugin's css file is to be shown all the time, then use type 'base'.
That way, a site's theme can still over-ride the plugin's style sheet.
--------------------------------------------------------

user_theme is one of the last css types called so basically would allow 
a user
to override a site's look and feel.  Right now this is used for 
simpledesign,
and lowbandwidth types.

You could for instance add a preference that allowed a user to set their
sitewide theme to one of 5 choices.  Right now the theme selection in
getCSS() in MySQL.pm checks for a user's simpledesign preference
and picks a css file based on that, or if that's not set falls back to 
$user->{css_theme};

If you had a preference which updated that, you could have user selected
themes, simpledesign being one option, that's currently controlled by a 
different
preference.

The skeleton is there to allow for such things, however we may need to 
separate
out simpledesign into its own thing if we want to allow for both 
simpledesign, and
a user_theme to be triggered at the same time.

--Tim


Shane wrote:

> question regarding the css_type table:
>
> currently I see these types defined:
>
> mysql> select * from css_type;
> +------+------------+----------+
> | ctid | name       | ordernum |
> +------+------------+----------+
> |    1 | base       |        1 |
> |    2 | page       |        2 |
> |    3 | theme      |        3 |
> |    4 | user_theme |        5 |
> |    5 | print      |        6 |
> |    6 | skin       |        4 |
> |    7 | handheld   |        7 |
> +------+------------+----------+
> 7 rows in set (0.13 sec)
>
>
> if a plugin adds a .css file, what should the type be? (I thought  
> maybe 'plugin', but there's no such type).
>
> what's the 'user_theme' for?
>
>  Shane
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-development

[Slashcode-development] css_types?

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

question regarding the css_type table:

currently I see these types defined:

mysql> select * from css_type;
+------+------------+----------+
| ctid | name       | ordernum |
+------+------------+----------+
|    1 | base       |        1 |
|    2 | page       |        2 |
|    3 | theme      |        3 |
|    4 | user_theme |        5 |
|    5 | print      |        6 |
|    6 | skin       |        4 |
|    7 | handheld   |        7 |
+------+------------+----------+
7 rows in set (0.13 sec)


if a plugin adds a .css file, what should the type be? (I thought  
maybe 'plugin', but there's no such type).

what's the 'user_theme' for?

  Shane

[Slashcode-development] Sql caching issue with perl/mysql?

[Gaulin, M. <mg...@gl...>]

Hi
I added a new table to slash (to allow emails to go to non-registered
users) and when the "daily" task ran last night it seemed to not see the
latest table contents.  I'm using the mysql "rename table" command to
swap a new copy of the table in and rotate an old copy out, and it sent
the emails to the people in the "old" table.  Is it possible that
renaming a table would allow an existing process (slashd) that had
already connected to the older copy of the table to not see it?  (I can
imagine a sql client library caching table ids or query plans or
something like that, but I certainly wasn't expecting it.)

Can anyone confirm this kind of problem, or am I just losing my mind?

Thanks
	Mark

[Slashcode-development] Slash plugins in C/C++?

[Ixkorr O. <oxk...@ya...>]

Hello,

Is it possible to write Slashcode plugins in C/C++? I
would like to develop some custom slash blocks, but I
don't have any experience writing Perl code, only
C/C++.

Also, are plugins the only way to add scripts to
generate Slash content? Is it possible to call CGI
programs by inserting HTML code into a Slash block?

Thanks for any info or pointers.

IO




		
____________________________________________________
Sell on Yahoo! Auctions – no fees. Bid on great items.  
http://auctions.yahoo.com/

[Slashcode-development] What do you think of *this?

[danalien <dan...@sl...>]

Hello,

this = http://science.slashdot.org/comments.pl?sid=152374&cid=12794462


PS. sorry for reposting this again, but for some reasons it went out 'blank', though
if you look at the source of the (previous) msg it's all there...  *weird*
-- 

//   with regards
//   UID ::  danalien-slashcode-development  ::  <${gofigurewhatmyemailis}@slicker.org>

- - -
Motto: I don't claim I know more than I know,
and if you know you know more than I know,
then by all means, let me know.

[Slashcode-development] What do you think of *this?

[danalien <dan...@sl...>]

Hello,

* this = http://science.slashdot.org/comments.pl?sid=152374&cid=12794462

-- 

//   with regards
//   UID ::  danalien-slashcode-development  ::  <${gofigurewhatmyemailis}@slicker.org>

- - -
Motto: I don't claim I know more than I know,
and if you know you know more than I know,
then by all means, let me know.

RE: [Slashcode-development] Side effects of making a topic a nexus?

[Gaulin, M. <mg...@gl...>]

Hi Shane
I did consider making a sort of "no-op" nexus, to hold the topic that I =
want to have/inherit the extras.  I suspect that the dummy topic would =
show up on the topics list, along with the real one, and that makes me =
not want to go there. =20

The true intent (or "vision") of a nexus is not entirely clear to me, =
and some of the code feels sort of "in between" different points of =
view. I chalk that up to things not be fully implemented yet, but there =
are also spots where things started leaning toward some "specialness" =
for nexuses that probably could have been done more generally for all =
topics (like the extras), or not done for nexuses at all (why not allow =
stories to be submitted to a nexus, if the db says it's ok?).

Assuming you don't care about these issues, the Rating system was pretty =
easy to install. I posted detailed to this list on 12/16/04, and I'll =
send them to you off-list too.

Thanks
	Mark



-----Original Message-----
From: sla...@li...
[mailto:sla...@li...]On Behalf Of
Shane
Sent: Wednesday, April 06, 2005 2:07 PM
To: <sla...@li...>
<sla...@li...>
Subject: Re: [Slashcode-development] Side effects of making a topic a
nexus?



On Apr 6, 2005, at 1:26 PM, Gaulin, Mark wrote:

> FYI, it turns out that making a topic a nexus has a side effect that=20
> no one mentioned yet: the topic will not appear in the list of=20
> available topics for story submission, which stinks (for my situation, =

> anyway).  I wish I knew the reason for that restriction... that might=20
> help me avoid other issues later (esp if I try to work around it).
>
> It seems weird since a topic already has a "story submittable"=20
> attribute that you'd think would cover any case were you wouldn't want =

> someone to submit to the nexus topic.  The logic to prevent a nexus=20
> topic from showing up in the submit.pl topic dropdown is in=20
> getDescriptions(), item "non_nexus_topics-submittable".  The=20
> "non_nexus_topics" prefix certainly means it was done on purpose.
>
> Oh well... I guess the whole topic/nexus thing was not intended to=20
> deal with a single topic that just needs extras (or, more generally, a =

> single topic that just wants to be a nexus of one).  Maybe the "nexus" =

> concept in "topic_nexus_extras" should be dropped, so any old topic=20
> can have extras.

Well why not

a) rename the nexus topic to "myTopic NEXUS"
b) create a new topic, that's a child of the "myTopic NEXUS", and name=20
this new topic the original name. check off issubmittable on this new=20
topic.

That would give you what you want, right?

> (The extra I'm trying to use is the Rating system.)
>

I've been meaning to try that out. What'd you have to do, to get it to=20
work? I recall there being some confusion a while back because when you=20
install-plugin it, there's other config work I thought I read somewhere=20
that you have to do, before it'll work properly.

I've also been wondering if it's possible to use it to attaching=20
'ratings' to other things, besides stories...

  Shane


--
My slashcode stuff: http://slash.lottadot.com/



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Slashcode-development mailing list
Sla...@li...
https://lists.sourceforge.net/lists/listinfo/slashcode-development

Re: [Slashcode-development] Side effects of making a topic a nexus?

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

On Apr 6, 2005, at 1:26 PM, Gaulin, Mark wrote:

> FYI, it turns out that making a topic a nexus has a side effect that 
> no one mentioned yet: the topic will not appear in the list of 
> available topics for story submission, which stinks (for my situation, 
> anyway).  I wish I knew the reason for that restriction... that might 
> help me avoid other issues later (esp if I try to work around it).
>
> It seems weird since a topic already has a "story submittable" 
> attribute that you'd think would cover any case were you wouldn't want 
> someone to submit to the nexus topic.  The logic to prevent a nexus 
> topic from showing up in the submit.pl topic dropdown is in 
> getDescriptions(), item "non_nexus_topics-submittable".  The 
> "non_nexus_topics" prefix certainly means it was done on purpose.
>
> Oh well... I guess the whole topic/nexus thing was not intended to 
> deal with a single topic that just needs extras (or, more generally, a 
> single topic that just wants to be a nexus of one).  Maybe the "nexus" 
> concept in "topic_nexus_extras" should be dropped, so any old topic 
> can have extras.

Well why not

a) rename the nexus topic to "myTopic NEXUS"
b) create a new topic, that's a child of the "myTopic NEXUS", and name 
this new topic the original name. check off issubmittable on this new 
topic.

That would give you what you want, right?

> (The extra I'm trying to use is the Rating system.)
>

I've been meaning to try that out. What'd you have to do, to get it to 
work? I recall there being some confusion a while back because when you 
install-plugin it, there's other config work I thought I read somewhere 
that you have to do, before it'll work properly.

I've also been wondering if it's possible to use it to attaching 
'ratings' to other things, besides stories...

  Shane


--
My slashcode stuff: http://slash.lottadot.com/

RE: [Slashcode-development] Side effects of making a topic a nexus?

[Gaulin, M. <mg...@gl...>]

FYI, it turns out that making a topic a nexus has a side effect that no =
one mentioned yet: the topic will not appear in the list of available =
topics for story submission, which stinks (for my situation, anyway).  I =
wish I knew the reason for that restriction... that might help me avoid =
other issues later (esp if I try to work around it).

It seems weird since a topic already has a "story submittable" attribute =
that you'd think would cover any case were you wouldn't want someone to =
submit to the nexus topic.  The logic to prevent a nexus topic from =
showing up in the submit.pl topic dropdown is in getDescriptions(), item =
"non_nexus_topics-submittable".  The "non_nexus_topics" prefix certainly =
means it was done on purpose.

Oh well... I guess the whole topic/nexus thing was not intended to deal =
with a single topic that just needs extras (or, more generally, a single =
topic that just wants to be a nexus of one).  Maybe the "nexus" concept =
in "topic_nexus_extras" should be dropped, so any old topic can have =
extras.  (The extra I'm trying to use is the Rating system.) =20

Thanks
	Mark


-----Original Message-----
From: Gaulin, Mark=20
Sent: Friday, March 04, 2005 6:58 AM
To: 'Shane'
Cc: sla...@li...
Subject: RE: [Slashcode-development] Side effects of making a topic a
nexus?


Hi Shane
Thanks again for the explanation, and the confirmation that what I want =
to do should work. I believe I fixed my problem by changing the code a =
bit. I'm going to run my changes by the original author to see if they =
are right.
Thanks
  Mark

-----Original Message-----
From: Shane [mailto:sh...@lo...]
Sent: Thursday, March 03, 2005 5:25 PM
To: Gaulin, Mark
Cc: sla...@li...
Subject: Re: [Slashcode-development] Side effects of making a topic a
nexus?



A skin is the equivlant of a 'section'.

The skin kinda brings it all together, including the graphical-changes=20
in appearance, if any, you'd want.

So, to answer your questions: yes, a skin gives you distinct sets of=20
articles - based on the skins.nexus. Since the nexus is a group of=20
topics - any story posted w/ a topic that's in that nexus is shown in=20
that skin. (well, depending on how you've arranged your topic=20
parent/children and the topics-list in each story).

I believe nexuses and skins are supposed to be 1-1, because you can=20
only assign a single nexus to any one skin.

A topic seems to only have topic-extras when it's marked as a nexus. So=20
you'd have to mark your 'book reviews' topic as being a Nexus. But you=20
don't necessarily have to associate a Nexus with a skin that I can see.=20
So I think you're OK with what you want to do.

  Shane




On Mar 3, 2005, at 4:05 PM, Gaulin, Mark wrote:

> Hi Shane
> I don't think I want the topic to be a skin, but that may be because I =

> don't know what a skin is for. Looking at the skins table definition,=20
> it seems that you want a skin if you want to have a different host=20
> name, indexhandler, and I'm not sure, but does it also give you a=20
> distinct set of articles on the "home" page (for that host name)?  I=20
> don't want any of those things for this topic/nexus (called Book=20
> Reviews), I just want to have topic_nexus_extras that are different=20
> than the Main Page (it's parent topic).
>
> Are nexuses and skins always supposed to be 1-to-1?  I would think=20
> not, but that could be part of my problem.
>
> Thanks
> 	Mark
>
>
> -----Original Message-----
> From: Shane [mailto:sh...@lo...]
> Sent: Thursday, March 03, 2005 1:28 PM
> To: Gaulin, Mark
> Cc: sla...@li...
> Subject: Re: [Slashcode-development] Side effects of making a topic a
> nexus?
>
>
>
> On Mar 3, 2005, at 11:40 AM, Gaulin, Mark wrote:
>
>> Hi
>> In order to get unique "extras" (from topic_nexus_extras) for a topic
>> I have, it looks like I need to convert the topic to a nexus, which
>> could be as simple as checking the Nexus box on the Topics Editor
>> page.  So far so good.  My question is, will anything else change for
>> that topic, assuming I don't change anything else?
>>
>> Thanks
>> 	Mark
>
> I don't think so. Just realize that making it a nexus doesn't
> necessarily make it a skin, if that's what you're going after.
>
>   Shane
>
>
>
--
http://shane.lottadot.com/

Re: [Slashcode-development] bad form error with aol/webtv?

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

On Apr 3, 2005, at 8:47 PM, CHRISTOPHER C WINN wrote:

> Very strange. An overwhelming number of AOL users and WebTV users are 
> reporting
> "invalid form key" errors when using my slash site - and it's so bad, 
> they
> can't do anything. Create an account or post any comments. Nothing. 
> Anyone
> heard of this? And if so, is there a solution?

My guess is it's the AOL proxies that are giving you problems.

What version of Slash/Apache are you running? You didn't say.

  Shane


--
My slashcode stuff: http://slash.lottadot.com/