Install error during fresh install of 0.7.6.3

a fresh install produces the following error:

http://img245.images…installerrorrx2.jpg


any hints? ;)
Fresh install of .7.6.3 went perfect here

--
Doe Maar Freak
Which package did you download?

--
itbegins.co.uk - Zikula Consulting

birtwistle.me.uk - Personal Blog


Please read the Support Guide
i downloaded the zip-package ...

http://noc.postnuke.com/frs/download.php/1288/PostNuke-0.763.zip
i just downloaded the tar.gz package
http://noc.postnuke.com/frs/download.php/1289/PostNuke-0.763.tar.gz
i get the same error.

i installed 0762! on the same server and it installs fine ^^

i am "glad" that another user is reporting this problem!

it seems not to be an "upload" problem.
I had the same problem. After reviewing the install instructions, it states the following:

Quote

For security reasons, we recommend you to have magic_quotes set to ON and register_globals
set to OFF in php.ini, although PostNuke will work regardless of these settings.


I'm not so sure it is optional for the install. I added the following line to my .htaccess file for Apache:
php_flag register_globals off

Hopefully someone with more experience can confirm this is an appropriate thing to do whether it is in php.ini or .htaccess (in a hosted environment).
I think with php.ini it would be just be register_globals off
Also, the the php.ini might have to be in every directory that you want it to affect, at least on phpsuexec servers. Fortunately, there are scripts that can copy it for you. icon_biggrin
For my host that ran PHP as an apache module, I think I used php_value register_globals 0 and php_value magic_quotes_gpc 1 in the .htaccess
However, if what you mentioned seems to work, don't bother with anything else.



edited by: Thug21, Oct 15, 2006 - 05:45 PM
icon_rolleyes

a .htaccess file with "php_flag register_globals Off" in the postnuke root solved the problem here.

thx a lot
We have a new pnAPI.php for the .7x series that emulates register_globals = off, which should solve this issue if the htaccess method doesn't work.

--
itbegins.co.uk - Zikula Consulting

birtwistle.me.uk - Personal Blog


Please read the Support Guide
Thats great news as I don't know of a host that doesn't have register_globals on by default.

beyss

icon_rolleyes

a .htaccess file with "php_flag register_globals Off" in the postnuke root solved the problem here.

I don't believe that works on every host. Glad it did for you though. icon_smile



edited by: Thug21, Oct 15, 2006 - 05:47 PM
I'm having the same problem. modifying the .htaccess file doesn't work and always produces error 500. I tried the new version of pnAPI.php and still get the exactly same error is you were getting originally. My server does not use a php.ini file to modify either.

This is the contents of line 498:
'style:=1\ndisplaymodules:=0\ndisplaywaiting:=0\ncontent:=index.php|$mainblock_block_home|$mainblock_block_homealt.LINESPLITuser.php|$mainblock_block_user|$mainblock_block_useralt.LINESPLITadmin.php|$mainblock_block_admin|$mainblock_block_adminalt.LINESPLITuser.php?module=User&op=logout|$mainblock_block_userexit|$mainblock_block_userexitalt.LINESPLIT|$modules|LINESPLIT[Downloads]|$mainblock_block_dl|$mainblock_block_dlalt.LINESPLIT[FAQ]|$mainblock_block_faq|$mainblock_block_faqalt.LINESPLIT[News]|$mainblock_block_news|$mainblock_block_newsalt.LINESPLIT[Reviews]|$mainblock_block_rws|$mainblock_block_rwsalt.LINESPLIT[Search]|$mainblock_block_search|$mainblock_block_searchalt.LINESPLIT[Sections]|$mainblock_block_sections|$mainblock_block_sectionsalt.LINESPLIT[Submit_News]|$mainblock_block_snews|$mainblock_block_snewsalt.LINESPLIT[Topics]|$mainblock_block_topics|$mainblock_block_topicsalt.LINESPLIT[Web_Links]|$mainblock_block_wlinks|$mainblock_block_wlinksalt.','',0, 'l','1.0',1,0,20011122090726,'', 1 , 1)")
IMHO there was no new "pnAPI.php" since the initial release of 0.763 ^^

the only thing you can do is ask your hoster for help, am i right with this?

my entry to the bug tracker was "closed" -_-

http://noc.postnuke.com/tracker/index.php?func=detail&aid=3465&group_id=5&atid=101



edited by: beyss, Oct 15, 2006 - 10:07 PM

beyss

my entry to the bug tracker was "closed" -_-


I'm going to take a wild guess here and say that it was closed because:

Quote

Date: 2006-10-15 04:16
Sender: Beyss

a .htaccess file with "php_flag register_globals Off"
in the postnuke root solved the problem here.


--
"Inside every large script (Zikula) is another script (Pagesetter) struggling to get out."

IE6DWX Logo
you might be right :)

but the "bug" was reported by other users that don't have a workaround for that - and it makes it still impossible to install 0.763 for them - or am i wrong with that? ;)

Quote

Date: 2006-10-15 04:16
Sender: Beyss

a .htaccess file with "php_flag register_globals Off"
in the postnuke root solved the problem here.


this solved the problem for ME ^^
The bug is closed because a fix is in SVN - you need a new pnAPI.php

--
itbegins.co.uk - Zikula Consulting

birtwistle.me.uk - Personal Blog


Please read the Support Guide
perhaps i am a little slow today ;)

In another topic you mentioned this file ...

HammerHead

In that case, you probably can't use the htaccess method. Instead, download a new pnAPI.php from SVN.


but this is exactly the same as the one that was shipped with the 0.763 release ^^
I have also this error:
Fatal error: Call to a member function on a non-object in localhost/postnuke/html/install/modify_config.php on line 498

I've tried setting register_globals in php.ini to off... no progress still.

but when I tried the one suggested by Thug21... IT WORKED!

Quote

I think I used php_value register_globals 0 and php_value magic_quotes_gpc 1 in the .htaccess


Thanks a lot! icon_biggrin

Hallo everyone,

Just made a fresh installation with the newest Postnuke version and encountered the exact same problem. Though I must say I never had issues before with older versions.

Could you please be so kind and explain the necessary changes in easy-to-follow steps. It would be nice to hear something like "open file A with editor and change line bla bla bla"

Thanks! icon_smile



edited by: 1aschnitzel, Oct 18, 2006 - 04:23 PM
There are a number of solutions to this problem.

If you run your own server, or PHP is running as a cgi on your hosted server:

Open php.ini, find the line

Code

register_globals = On

and change it to:

Code

register_globals = Off


If you don't run your own server, and PHP is running as an apache module, create an .htaccess file (or edit your existing one) and add:

Code

php_flag register_globals Off


If this generates an error 500, then talk to your host. If they won't or can't disable register_globals, then you will need an updated pnAPI.php from SVN once a particular bug is fixed.


--
itbegins.co.uk - Zikula Consulting

birtwistle.me.uk - Personal Blog


Please read the Support Guide
When I read your post I was first kind of anoyed.. cause.. anyone knows that I cant create a file starting with a dot! But I trusted in your wisdom and the installation worked perfectly!!!! icon_razz

Just one last question: I put the .htaccess in the root directory of my server. Is that okay? Or was I supposed to put it into the folder where PN was installed? Should I delete it afterwards? Does this file create any security gap? (just answer briefly please, you already helped me wonderfully!)

1aschnitzel

When I read your post I was first kind of anoyed.. cause.. anyone knows that I cant create a file starting with a dot! But I trusted in your wisdom and the installation worked perfectly!!!! icon_razz


:) .htaccess files tell apache what to do within certain directories, you can change the way apache handles tasks... you can pasword protect directories, redirect, use SSI.. ect. ect.

Your root directory, your PN root are both find choices. Your PN root is the better choice.. because you really only want to change the behavior of apache for your PN.


--
David Pahl
Zikula Support Team

HammerHead

There are a number of solutions to this problem.

If you run your own server, or PHP is running as a cgi on your hosted server:

Open php.ini, find the line

Code

register_globals = On

and change it to:

Code

register_globals = Off


If you don't run your own server, and PHP is running as an apache module, create an .htaccess file (or edit your existing one) and add:

Code

php_flag register_globals Off


If this generates an error 500, then talk to your host. If they won't or can't disable register_globals, then you will need an updated pnAPI.php from SVN once a particular bug is fixed.


Edit** Follow Simons advice as you want the globals off, but if you can not install with the above mentioned..then proceed..

Of course, you can always install your site manually, bypassing the script. I switched my globals 'on' in my php.ini. Ran the script.. got the error, dumped my database... dumped the packaged database manually. The script till that point already... changed my config.php... and did some quick testing around the site.. no issues to report.

And of course you can get some detailed instructions at http://pnSetup.com .




edited by: AmmoDump, Oct 18, 2006 - 02:56 PM

--
David Pahl
Zikula Support Team
This problem was plaguing me as well. I solved it by creating a php.ini file in the root of my postnuke install with the following settings:

Code

register_globals=off
post_max_size = 20M
memory_limit = 80M
upload_max_filesize = 20M

max_execution_time = 120
expose_php=off

jeff300

This problem was plaguing me as well. I solved it by creating a php.ini file in the root of my postnuke install with the following settings:

Code

register_globals=off
post_max_size = 20M
memory_limit = 80M
upload_max_filesize = 20M

max_execution_time = 120
expose_php=off



Creating a pnp.ini in you postnuke root ???


--

HammerHead

There are a number of solutions to this problem.

If you run your own server, or PHP is running as a cgi on your hosted server:

Open php.ini, find the line

Code

register_globals = On

and change it to:

Code

register_globals = Off


If you don't run your own server, and PHP is running as an apache module, create an .htaccess file (or edit your existing one) and add:

Code

php_flag register_globals Off


If this generates an error 500, then talk to your host. If they won't or can't disable register_globals, then you will need an updated pnAPI.php from SVN once a particular bug is fixed.



I'm having trouble figuring out how to tell the difference between which solution I should be using. I'm not terribly familiar with the differences in the type of servers. I have no php.ini file anywhere but I do have a .htaccess file which I modified and just put "php_flag register_globals Off" at the end of the file but I instantly get error 500. I tried updating the pnAPI.php from SVN but got even more errors. How can I tell which direction I should be approaching this from so I'm not wasting any more of my time?
It's possible your host has disabled php_flag, so talk to them about the problem. They should be able to help you.

--
itbegins.co.uk - Zikula Consulting

birtwistle.me.uk - Personal Blog


Please read the Support Guide
Ok, I was having this problem as well. The .httaccess file thing was giving me the error page. I'm on godaddy shared hosting so I had no access to my php.ini file so I called support and they told me: "Just create your own file, write register_globals = Off, save it as php.ini, and upload it to your root directory"

DUH, it worked like a charm.
I am getting this same frustrating error. It is not the server settings it is this new .763. I installed four .762 sites last week on the same server without any failings - but the same cannot be said of this new package. I installed .762 on over 40 sites in the past three months - never had a single problem.

I've tried every fix on these forums and none work. Frustrating to say the least.

Where can I download the old .762?

--
My PN's:

Health News

Canadian Domain Names

Free Press Releases

Politics Journal

Hey czardogs,

Did you try manually installing it?

Installing it manually bypasses the install script totally.

I have added a manual install process at my site listed below...

Note: Encrypt your DB pass... use PSAK to do so.

Let me know if you have issues with that.

Good luck,
Dave

--
David Pahl
Zikula Support Team
Okay - I found a .762 package on an old backup disk - It installed first time without any problems.

--
My PN's:

Health News

Canadian Domain Names

Free Press Releases

Politics Journal

Upgrade!


--
David Pahl
Zikula Support Team
You can download a patched modify_config.php from SVN which should eliminate the issue, though the other solutions shouild work as well.

--
itbegins.co.uk - Zikula Consulting

birtwistle.me.uk - Personal Blog


Please read the Support Guide