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 have got a problem updating Drake v. 0.4.0 to
0.4.1.
Either I choose Remote Update oder Fileupload
this Message appears:
Quote:
Fatal error: Allowed memory size
of 8388608 bytes exhausted (tried to allocate 512 bytes) in
::/admin/classes/phppatcher.php on line 222
How
can I update Drake without uploading the new verison and deleting
the old?
Regards, Siedlerchr
legolas558
Re : Update problem
17 May 2007 22:46
Anonymous
If you cannot raise the memory limit and if you do not want to
wait for the full patch (which should soon be released through
SF.net file download service) you will need to:
1.
create a database backup from your Drake CMS v0.4.0 2.
copy the content of folders private/downloads/, images/ and any
other custom file 3. install Drake CMS v0.4.1 4.
restore the database backup file 5. copy back the other
files to the previous location
I will modify Drake CMS
so that this error wont happen in future updates
siedlerchr
Re : Update problem
17 May 2007 23:06
Anonymous
I will wait for the full patch...
And, this time I did
an backup...
What is the difference form this patch to
the full patch?
Regards, Siedlerchr
legolas558
Re : Update problem
17 May 2007 23:31
Anonymous
Quote:
I will wait for
the full patch...
And, this time I did an
backup...
It is always a good safety measure to make
backups before updating
Quote:
What is the difference form this patch to the full
patch?
The full patch will copy full files
instead of trying to patch the existing files; this will require
less memory for the operation and also allow update of customized
Drake CMS versions (although the customizations will be
overwritten). You will read more about them on the apposite news.
siedlerchr
Re : Update problem
24 May 2007 19:43
Anonymous
Now v.0.4.02 is out and I have still the old version... When
do you create/post this patch ??
Regards Christoph
trex1512
Re : Update problem
24 May 2007 20:51
Anonymous
Hi
If you mean the 0.4.1 patch it was posted as per
the news item..."Overwrite patch to v0.4.1 released"
The two patches were available from the download area of
SF
The News release described how to do a manual
update using the overwrite patch.
The patch was
released on Thursday, 17 May 2007.
The overwrite
patchs for 0.4.0->0.4.1 and 0.4.1->0.4.2 are available Here
If we can
help further let us know...
siedlerchr
Re : Update problem
24 May 2007 23:13
Anonymous
Ok, I found the overwrite patch from 0.4.0 to 0.4.1
But there is a "raw" patch from 0.4.1 to 0.4.2..
Is this a difference?
trex1512
Re : Update problem
24 May 2007 23:42
Anonymous
Hi
Apply the 0.4.0->0.4.1 overwrite patch first and
attempt to carry out the online update to 0.4.2.
If
you are unable to complete the update to 0.4.2 using the online
update process then you can attempt to carryout the update using
the local path option, you will have to download the standard
patch and then upload it to a temp directory in your site.
OR go straight to the manual overwrite update process as
described, use the update_from_v0.4.1_to_v0.4.2-raw_patch.zip as
you would the overwrite patch...
With this update a
number of fixes have been implemented in an effort to ensure that
the online update process would always be avaiable.
siedlerchr
Re : Update problem
24 May 2007 23:55
Anonymous
I chose the overwrite patch from 0.4.0 to 0.4.1, but I still get
the error described in my first post.
You told me,
that the overwrite patch will take less memory than the normal
patch...
Here is the error which appeared while
installing the overwrite patch..
Quote:
Fatal error: Allowed
memory size of 8388608 bytes exhausted (tried to allocate 71
bytes) in .../admin/classes/phppatcher.php on line 222
trex1512
Re : Update problem
25 May 2007 05:10
Anonymous
Quote:
I chose the
overwrite patch from 0.4.0 to 0.4.1, but I still get the error
described in my first post.
The procedures to
use the overwrite patch were detailed in the news item described
above and Here.
Quote:
You told me, that the
overwrite patch will take less memory than the normal patch...
It does, unfortunately the system you are
trying to install on appears to have a very restrictive
enviroment
Did you try the install from a Local Path
option? It uses slightly less system resources.
Quote:
Fatal error: Allowed
memory size of 8388608 bytes exhausted (tried to allocate 71
bytes) in .../admin/classes/phppatcher.php on line 222
Last option is to read the instructions Here on how to carry out a
manual update on systems that will not allow other forms of
update.
A bit more work unfortunately but at least
will preserve your installed data etc from your current
install.
Stay with it, there will be a way to get it
done, you only have to look at the Official Site here to see
that, a very restrictive enviroment.
See how you go
with the above, good luck.
legolas558
Re : Update problem
25 May 2007 05:41
Anonymous
Quote:
Ok, I found the
overwrite patch from 0.4.0 to 0.4.1
But there is a
"raw" patch from 0.4.1 to 0.4.2..
Is this a
difference?
No there isn't, I
actually chose a different naming (now "raw") hoping
that it is more correct.
Sorry for the confusion I
generated
siedlerchr
Re : Update problem
25 May 2007 19:58
Anonymous
I tried to install from my system...
What do you mean
wirht local path? Do you mean this option: installing from
the root folder of drake?
PS: I love Drake CMS because
of its simplicity and because of the well arranged admin
menue...
legolas558
Re : Update problem
25 May 2007 20:37
Anonymous
Quote:
I tried to
install from my system...
What do you mean wirht local
path? Do you mean this option: installing from the root
folder of drake?
Yes, the third tab
Quote:
PS: I
love Drake CMS because of its simplicity and because of the well
arranged admin menue...
Yeah actually if you look at it it is simple, it is just the
documentation wich is lacking and the english labels which could
be improved in their wording..
siedlerchr
Re : Update problem
25 May 2007 23:25
Anonymous
Quote:
Yeah actually if you look at it it is simple, it is just the
documentation wich is lacking and the english labels which could
be improved in their wording..
Well, I think the admin menue is very easy to understand
for me, I'm from Germany but I can understand nearly everything..
I will test the installation from the root folder in drake
legolas558
Re : Update problem
26 May 2007 00:01
Anonymous
Good news for you: HeliG is going to keep help with the German
translation, so we should soon have also an updated German
language pack
siedlerchr
Re : Update problem
26 May 2007 15:14
Anonymous
Quote:
Good news for
you: HeliG is going to keep help with the German translation, so
we should soon have also an updated German language pack
This are really good news but my problem
ist still alive While updating with the raw patch a lot of errors appeared an
now my frontpage is, hm, how could I explain it.. Look Here
legolas558
Re : Update problem
26 May 2007 15:56
Anonymous
Quote:
While updating
with the raw patch a lot of errors appeared an now my frontpage
is, hm, how could I explain it.. Look Here
Now you should
get the full archive of v0.4.2 and overwrite (via FTP) all the
files. It will work.
I am sorry for all the troubles
you got
siedlerchr
Re : Update problem
26 May 2007 16:11
Anonymous
OK, I will test it... Thx for your support
siedlerchr
Re : Update problem
26 May 2007 17:16
Anonymous
Now I have verion 0.4.2 and wanted to update the hotfix, but an
error appears, no Hask, just only this:
Quote:
Drake CMS Site
Filesystem operation failed Failed to create
directory __________________________ If you cannot
solve the error by its message, check that the correct write
permissions are set on the target path
What
should I do now?
legolas558
Re : Update problem
30 May 2007 18:45
Anonymous
You database should be already updated, try to overwrite the
files manually.
Hopefully these issues will be gone
with the next version
Update problem 
but my problem
ist still alive 
