I am using FreeBSD 6.1 32 bits and never met this issue.
Can you describe the way you install campsite?

Ondra

digitalnegocio@gmail.com píše v čt 12. 10. 2006 v 21:10 +0200:
> At last, the support center of my provider installed manually a
> FreeBSD 6.1 64 bits in my server. It works fine.
>
> I installed:
>
> Apache 2.0.59
> php4
> mysql5
>
>
> I'm getting some strange errors while compiling the campsite port.
> These are some of them:
>
> PHP Warning: Function registration failed - duplicate name -
> imagechar in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecharup in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorat in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorallocate in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepalettecopy in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromstring in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorclosest in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorclosesthwb in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolordeallocate in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorresolve in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorexact in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorset in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolortransparent in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorstotal in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorsforindex in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecopy in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecopymerge in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecopymergegray in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecopyresized in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreate in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatetruecolor in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imageistruecolor in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagetruecolortopalette in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagesetthickness in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefilledarc in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefilledellipse in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagealphablending in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagesavealpha in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorallocatealpha in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorresolvealpha in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorclosestalpha in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolorexactalpha in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecopyresampled in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagerotate in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imageantialias in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagesettile in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagesetbrush in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagesetstyle in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefrompng in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromgif in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromjpeg in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromwbmp in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromxbm in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromxpm in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromgd in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromgd2 in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecreatefromgd2part in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - imagepng
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - imagegif
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagejpeg in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagewbmp in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - imagegd
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - imagegd2
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagedestroy in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagegammacorrect in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefill in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefilledpolygon in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefilledrectangle in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefilltoborder in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefontwidth in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefontheight in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imageinterlace in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imageline in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imageloadfont in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepolygon in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagerectangle in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagesetpixel in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagestring in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagestringup in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - imagesx
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - imagesy
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagedashedline in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagettfbbox in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagettftext in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imageftbbox in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagefttext in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepsloadfont in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepsfreefont in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepsencodefont in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepsextendfont in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepsslantfont in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepstext in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagepsbbox in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagetypes in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> jpeg2wbmp in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - png2wbmp
> in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> image2wbmp in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagelayereffect in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> imagecolormatch in Unknown on line 0
> PHP Warning: gd: Unable to register functions, unable to load in
> Unknown on line 0
> PHP Warning: Function registration failed - duplicate name - iconv in
> Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> ob_iconv_handler in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> iconv_get_encoding in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> iconv_set_encoding in Unknown on line 0
> PHP Warning: iconv: Unable to register functions, unable to load in
> Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_connect in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_pconnect in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_close in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_select_db in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_query in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_unbuffered_query in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_db_query in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_list_dbs in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_list_tables in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_list_fields in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_list_processes in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_error in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_errno in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_affected_rows in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_insert_id in Unknown on line 0
> PHP Warning: Function registration failed - duplicate name -
> mysql_result in Unknown on line 0
>
>
>
>

most likely, you have upgraded or recompiled PHP, and there are
dynamic extensions being loaded that are duplicating compiled-in
functions in PHP. check the 'extension=' lines in your php.ini file,
and have a look in whatever directory is named on your 'extension-dir'
line.


On 10/12/06, digitalnegocio@gmail.com wrote:
> cd /usr/ports/www/apache20
> make install clean
>
>
> cd /usr/ports/lang/php4
> make install clean
>
>
> cd /usr/ports/lang/php4-extensions
> make config
> make install clean
>
> cd /usr/ports/www/campsite
> make install clean
>
>
> 2006/10/12, Ondra Koutek :
> > I am using FreeBSD 6.1 32 bits and never met this issue.
> > Can you describe the way you install campsite?
> >
> > Ondra
> >
> > digitalnegocio@gmail.com p

As Holman noticed, the problem was in a previous installation of apache,
that didn't erase the httpd.conf (that loads dinamically modules that are in
conflict with the cli version).

At last, I installed only the cli version, not the module one. And I wonder
if this will have a negative consecuence for me (can I include my own php
code with phpwrapper in the pages?)

By the way, now I can't access the aplication because the server didn't
recognize the php, so the explorer asks me to save the page.

I added the "AddType... .php" lines in httpd and campsite-vhost.conf with
the same result. Does someone know what's wrong?

Thanks, Mugur. Now I now Thta's the problem, because I uninstalled the
module, because I thought only the cli was needed.

I will reinstall everything again.

Just a short message to let you know that not everything are tech problems.
I'm having fun creating the publication (templates, article types and so
on). And the system works fine: fast and safe.

Thanks for the good work.

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
> /usr/local/campsite/sbin/capsite_notifyendsubs
> X-Cron-Env:
> X-Cron-Env:
> X-Cron-Env:
> X-Cron-Env:
> X-Cron-Env:
> /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.

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 :
> 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
> >
> /usr/local/campsite/sbin/capsite_notifyendsubs
> > X-Cron-Env:
> > X-Cron-Env:
> > X-Cron-Env:
> > X-Cron-Env:
> > X-Cron-Env:
> > /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.
>
>

How would you implement an ordering system in the issue? Browsing all articles in an issue in one
list may be quite cumbersome. My first idea is to implement article score or something like that
but we certainly need to get more ideas.

I posted this email to campsite-dev@campware.org too and I invite you to continue this discution
there.

Mugur

--- digitalnegocio@gmail.com wrote:
> 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:
>
>
>
>
> 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 :
> >
> > 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

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 :
>
>
>
> 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:
>
>
>
>
> 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 :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

Yesterday I had a problem changing the hostname in my server: the
publication stopped working and got some mysql errors, so I rolled back the
changes and restored a backup. The problems were fixed, but know I receive a
permissions error in Image and Thumbnails directory when I try to upload a
picture.

I reinstalled ImageMagick and give writing permissions to both directories,
but the problem remains.

Any quick help would be really appreciated because we can't attach images to
the news.

Thank you.



2006/10/19, Mugur Rus :
>
> Thanks for ideas, I created a ticket for this feature and put it under
> public requests:
> http://code.campware.org/projects/campsite/ticket/2352
>
> Mugur
>
> --- digitalnegocio@gmail.com wrote:
> > 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 :
> > >
> > >
> > >
> > > 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:
> > >
> > >
> > >
> > >
> > > 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 :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

Yes, and every file in those directories.

2006/10/23, Holman Romero :
>
> is the user running apache the owner for both images and thumbnails
> directories?
>
>
> On 10/23/06, digitalnegocio@gmail.com wrote:
> > Yesterday I had a problem changing the hostname in my server: the
> > publication stopped working and got some mysql errors, so I rolled back
> the
> > changes and restored a backup. The problems were fixed, but know I
> receive a
> > permissions error in Image and Thumbnails directory when I try to upload
> a
> > picture.
> >
> > I reinstalled ImageMagick and give writing permissions to both
> directories,
> > but the problem remains.
> >
> > Any quick help would be really appreciated because we can't attach
> images to
> > the news.
> >
> > Thank you.
> >
> >
> >
> > 2006/10/19, Mugur Rus :
> > > Thanks for ideas, I created a ticket for this feature and put it under
> > public requests:
> > > http://code.campware.org/projects/campsite/ticket/2352
> > >
> > > Mugur
> > >
> > > --- digitalnegocio@gmail.com wrote:
> > > > 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 :
> > > > >
> > > > >
> > > > >
> > > > > 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:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 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 :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

I deinstalled ImageMagick and installed GraphicsMagick; restarted apache and
the template engine. But I get the same error.


2006/10/23, Ondra Koutek :
>
> On FreeBSD we use Graphics magick instead of Image Magick. Remove Image
> magick if you do not need it elsewhere, reinstall Graphics Magick and
> restart apache.
>
> Ondra
>
> digitalnegocio@gmail.com p

I fighted this issue a lot. if you give me access to your server, i can
have a look at it. You can send me passwords to +420 603 461 548
At least you can try to reinstall php, check file permissions...

Ondra

digitalnegocio@gmail.com píše v po 23. 10. 2006 v 14:18 +0200:
> I deinstalled ImageMagick and installed GraphicsMagick; restarted
> apache and the template engine. But I get the same error.
>
>
> 2006/10/23, Ondra Koutek :
> On FreeBSD we use Graphics magick instead of Image Magick.
> Remove Image
> magick if you do not need it elsewhere, reinstall Graphics
> Magick and
> restart apache.
>
> Ondra
>
> digitalnegocio@gmail.com píše v po 23. 10. 2006 v 14:01 +0200:
> > Yes, and every file in those directories.
> >
> > 2006/10/23, Holman Romero < holman.romero@gmail.com>:
> > is the user running apache the owner for both images
> and
> > thumbnails directories?
> >
> >
> > On 10/23/06, digitalnegocio@gmail.com
> > wrote:
> > > Yesterday I had a problem changing the hostname in
> my
> > server: the
> > > publication stopped working and got some mysql
> errors, so I
> > rolled back the
> > > changes and restored a backup. The problems were
> fixed, but
> > know I receive a
> > > permissions error in Image and Thumbnails
> directory when I
> > try to upload a
> > > picture.
> > >
> > > I reinstalled ImageMagick and give writing
> permissions to
> > both directories,
> > > but the problem remains.
> > >
> > > Any quick help would be really appreciated because
> we can't
> > attach images to
> > > the news.
> > >
> > > Thank you.
> > >
> > >
> > >
> > > 2006/10/19, Mugur Rus < mugur1973@yahoo.com>:
> > > > Thanks for ideas, I created a ticket for this
> feature and
> > put it under
> > > public requests:
> > > >
> http://code.campware.org/projects/campsite/ticket/2352
> > > >
> > > > Mugur
> > > >
> > > > --- digitalnegocio@gmail.com wrote:
> > > > > 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
> :
> > > > > >
> > > > > >
> > > > > >
> > > > > > 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:
> > > > > >
> > > > > > > onsection
> > is on>
> > > > > >
> > > > > >
> > > > > > 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:
> > > > > > > > X-Cron-Env:
> > > > > > > > X-Cron-Env:
> > > > > > > > X-Cron-Env:
> > > > > > > > X-Cron-Env:
> > > > > > > >
> > > /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.mdlf.org/support-free-press
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam? Yahoo! Mail has the best spam
> protection
> > around
> > > > http://mail.yahoo.com
> > > >
> > >
> > >
> >
> >
> > --
> > /holman
> >
>
>

Ondra fixed my system, which is working properly now.

Thanks a lot.


2006/10/23, digitalnegocio@gmail.com :
>
> The error message, in Spanish:
>
> "El sistema no pudo crear el archivo 'cms-thumb-000000190.jpg'. Por favor
> verifique que el usuario 'www' tenga permiso para escribir en el directorio
> '/usr/local/campsite/www/campsite/html/images//thumbnails'. "
>
> BTW, the images are created in both directories, but the system says they
> are not.
>
>
>
> 2006/10/23, Ondra Koutek :
> >
> > I fighted this issue a lot. if you give me access to your server, i can
> > have a look at it. You can send me passwords to +420 603 461 548
> > At least you can try to reinstall php, check file permissions...
> >
> > Ondra
> >
> > digitalnegocio@gmail.com p