I was upgrading and put the files like asked and got a totally blank
site.
Apache error log tells:

[Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP Notice:
Undefined index: CacheEngine in /home/webadmin/www.mywebserver.fi/html/classes/SystemPref.php
on line 54
[Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP Fatal
error: Cannot redeclare templateerrorhandler() in /home/webadmin/www.mywebserver.fi/html/template_engine/classes/SyntaxError.php
on line 137

/G

On 24.6.2009, at 12.05, sava.tatic@mdlf.org wrote:

>
> Dear All,
>
> I am happy to announce the release of Campsite 3.3 "Speedy".
> "Speedy," is a
> major upgrade, bringing--you've guessed right--more speed (up to a 5x
> improvement), as well as many other enhancements.
>
> The main new features Campsite 3.3 brings are:
>
> * New article-field types: switch and numeric
> * Pluggable caching mechanism
> * Much improved caching (list classes, all database access classes,
> images, object lists, template meta action list)
> * Optimization of the ArticleType and ArticleTypeField classes
> * Caching for static methods that return objects list
> * Better log of all backend activity
> * Better online template editor (Editarea)
> * Global setting for resizing images inserted via the TinyMCE
> editor
> * Upgrade of the TinyMCE editor to the latest stable version,
> with a
> completely rewritten Paste from Word plugin
> * Enhancements to the Article Type management screens
> * Usability improvements to the Localizer tool (progress
> indicator and
> highlights to string groups needing attention.
>
> For a full list of enhancements and bug fixes, please go here:
> http://trac.campware.org/campsite/query?status=closed&milestone=3.3.0
>
> If you are a Campsite fan and would like to help it develop even
> faster,
> please take a minute to read our new How to Contribute section of the
> Campsite wiki (
> http://trac.campware.org/campsite/wiki/HowToContribute-Campsite).
>
> And, for starters, get the press release attached to the official
> announcement on the campware site
> (http://http://campware.org/en/camp/campsite_news/762/) and send it to
> anyone who may find it of interest. Let's get the word out!
>
> All the best (with the usual apologies for cross-posting),
>
> Sava
>

Hi,If you used the campsite-backup script and if it said it completed its job, then you are fine. Being an amateur system administrator myself, I've also found this part of the instructions a bit cryptic (but I thought it was only me). So we'll change it to something more copy-and-pastable very soon. And once we sort your problems, please let's document how we did it on your particular setup.The way I do it as root on my budding online empire (a BIG joke , a Centos machine with Plesk: cp  -a  /directorywhereiunpackedthenewtarball/campsite/implementation/site/*    /var/www/vhosts/myexampledomain.net/httpdocs/You don't need to copy any configuration files or anything. What I found out is that sometimes I have to make sure that apache user has all the required rights, which I achieve as root with:chown -R apache:apache /var/www/vhosts/myexampledomain.net/httpdocsThis is again valid only under Centos. I hope someone more knowledgeable will step in and provide a proper, yet not too succint explanation.All the best,Savap.s. and yes, sometimes I need to restart apache... -----Generare Management Department <management@generare.com> wrote: -----To: campsite-support@campware.orgFrom: Generare Management Department <management@generare.com>Date: 06/24/2009 11:43PMSubject: Re: [campsite-support] Campsite 3.3 "Speedy": Faster, Cheaper, Better!The guide says:
"Upgrading from Campsite 3.0.x, 3.1.x and 3.2.x:Drop the new sources over the existing install, open a browser and makea request for the publication home page:http://[site_name]The upgrade will be performed automatically when you make the firstrequest to the publication site or to the Campsite admin interface."
If I DROP new sources over the existing install, I will overwrite all. Is that the meaning?
Then upgrade and put back configuration files and templates and possibly something else?
How does it know the installation path if I overwrite all by dropping over the existing one?! (it's really tested many times, and that's how the ftp sw works overwritting things)
Now I was trying to replace most of files but leave templates intact. So, didn't work out. I did replace some configuration files... (install_conf.php & liveuser_configuration.php)
Putting back the previous files, hopefully my backup was full really without any corrupt files since can't keep the site BLANK either!
/G
On 25.6.2009, at 0.17, Generare Management Department wrote:
I was upgrading and put the files like asked and got a totally blank site. :(Apache error log tells:[Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP Notice:  Undefined index:  CacheEngine in /home/webadmin/
www.mywebserver.fi/html/classes/SystemPref.php
on line 54[Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP Fatal error:  Cannot redeclare templateerrorhandler() in /home/webadmin/
www.mywebserver.fi/html/template_engine/classes/SyntaxError.php
on line 137/GOn 24.6.2009, at 12.05,
sava.tatic@mdlf.org
wrote:Dear All,I am happy to announce the release of Campsite 3.3 "Speedy". "Speedy," is amajor upgrade, bringing--you've guessed right--more speed (up to a 5ximprovement), as well as many other enhancements.The main new features Campsite 3.3 brings are:   * New article-field types: switch and numeric   * Pluggable caching mechanism   * Much improved caching (list classes, all database access classes,images, object lists, template meta action list)   * Optimization of the ArticleType and ArticleTypeField classes   * Caching for static methods that return objects list   * Better log of all backend activity   * Better online template editor (Editarea)   * Global setting for resizing images inserted via the TinyMCE editor   * Upgrade of the TinyMCE editor to the latest stable version, with acompletely rewritten Paste from Word plugin   * Enhancements to the Article Type management screens   * Usability improvements to the Localizer tool (progress indicator andhighlights to string groups needing attention.For a full list of enhancements and bug fixes, please go here:http://trac.campware.org/campsite/query?status=closed&milestone=3.3.0
If you are a Campsite fan and would like to help it develop even faster,please take a minute to read our new How to Contribute section of theCampsite wiki (http://trac.campware.org/campsite/wiki/HowToContribute-Campsite)
.And, for starters, get the press release attached to the officialannouncement on the campware site(
http://http
://campware.org/en/camp/campsite_news/762/) and send it toanyone who may find it of interest. Let's get the word out!All the best (with the usual apologies for cross-posting),Sava

CAMPSITE - SUCCESSFUL UPGRADING VIA FTP SOFTWARE

Preparation

A. Please first take a backup as described here... or atleast by
downloading all files from your site implemation in the server to your
local folder.
B. if your site is online when starting to make this upgrade, please
put a temporary index.html on your site folder to say that you are on
maintenance process for a while. Then your process won't be seen or
interferred by anyone else in the world.

Upgrade process

1. In your FTP software open the local folder of Campsite (campsite/
implementation/site) and you should see all the folders needed and
select the ones that are in the picture below here:



If you can't see the attached picture here, please select in your
ftp's local view all the other folders and files but not "conf",
"bin", "admin-files", "templates" or index.php or admin.php.

2. Transfer selected files over your campsite files in the server
(once again only after you are sure you did take a backup copy of them).

3. Open local folder "conf" and put the content in the server inside a
folder with the same name (do not replace the folder, only add /
replace the files of the local folder, leave other files in the server
inside "conf" intact)

4. Open local folder "bin" and put the content in the server inside a
folder with the same name (do not replace the folder, only add /
replace the files of the local folder, leave other files in the server
inside "bin" intact). Note that the folder "bin" has your backup copy
if you have taken it in the beginning like the Campsite manual guides
you to do.

5. You can check that your folder "templates" still have your
personalized template files. No need to add there anything.

6. Check the permissions of your files index.php and admin.php. You
may need to give more permissions for the upgrade process than they
have (for example 755 or 777). If the ftp software refuses to change
the permissions, please remove these from your server side and upload
there new ones from the upgrade folder open on your local view and
then check the permissions again.

7. Open the folder "admin-files" locally and select everything else
except the folder "lang". Transfer selected files over your campsite
admin-files in the server.



8. You should be ready to go on your web browser and access the site.
An automatic process of upgrading should start quite shortly. If you
see only a blank site, you may need to check you followed exactly the
guide here or check the index.php settings for permissions again as
well. Please log in to your admin site and make sure all is fine there
as well. You should see the new version number (the proof of upgrade)
on the bottom of the admin site.

/G

On 25.6.2009, at 8.34, Generare Management Department wrote:

> Hi Sava!
>
> I think the major difficulty here for the normal user is that she or
> he will try to do it in "normal" way and the "normal" way to a
> typical user is to use FTP software for this, not unix commands via
> black and white screen. On the other hand, for a typical "nerd", the
> normal way may be via unix commands like "cp" etc.
>
> The guide nevertheless is not implicating in which way you should do
> it and if you do it via a normal "graphical" ftp software, you end
> up overwriting everything by following the guides.
>
> So, we should have a list of folders that should not be touched when
> upgrading, like "templates", and we take backup of those files.
> Also special, personalised edited other files should be in some kind
> of folder of "overrides" that we could easily save them. Then we
> should just put all the new version files in the server and after
> that take the not-meant-to-be-touched files, like "templates" back
> from our backup.
>
> And if you do this whole procedure for a live site, there should
> also be a guide saying to put some kind of temporary page meanwhile
> the procedure is over. Visitors can't be looking at a blank site or
> even worse, start to make the upgrade by clicking the appearing link.
>
> And by the way, the part of the guide that is for versions 3.x, it
> doesn't tell to make a backup either...
> Ok, I go ahead with my trial and error here, and report my experience.
>
> /G
>
> On 25.6.2009, at 1.58, sava.tatic@mdlf.org wrote:
>
>> Hi,
>>
>> If you used the campsite-backup script and if it said it completed
>> its job, then you are fine.
>>
>> Being an amateur system administrator myself, I've also found this
>> part of the instructions a bit cryptic (but I thought it was only
>> me). So we'll change it to something more copy-and-pastable very
>> soon. And once we sort your problems, please let's document how we
>> did it on your particular setup.
>>
>> The way I do it as root on my budding online empire (a BIG joke ,
>> a Centos machine with Plesk:
>>
>> cp -a /directorywhereiunpackedthenewtarball/campsite/
>> implementation/site/* /var/www/vhosts/myexampledomain.net/
>> httpdocs/
>>
>> You don't need to copy any configuration files or anything.
>>
>> What I found out is that sometimes I have to make sure that apache
>> user has all the required rights, which I achieve as root with:
>>
>> chown -R apache:apache /var/www/vhosts/myexampledomain.net/httpdocs
>>
>> This is again valid only under Centos. I hope someone more
>> knowledgeable will step in and provide a proper, yet not too
>> succint explanation.
>>
>> All the best,
>>
>> Sava
>>
>> p.s. and yes, sometimes I need to restart apache...
>>
>>
>>
>> -----Generare Management Department
>> wrote: -----
>>
>> To: campsite-support@campware.org
>> From: Generare Management Department
>> Date: 06/24/2009 11:43PM
>> Subject: Re: [campsite-support] Campsite 3.3 "Speedy": Faster,
>> Cheaper, Better!
>>
>> The guide says:
>>
>> "Upgrading from Campsite 3.0.x, 3.1.x and 3.2.x:
>>
>> Drop the new sources over the existing install, open a browser and
>> make
>> a request for the publication home page:
>> http://[site_name]
>>
>> The upgrade will be performed automatically when you make the first
>> request to the publication site or to the Campsite admin interface."
>>
>> If I DROP new sources over the existing install, I will overwrite
>> all. Is that the meaning?
>> Then upgrade and put back configuration files and templates and
>> possibly something else?
>> How does it know the installation path if I overwrite all by
>> dropping over the existing one?! (it's really tested many times,
>> and that's how the ftp sw works overwritting things)
>>
>> Now I was trying to replace most of files but leave templates
>> intact. So, didn't work out. I did replace some configuration
>> files... (install_conf.php & liveuser_configuration.php)
>>
>> Putting back the previous files, hopefully my backup was full
>> really without any corrupt files since can't keep the site BLANK
>> either!
>>
>> /G
>>
>> On 25.6.2009, at 0.17, Generare Management Department wrote:
>>
>>> I was upgrading and put the files like asked and got a totally
>>> blank site.
>>> Apache error log tells:
>>>
>>> [Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP
>>> Notice: Undefined index: CacheEngine in /home/webadmin/ www.mywebserver.fi/html/classes/SystemPref.php
>>> on line 54
>>> [Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP
>>> Fatal error: Cannot redeclare templateerrorhandler() in /home/
>>> webadmin/ www.mywebserver.fi/html/template_engine/classes/SyntaxError.php
>>> on line 137
>>>
>>> /G
>>>
>>> On 24.6.2009, at 12.05, sava.tatic@mdlf.org wrote:
>>>
>>>>
>>>> Dear All,
>>>>
>>>> I am happy to announce the release of Campsite 3.3 "Speedy".
>>>> "Speedy," is a
>>>> major upgrade, bringing--you've guessed right--more speed (up to
>>>> a 5x
>>>> improvement), as well as many other enhancements.
>>>>
>>>> The main new features Campsite 3.3 brings are:
>>>>
>>>> * New article-field types: switch and numeric
>>>> * Pluggable caching mechanism
>>>> * Much improved caching (list classes, all database access
>>>> classes,
>>>> images, object lists, template meta action list)
>>>> * Optimization of the ArticleType and ArticleTypeField classes
>>>> * Caching for static methods that return objects list
>>>> * Better log of all backend activity
>>>> * Better online template editor (Editarea)
>>>> * Global setting for resizing images inserted via the TinyMCE
>>>> editor
>>>> * Upgrade of the TinyMCE editor to the latest stable version,
>>>> with a
>>>> completely rewritten Paste from Word plugin
>>>> * Enhancements to the Article Type management screens
>>>> * Usability improvements to the Localizer tool (progress
>>>> indicator and
>>>> highlights to string groups needing attention.
>>>>
>>>> For a full list of enhancements and bug fixes, please go here:
>>>> http://trac.campware.org/campsite/query?status=closed&milestone=3.3.0
>>>>
>>>> If you are a Campsite fan and would like to help it develop even
>>>> faster,
>>>> please take a minute to read our new How to Contribute section of
>>>> the
>>>> Campsite wiki (
>>>> http://trac.campware.org/campsite/wiki/HowToContribute-Campsite) .
>>>>
>>>> And, for starters, get the press release attached to the official
>>>> announcement on the campware site
>>>> ( http://http ://campware.org/en/camp/campsite_news/762/) and
>>>> send it to
>>>> anyone who may find it of interest. Let's get the word out!
>>>>
>>>> All the best (with the usual apologies for cross-posting),
>>>>
>>>> Sava
>>>>

Yes, you must overwrite the old sources, that's what it means. It doesn't
say delete the extra files there. When you copy some new files/directories
over existing (the meaning of drop) any extra files will be left there, not
deleted - that's how a copy command works.

Mugur

On Thu, Jun 25, 2009 at 12:43 AM, Generare Management Department <
management@generare.com> wrote:

> The guide says:
>
> "Upgrading from Campsite 3.0.x, 3.1.x and 3.2.x:
>
> Drop the new sources over the existing install, open a browser and make
> a request for the publication home page:
> http://[site_name]
>
> The upgrade will be performed automatically when you make the first
> request to the publication site or to the Campsite admin interface."
>
>
> If I DROP new sources over the existing install, I will overwrite all. Is
> that the meaning?
> Then upgrade and put back configuration files and templates and possibly
> something else?
> How does it know the installation path if I overwrite all by dropping over
> the existing one?! (it's really tested many times, and that's how the ftp sw
> works overwritting things)
>
> Now I was trying to replace most of files but leave templates intact. So,
> didn't work out. I did replace some configuration files... (install_conf.php
> & liveuser_configuration.php)
>
> Putting back the previous files, hopefully my backup was full really
> without any corrupt files since can't keep the site BLANK either!
>
> /G
>
> On 25.6.2009, at 0.17, Generare Management Department wrote:
>
> I was upgrading and put the files like asked and got a totally blank site.
>
> Apache error log tells:
>
> [Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP Notice:
> Undefined index: CacheEngine in /home/webadmin/
> www.mywebserver.fi/html/classes/SystemPref.php on line 54
> [Thu Jun 25 00:14:11 2009] [error] [client 62.xx.xxx.xxx] PHP Fatal error:
> Cannot redeclare templateerrorhandler() in /home/webadmin/
> www.mywebserver.fi/html/template_engine/classes/SyntaxError.php on line
> 137
>
> /G
>
> On 24.6.2009, at 12.05, sava.tatic@mdlf.org wrote:
>
>
> Dear All,
>
>
> I am happy to announce the release of Campsite 3.3 "Speedy". "Speedy," is a
>
> major upgrade, bringing--you've guessed right--more speed (up to a 5x
>
> improvement), as well as many other enhancements.
>
>
> The main new features Campsite 3.3 brings are:
>
>
> * New article-field types: switch and numeric
>
> * Pluggable caching mechanism
>
> * Much improved caching (list classes, all database access classes,
>
> images, object lists, template meta action list)
>
> * Optimization of the ArticleType and ArticleTypeField classes
>
> * Caching for static methods that return objects list
>
> * Better log of all backend activity
>
> * Better online template editor (Editarea)
>
> * Global setting for resizing images inserted via the TinyMCE editor
>
> * Upgrade of the TinyMCE editor to the latest stable version, with a
>
> completely rewritten Paste from Word plugin
>
> * Enhancements to the Article Type management screens
>
> * Usability improvements to the Localizer tool (progress indicator and
>
> highlights to string groups needing attention.
>
>
> For a full list of enhancements and bug fixes, please go here:
>
> http://trac.campware.org/campsite/query?status=closed&milestone=3.3.0
>
>
> If you are a Campsite fan and would like to help it develop even faster,
>
> please take a minute to read our new How to Contribute section of the
>
> Campsite wiki (
>
> http://trac.campware.org/campsite/wiki/HowToContribute-Campsite)
> .
>
>
> And, for starters, get the press release attached to the official
>
> announcement on the campware site
>
> (http://http://campware.org/en/camp/campsite_news/762/) and send it to
>
> anyone who may find it of interest. Let's get the word out!
>
>
> All the best (with the usual apologies for cross-posting),
>
>
> Sava
>
>
>
>
>
>

Gene,

This is great. Could you just update it so it reflects Mugur's corrections?
Even better, I could give you access to the Wiki (we keep it closed to keep
away the lowest form of human life on earth: the wiki spammer), so you can
maintain it there in the future.

What do you say?

Sava



From: Generare Management Department

To: campsite-support@campware.org

Date: 06/25/2009 12:58 PM

Subject: Re: [campsite-support] Campsite 3.3 "Speedy": Faster, Cheaper, Better!






CAMPSITE - SUCCESSFUL UPGRADING VIA FTP SOFTWARE

Preparation

A. Please first take a backup as described here... or atleast by
downloading all files from your site implemation in the server to your
local folder.
B. if your site is online when starting to make this upgrade, please put a
temporary index.html on your site folder to say that you are on maintenance
process for a while. Then your process won't be seen or interferred by
anyone else in the world.

Upgrade process

1. In your FTP software open the local folder of Campsite
(campsite/implementation/site) and you should see all the folders needed
and select the ones that are in the picture below here:



If you can't see the attached picture here, please select in your ftp's
local view all the other folders and files but not "conf", "bin",
"admin-files", "templates" or index.php or admin.php.

2. Transfer selected files over your campsite files in the server (once
again only after you are sure you did take a backup copy of them).

3. Open local folder "conf" and put the content in the server inside a
folder with the same name (do not replace the folder, only add / replace
the files of the local folder, leave other files in the server inside
"conf" intact)

4. Open local folder "bin" and put the content in the server inside a
folder with the same name (do not replace the folder, only add / replace
the files of the local folder, leave other files in the server inside "bin"
intact). Note that the folder "bin" has your backup copy if you have taken
it in the beginning like the Campsite manual guides you to do.

5. You can check that your folder "templates" still have your personalized
template files. No need to add there anything.

6. Check the permissions of your files index.php and admin.php. You may
need to give more permissions for the upgrade process than they have (for
example 755 or 777). If the ftp software refuses to change the permissions,
please remove these from your server side and upload there new ones from
the upgrade folder open on your local view and then check the permissions
again.

7. Open the folder "admin-files" locally and select everything else except
the folder "lang". Transfer selected files over your campsite admin-files
in the server.



8. You should be ready to go on your web browser and access the site. An
automatic process of upgrading should start quite shortly. If you see only
a blank site, you may need to check you followed exactly the guide here or
check the index.php settings for permissions again as well. Please log in
to your admin site and make sure all is fine there as well. You should see
the new version number (the proof of upgrade) on the bottom of the admin
site.

/G

On 25.6.2009, at 8.34, Generare Management Department wrote:

Hi Sava!

I think the major difficulty here for the normal user is that she or
he will try to do it in "normal" way and the "normal" way to a
typical user is to use FTP software for this, not unix commands via
black and white screen. On the other hand, for a typical "nerd", the
normal way may be via unix commands like "cp" etc.

The guide nevertheless is not implicating in which way you should do
it and if you do it via a normal "graphical" ftp software, you end up
overwriting everything by following the guides.

So, we should have a list of folders that should not be touched when
upgrading, like "templates", and we take backup of those files.
Also special, personalised edited other files should be in some kind
of folder of "overrides" that we could easily save them. Then we
should just put all the new version files in the server and after
that take the not-meant-to-be-touched files, like "templates" back
from our backup.

And if you do this whole procedure for a live site, there should also
be a guide saying to put some kind of temporary page meanwhile the
procedure is over. Visitors can't be looking at a blank site or even
worse, start to make the upgrade by clicking the appearing link.

And by the way, the part of the guide that is for versions 3.x, it
doesn't tell to make a backup either...
Ok, I go ahead with my trial and error here, and report my
experience.

/G

On 25.6.2009, at 1.58, sava.tatic@mdlf.org wrote:

Hi,

If you used the campsite-backup script and if it said it
completed its job, then you are fine.

Being an amateur system administrator myself, I've also found
this part of the instructions a bit cryptic (but I thought it
was only me). So we'll change it to something more
copy-and-pastable very soon. And once we sort your problems,
please let's document how we did it on your particular setup.

The way I do it as root on my budding online empire (a BIG
joke , a Centos machine with Plesk:

cp
-a /directorywhereiunpackedthenewtarball/campsite/implementation/site/* /var/www/vhosts/myexampledomain.net/httpdocs/


You don't need to copy any configuration files or anything.

What I found out is that sometimes I have to make sure that
apache user has all the required rights, which I achieve as
root with:

chown -R
apache:apache /var/www/vhosts/myexampledomain.net/httpdocs

This is again valid only under Centos. I hope someone more
knowledgeable will step in and provide a proper, yet not too
succint explanation.

All the best,

Sava

p.s. and yes, sometimes I need to restart apache...



-----Generare Management Department
wrote: -----

To: campsite-support@campware.org
From: Generare Management Department
Date: 06/24/2009 11:43PM
Subject: Re: [campsite-support] Campsite 3.3 "Speedy": Faster,
Cheaper, Better!

The guide says:

"Upgrading from Campsite 3.0.x, 3.1.x and 3.2.x:

Drop the new sources over the existing install, open a
browser and make
a request for the publication home page:
http://[site_name]

The upgrade will be performed automatically when you make
the first
request to the publication site or to the Campsite admin
interface."

If I DROP new sources over the existing install, I will
overwrite all. Is that the meaning?
Then upgrade and put back configuration files and templates
and possibly something else?
How does it know the installation path if I overwrite all by
dropping over the existing one?! (it's really tested many
times, and that's how the ftp sw works overwritting things)

Now I was trying to replace most of files but leave templates
intact. So, didn't work out. I did replace some configuration
files... (install_conf.php & liveuser_configuration.php)

Putting back the previous files, hopefully my backup was full
really without any corrupt files since can't keep the site
BLANK either!

/G

On 25.6.2009, at 0.17, Generare Management Department wrote:

I was upgrading and put the files like asked and got a
totally blank site.
Apache error log tells:

[Thu Jun 25 00:14:11 2009] [error] [client
62.xx.xxx.xxx] PHP Notice: Undefined index:
CacheEngine in /home/webadmin/
www.mywebserver.fi/html/classes/SystemPref.php on line
54
[Thu Jun 25 00:14:11 2009] [error] [client
62.xx.xxx.xxx] PHP Fatal error: Cannot redeclare
templateerrorhandler() in /home/webadmin/
www.mywebserver.fi/html/template_engine/classes/SyntaxError.php

on line 137

/G

On 24.6.2009, at 12.05, sava.tatic@mdlf.org wrote:


Dear All,

I am happy to announce the release of Campsite 3.3
"Speedy". "Speedy," is a
major upgrade, bringing--you've guessed
right--more speed (up to a 5x
improvement), as well as many other enhancements.

The main new features Campsite 3.3 brings are:

* New article-field types: switch and numeric
* Pluggable caching mechanism
* Much improved caching (list classes, all
database access classes,
images, object lists, template meta action list)
* Optimization of the ArticleType and
ArticleTypeField classes
* Caching for static methods that return objects
list
* Better log of all backend activity
* Better online template editor (Editarea)
* Global setting for resizing images inserted
via the TinyMCE editor
* Upgrade of the TinyMCE editor to the latest
stable version, with a
completely rewritten Paste from Word plugin
* Enhancements to the Article Type management
screens
* Usability improvements to the Localizer tool
(progress indicator and
highlights to string groups needing attention.

For a full list of enhancements and bug fixes,
please go here:
http://trac.campware.org/campsite/query?status=closed&milestone=3.3.0


If you are a Campsite fan and would like to help
it develop even faster,
please take a minute to read our new How to
Contribute section of the
Campsite wiki (
http://trac.campware.org/campsite/wiki/HowToContribute-Campsite)

.

And, for starters, get the press release attached
to the official
announcement on the campware site
( http://http
://campware.org/en/camp/campsite_news/762/) and
send it to
anyone who may find it of interest. Let's get the
word out!

All the best (with the usual apologies for
cross-posting),

Sava