You are reading the Drake CMS Official Forums archive, available for historical purposes only.
Drake CMS has been rebranded into Lanius CMS, visit the new Lanius CMS Official Forums if you need support about Lanius CMS or Drake CMS -> Lanius CMS migration.
I wanted to update from version "Drake v0.3.3 Beta
rev.1387" to version 0.3.4. I started the update Mangager
and selechted: Install from an url.
Then I received
the following error: Quote:
Fatal error: Allowed memory size of 8388608 bytes
exhausted (tried to allocate 24 bytes) in
/home/jeakxdby/www.jeak.de/Subpages/siedlerchr/drake/admin/classe
s/phppatcher.php
on
What does this mean?
dit: And now I can't
go to any site, I get the following error
==Server== Drake v0.3.3 Beta rev.1387 Server:
Apache PHP version: 4.4.4-pl6-gentoo Database:
gladius Protocol: HTTP/1.1 Host: jeak.de OS: Linux
serv06 2.6.12-vs2.0-gentoo-r1 #2 Mon Dec 12 21:28:00 CET 2005
x86_64
==Client== User agent: Mozilla/4.0
(compatible; MSIE 6.0; Windows NT 5.1; Avant Browser; Avant
Browser; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Accept-charset: Accept-language: de
I
wanted to update from version "Drake v0.3.3 Beta rev.1387" to
version 0.3.4. I started the update Mangager and selechted:
Install from an url.
Then I received the following
error: Quote:
Fatal
error: Allowed memory size of 8388608 bytes exhausted (tried to
allocate 24 bytes) in
/home/jeakxdby/www.jeak.de/Subpages/siedlerchr/drake/admin/classe
s/phppatcher.php
on
What does this mean?
Siedlerchr your
Drake CMS installation is now broken because the patching process
aborted due to a memory constraint of your server (about 8Mb,
which is a low value in my opinion). In future I will make the
patching process (which is a part of the update process) less
memory consumptive, however now to recover your website you
should download the latest Drake CMS package and restore the
database backup in the newly installed Drake CMS. If you have not
done any database backup, you might try to overwrite the Drake
CMS installation with the new files (except the install folder,
which is not needed if you are not going to re-install) but this
might lead to instability if your previous version was not
compatible. Don't worry, we're gonna help you to restore
everything up as previously was.
What version of Drake
CMS were you updating from? v0.3.4?
Siedlerchr
Re:Update problem
05 March 2007 17:08
Anonymous
I wanted to update from v0.3.3 to 0.3.4 . My idea was to
update first to 0.3.4 and then to 0.3.5...
I didn't do
a backup before.. The next time I will...
I
think I upload the newest verion on the server and I will
see..
I've also got a question: I read about German
language files, where do I find them?
Quote:
...about 8Mb, which
is a low value in my opinion)
I was glad to see, that
Drake works with the server!! I'm using the Gladius DB,
because there is no sql database on the server..
legolas558
Re:Update problem
06 March 2007 07:07
Anonymous
Siedlerchr wrote: Quote:
I wanted to update
from v0.3.3 to 0.3.4 . My idea was to update first to 0.3.4
and then to 0.3.5...
I didn't do a backup before.. The
next time I will...
Sure you can update incrementally but a
backup is always suggested if you have important data! Quote:
I think I
upload the newest version on the server and I will see..
Ok but first delete the old files (or at least the
private/drake folder) Quote:
I've also got a question: I read about German
language files, where do I find them?
They are
not yet released but available for everybody on the SVN
repository, read this and this, but it is not so easy!
If you are not able to get the files just wait for the official
release
Quote:
Quote:
...about 8Mb, which
is a low value in my opinion)
I was glad to see, that
Drake works with the server!! I'm using the Gladius DB,
because there is no sql database on the server..
Yes
it
is our goal to have Drake CMS work with almost everything and
keep it fast; however I was talking about the memory limit, not
the database
it
is our goal to have Drake CMS work with almost everything and
keep it fast; however I was talking about the memory limit, not
the database 