PostNuke Community

• Wendell
  
  

  • Rank: Professional
  • Registered: 07.02.04
  • last visit: 02.07.09
  • Posts: 1176

  Posted: 15.10.2006, 21:10

  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."
  
  

  • 
  •  
• beyss
  
  

  • Rank: Freshman
  • Registered: 31.12.69
  • last visit: 27.06.09
  • Posts: 40

  Posted: 15.10.2006, 21:17

  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 ^^
  

  • 
  •  
• Simon
  
  

  • Rank: Steering Committee
  • Registered: 11.12.02
  • last visit: 01.07.09
  • Posts: 13378

  Posted: 16.10.2006, 14:15

  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

  • 
  •  
• beyss
  
  

  • Rank: Freshman
  • Registered: 31.12.69
  • last visit: 27.06.09
  • Posts: 40

  Posted: 16.10.2006, 14:43

  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 ^^
  

  • 
  •  
• kithkanan
  
  

  • Rank: Registered User
  • Registered: 18.10.06
  • last visit: 18.10.06
  • Posts: 1

  Posted: 18.10.2006, 09:44

  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!
  
  

  • 
  •  
• 1aschnitzel
  
  

  • Rank: Freshman
  • Registered: 18.10.06
  • last visit: 18.10.06
  • Posts: 4

  Posted: 18.10.2006, 16:22

  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

  • 
  •  
• Simon
  
  

  • Rank: Steering Committee
  • Registered: 11.12.02
  • last visit: 01.07.09
  • Posts: 13378

  Posted: 18.10.2006, 17:56

  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

  • 
  •  
• 1aschnitzel
  
  

  • Rank: Freshman
  • Registered: 18.10.06
  • last visit: 18.10.06
  • Posts: 4

  Posted: 18.10.2006, 18:45

  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!)

  • 
  •  
• AmmoDump
  
  

  • Rank: Team Member
  • Registered: 08.12.03
  • last visit: 28.06.09
  • Posts: 3062

  Posted: 18.10.2006, 18:58

  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

  • 
  •  
• AmmoDump
  
  

  • Rank: Team Member
  • Registered: 08.12.03
  • last visit: 28.06.09
  • Posts: 3062

  Posted: 18.10.2006, 19:53

  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

  • 
  •  
• jeff300
  
  

  • Rank: Freshman
  • Registered: 01.10.03
  • last visit: 26.02.07
  • Posts: 35

  Posted: 21.10.2006, 01:16

  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

  
  

  • 
  •  
• gerkynet
  
  

  • Rank: Helper
  • Registered: 19.02.06
  • last visit: 27.06.09
  • Posts: 256

  Posted: 21.10.2006, 02:39

  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 ???
  
  
  --
  

  _00_
  
  Hispa-PN.net - Desarrollos PostNuke

  • 
  •  
• makoto_makoto
  
  

  • Rank: Freshman
  • Registered: 14.10.06
  • last visit: 21.10.06
  • Posts: 10

  Posted: 21.10.2006, 08:13

  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?

  • 
  •  
• Simon
  
  

  • Rank: Steering Committee
  • Registered: 11.12.02
  • last visit: 01.07.09
  • Posts: 13378

  Posted: 21.10.2006, 08:32

  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

  • 
  •  
• intristin
  
  

  • Rank: Freshman
  • Registered: 21.10.06
  • last visit: 27.10.06
  • Posts: 20

  Posted: 21.10.2006, 14:40

  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.

  • 
  •  
•  
•  

Users online

This list is based on the users active over the last 60 minutes.