I am a litle bit confused about the installation procedure for PostNuke 0.764. I try to upgrade from 0.762. The manual tells me at point nr 6:
Remove ALL of the files in your existing PostNuke distribution.
ALL of them. Put your new distribution in its place.
If you had 3rd party modules and/or blocks installed, copy them from your backup into your new installation NOW, *before* continuing the upgrade process.

On the other hand under point nr 5 the manual says:

you're upgrading from an earlier release containing the Xanthia and pnRender modules, ensure that all cache and compile directories in pnTemp are emptied.

Well my question: Should I erase all directories and If so whats the meaning of to empty all cache and compile directories when they will be deleted in the next step.

I have tried to erase all directories as the manual says but later upgrades failes. I therefore asume that I do something wrong.

It does seem a little redundant, this may due to the idea that it is recommended that the pnTemp directory be placed outside you're web root. Regardless if your pnTemp directory is in the default location it should be deleted and replaced with the new and ensure that pnTemp and sub-directories are world writeable (777).

Where does the upgrade fail? What error message do you get?

--
Under Construction!

I halts with the following message:

Fatal error: Call to a member function on a non-object in /data/members/paid/v/e/verdis.se/htdocs/www/install/pn64.php on line 416

Do you know who one can solve this.

I`m trying to upgrade from 0.762 to 0.764. In the upgradepage where you choose version to upgrade from the latest version to upgrade from is 0.72. Why?

You don't have to use any upgrade.php file.

Just copy the new 0.764 files to you existing 0.762 installation.
No more actions or functions needed.

It will only takes a few seconds. Upload ==> done

--
Carsten-volmer.de [40]
Saga-Treff.de [41]

Thanks for the information. I´m a beginner in PostNuke. When you say that its only to copy the new 0.764 files. Do you mean a total replacement with the files from the new files or is a specific directory or file/s. When i do a total replacement of all files and directorys the connection to the database is lost. I could not expect any thing else. So the question is wich files do i replace. I think PostNuke seems promissing, but i am missing a good documentation [47] of the system.

Greetings
Jorgen Hanak

Sorry, it's so easy to assume that people know the basics when you've done it so many times. From 0.762 to 0.764 there are no DB changes so it's just a matter of replacing all files except third party moduels and config.php (which holds your DB connection info).

So...

1. Backup files.

2. Set your theme to extralite.

3. Clear/delete all files.

4. Place third party modules back into the modules directory as well as any custom blocks you may have into the includes/blocks directory. If you're using a custom/third party theme add that back into the themes directory at this point too.

5. Replace config.php with your backup copy (you might want to compare the old with the new, but I don't believe there were any changes to the entries in this file for this upgrade).

That should be it. I think step 5 is all you're missing at this point but there's the whole thing anyway.



This issue is painfully known and there is a team dedicated to documentation [54] at this point, albeit this will be for 0.8 forward. That being said this forum works well for any questions you may have.



edited by: Topiatic, Feb 11, 2008 - 09:13 AM

--
Under Construction!

I have done exactly as you described but still gets the message "Problem in Database Connection. There must be something else that needs to be adjusted. It works fine with the same config.php when i shift back to the old version. There is not any structrural diffrence between the new version and my old config.php except configdata as dbuname, dbpass, etc.

I tried to change config.php from encoded='1' to encoded='0' and typed uname and dpuname and dbpass in clear text. But still get the result "Problem in Database Connection". The system works normal when i shift back to the old version, as I mention before.
Is there a number of specific corefiles listed somewhere in postsnuke? In that case i could shift back to the previous version and update listed files one by one and check if and where the system fails to contact the database.



edited by: jnh1115, Feb 12, 2008 - 09:45 AM

Use you old version of config.php. Otherwise I am not sure what you are asking... sorry.


--
David Pahl
Zikula Support Team

I am using my old config.php but gets the message "Problem in database connection" anyway. I have checked that the database is running. When i shift back to my original version () it´s working fine. My question: Is there any other file then config.sys that could interfer in the connection to the database?

I think there is come confusion here.

If your original file works, why don't you just use that? (nevermind the config.old or whatever it is)


--
David Pahl
Zikula Support Team

I wanted to upgrade from version 0.762 to 0.764. Herr. Vorragend kindly told me "Just copy the new 0.764 files to you existing 0.762 installation. No more actions or functions needed". He forgott to tell me about config.php. I have tried to installed 0.764 this way and then copy config.php from my 0.762 installation to the new 0.764. But it does not work. When i move back to version 0.762 it`s possible to log on again. I have moved to and from now several times but allaways get "Problems in Database Connection" with version 0.764 despite that i use the same config.php. Thats way i ask if there is any other files involved in the connection to the database.

Yup. It is a file upgrade only.

There are no other configurable files involved in DB connect.. but indeed there are others. You may have missing or corrupt files -- this can happen if you are use FTP.



--
David Pahl
Zikula Support Team