- Moderated by:
- Support
Goto page: [-1] 1 - 2 - 3 [+1]
Install error during fresh install of 0.7.6.3
-
- rank:
-
Professional
- registered:
- February 2004
- Status:
- offline
- last visit:
- 02.12.08
- Posts:
- 1039
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.
--
-
- rank:
-
Freshman
- registered:
- December 1969
- Status:
- offline
- last visit:
- 16.10.06
- Posts:
- 41
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 ^^
-
- rank:
-
Steering Committee
- registered:
- December 2002
- Status:
- online
- Posts:
- 13418
The bug is closed because a fix is in SVN - you need a new pnAPI.php
--
Regards,
Simon
itbegins.co.uk - Zikula Consulting
Please read the Support Guide
-
- rank:
-
Freshman
- registered:
- December 1969
- Status:
- offline
- last visit:
- 16.10.06
- Posts:
- 41
-
- rank:
-
Registered User
- registered:
- October 2006
- Status:
- offline
- last visit:
- 18.10.06
- Posts:
- 1
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!
-
- rank:
-
Freshman
- registered:
- October 2006
- Status:
- offline
- last visit:
- 18.10.06
- Posts:
- 4
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!
edited by: 1aschnitzel, Oct 18, 2006 - 04:23 PM
-
- rank:
-
Steering Committee
- registered:
- December 2002
- Status:
- online
- Posts:
- 13418
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.
--
Regards,
Simon
itbegins.co.uk - Zikula Consulting
Please read the Support Guide
-
- rank:
-
Freshman
- registered:
- October 2006
- Status:
- offline
- last visit:
- 18.10.06
- Posts:
- 4
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!!!!
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!)
-
- rank:
-
Team Member
- registered:
- December 2003
- Status:
- offline
- last visit:
- 01.12.08
- Posts:
- 2989
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!!!!
:) .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
-
- rank:
-
Team Member
- registered:
- December 2003
- Status:
- offline
- last visit:
- 01.12.08
- Posts:
- 2989
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
-
- rank:
-
Freshman
- registered:
- October 2003
- Status:
- offline
- last visit:
- 26.02.07
- Posts:
- 35
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
-
- rank:
-
Helper
- registered:
- February 2006
- Status:
- offline
- last visit:
- 21.11.06
- Posts:
- 257
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 ???
--
-
- rank:
-
Freshman
- registered:
- October 2006
- Status:
- offline
- last visit:
- 21.10.06
- Posts:
- 10
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?
-
- rank:
-
Steering Committee
- registered:
- December 2002
- Status:
- online
- Posts:
- 13418
It's possible your host has disabled php_flag, so talk to them about the problem. They should be able to help you.
--
Regards,
Simon
itbegins.co.uk - Zikula Consulting
Please read the Support Guide
-
- rank:
-
Freshman
- registered:
- October 2006
- Status:
- offline
- last visit:
- 27.10.06
- Posts:
- 20
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.
Goto page: [-1] 1 - 2 - 3 [+1]
|
