|
List Info
Thread: Another FreeBSD Campsite server
|
|
| Another FreeBSD Campsite server |

|
2006-10-17 14:27:57 |
Yes, this will be handled more transparently in the future
with Switches
and what not. But for the moment, you could also (ab)use the
Topics for
that purpose.
You could create a root topic called Positioning (or
whatever) and then say
subtopics are "Top Story of the Day", "Second
Most Important Story", "Left
Sidebar Story". Then you could create a dropdown in
your article type
called Postioning (or Importance), and it would list the
options you had
defined as subtopics.
So your home page template would consist of several lists,
one of them
being the list of top stories (length 1), the other one the
list of Second
Most Important Stories... etc.
A bit cumbersome, but hey, it is a workaround, that mostly
bothers only the
web designer, not the editor/journalist.
And yes, to go back to Mugur's musing on how we should do it
in the future,
we should be able to show a list of all articles in one
issue in the admin
interface, regardless of the section, and be able to sort
this list by
Topics (Switches, whatever).
If you really want to bend your mind, thinking about the
future, introduce
Scheduled Publishing into the equation. We should really
think of advanced
home page management after 3.0...
Sava
digitalnegocio gmail.com
10/16/2006 06:04 PM ZE2
Please respond to campsite-support
To: campsite-support campware.org
cc:
bcc:
Subject: Re: [campsite-support] Another FreeBSD Campsite
server
Yeah, I know. For instance, this is the code to obtain the
list of articles
in a section marked to be on section page and ordered by the
"order number"
(not the article number) you can select in the section:
<!** List length 10 article type is noticia onsection is
on>
<!** Endlist>
The problem: homepage is not a section so you can't give an
order number to
their articles.
The only workaround I found is to make a homepage.tpl per
section.
In the template1, main article in section 1 is the most
important in home
page.
In the template2, main article in section 2 is the most
important in home
page.
In the template3, main article in section 3 is the most
important in home
page.
So you can associate one of these templates to the edition
according to the
importance of the news in every section.
But I think this is such an important issue that should be
considered a
better solution for in the future.
2006/10/16, Ondra Koutek <kouteko tol.org>:The priority on
the homepage? It
is question of templates. Depending on
the template you use on template you can put different
ctiterias to list
articles command which can additionaly be sorted. So take
the list and
customize it to your needs.
Ondra
digitalnegocio gmail.com pí?e v ne 15. 10. 2006 v 22:21
+0200:
> Thanks, Ondra. I added these two lines with crontab -e:
>
> # Campsite: acaba el proceso campsite_server cada 5
minutos.
> */5 * * * * /usr/bin/killall campsite_server
>
> Is it ok?
>
> And do you know how to give priority to articles in
home page?
>
> 2006/10/15, Ondra Koutek <kouteko tol.org>:
> This is campsite bug, that I am unable to fix.
the same bug is
> everywhere I see campsite and the only solution
I use
> everywhere is
> automatic campsite parser killing every 5 or 10
minutes.
> I believe that new campsite 3.0 with completely
rewritten
> parser will
> fix this issue. and I asked myself campsite
developers to
> speadup the
> 3.0 release asap.
>
> As the 3.0 is kind of near (I hope till the end
of the year
> 2006) I
> believe we can live with restarts and wait for
new parser,
> then loose
> time by fixing 2.6 branch.
>
> Ondra
>
> digitalnegocio gmail.com pí?e v ne 15. 10.
2006 v 20:25 +0200:
> > My first impressions after 48 hours
testing are really,
> really good.
> >
> > I only got two problems:
> >
> > - The server stops after some time.
> > There were errors!
> > Internal error: Invalid value "
informes.info" of "site
> alias"
> > I fix it killing campsite_server process
and restarting
> apache, but I
> > hope there is a way to avoid this error. I
received in the
> mail these
> > two messages:
> >
> > Subject: Cron
> >
> <root negocio>
/usr/local/campsite/sbin/capsite_notifyendsubs
> > X-Cron-Env: <SHELL=/bin/sh>
> > X-Cron-Env: <HOME=/root>
> > X-Cron-Env: <PATH=/usr/bin:/bin>
> > X-Cron-Env: <LOGNAME=root>
> > X-Cron-Env: <USER=root>
> >
/usr/local/campsite/sbin/capsite_notifyendsubs: not found
> >
> >
>
------------------------------------------------------------
--------------
> >
> > negocio kernel log messages:
> > +++ /tmp/security.K9DafZLi Sun Oct 15
03:04:04 2006
> > +pid 31927 (campsite_server), uid 80:
exited on signal 11
> (core
> > dumped)
> > +pid 34654 (campsite_server), uid 80:
exited on signal 11
> (core
> > dumped)
> > +pid 34772 (campsite_server), uid 80:
exited on signal 11
> (core
> > dumped)
> >
> >
> > - In the other hand, I know how to
priorize the articles in
> the
> > sections (with the numbers), but not how
to do it in the
> home. I can
> > specify the article to appear on the home
page, but ¿how to
> set the
> > order?
> >
> > Problems aside, Campsite is fantastic and
FreeBSD server is
> fast and
> > smooth.
>
>
Invest in Press Freedom: Visit http://www.mdl
f.org/support-free-press
|
|
| Another FreeBSD Campsite server |

|
2006-10-17 17:07:59 |
|
I will think about all your good advices. The topics system seems to be good, but it requires the editor to edit every article involved in the frontpage to change its aspect (I mean, open the section, open the article, change topic, save, get back, go to another section, another article, change topic, save... It is ok? No. Open the section, open the article...). If there is an easier way to change the topics without entering in every article, please let me know.
Meanwhile, my two cents for the future: a virtual section, which is the frontpage, with the same ordering system than normal sections. I think it is the easier way to achieve the frontpage ordering and good enough to make complex templating. At least for me: combining this ordering system, image numbers and only three templates, I can get five different frontpages in every section.
This frontpage issue apart, I'm really glad with campsite. Did I tell you before? 
2006/10/17, sava.tatic mdlf.org">sava.tatic mdlf.org < sava.tatic mdlf.org">sava.tatic mdlf.org>:
Yes, this will be handled more transparently in the future with Switches and what not. But for the moment, you could also (ab)use the Topics for
that purpose.
You could create a root topic called Positioning (or whatever) and then say subtopics are "Top Story of the Day", "Second Most Important Story", "Left Sidebar Story". Then you could create a dropdown in your article type
called Postioning (or Importance), and it would list the options you had defined as subtopics.
So your home page template would consist of several lists, one of them being the list of top stories (length 1), the other one the list of Second
Most Important Stories... etc.
A bit cumbersome, but hey, it is a workaround, that mostly bothers only the web designer, not the editor/journalist.
And yes, to go back to Mugur's musing on how we should do it in the future,
we should be able to show a list of all articles in one issue in the admin interface, regardless of the section, and be able to sort this list by Topics (Switches, whatever).
If you really want to bend your mind, thinking about the future, introduce
Scheduled Publishing into the equation. We should really think of advanced home page management after 3.0...
Sava
digitalnegocio gmail.com">digitalnegocio gmail.com 10/16/2006 06:04 PM ZE2
Please respond to campsite-support
To: campsite-support campware.org">campsite-support campware.org cc: bcc: Subject: Re: [campsite-support] Another FreeBSD Campsite server
Yeah, I know. For instance, this is the code to obtain the list of articles in a section marked to be on section page and ordered by the "order number" (not the article number) you can select in the section:
<!** List length 10 article type is noticia onsection is on> <!** Endlist>
The problem: homepage is not a section so you can't give an order number to their articles.
The only workaround I found is to make a
homepage.tpl per section.
In the template1, main article in section 1 is the most important in home page. In the template2, main article in section 2 is the most important in home page. In the template3, main article in section 3 is the most important in home
page.
So you can associate one of these templates to the edition according to the importance of the news in every section.
But I think this is such an important issue that should be considered a better solution for in the future.
2006/10/16, Ondra Koutek < kouteko tol.org">kouteko tol.org>:The priority on the homepage? It is question of templates. Depending on the template you use on template you can put different ctiterias to list
articles command which can additionaly be sorted. So take the list and customize it to your needs.
Ondra
digitalnegocio gmail.com">digitalnegocio gmail.com pí?e v ne 15. 10. 2006 v 22:21 +0200:
> Thanks, Ondra. I added these two lines with crontab -e: > > # Campsite: acaba el proceso campsite_server cada 5 minutos. > */5 * * * * /usr/bin/killall campsite_server > > Is it ok?
> > And do you know how to give priority to articles in home page? > > 2006/10/15, Ondra Koutek < kouteko tol.org">kouteko tol.org>: > This is campsite bug, that I am unable to fix. the same bug is
> everywhere I see campsite and the only solution I use > everywhere is > automatic campsite parser killing every 5 or 10 minutes. > I believe that new campsite 3.0
with completely rewritten > parser will > fix this issue. and I asked myself campsite developers to > speadup the > 3.0 release asap. > > As the
3.0 is kind of near (I hope till the end of the year > 2006) I > believe we can live with restarts and wait for new parser, > then loose > time by fixing 2.6 branch.
> > Ondra > > digitalnegocio gmail.com">digitalnegocio gmail.com pí?e v ne 15. 10. 2006 v 20:25 +0200: > > My first impressions after 48 hours testing are really,
> really good. > > > > I only got two problems: > > > > - The server stops after some time. > > There were errors! > > Internal error: Invalid value "
informes.info" of "site > alias" > > I fix it killing campsite_server process and restarting > apache, but I > > hope there is a way to avoid this error. I received in the
>  
| |