Closed (fixed)
Project:
Drupal core
Version:
6.4
Component:
install system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Aug 2008 at 03:27 UTC
Updated:
2 Jan 2014 at 19:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jaydoubleu commentedThe error message is shown in the screen shot below.
Comment #2
Morn commentedFrom the documentation on shared hosting on 1 and 1
Fix:
Add the following line to the existing .htaccess file in the Drupal root directory (near the beginning of the file )
AddType x-mapp-php5 .phpThis works because the default for php V5 is register globals off
Comment #3
Morn commentedset to fixed
Comment #4
jaydoubleu commentedThanks Morn- that snippet of code seemed to work. It took me to the next step.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #6
Ms. James commentedi don't see this file in my drupal root directory. I did see it in my logs folder but cannot access it. I am with 1 and 1 as well and am getting the same error about the registered_globals being enabled. What do I do?
Comment #7
alternativecatII commentedIs it normal to not be able to find register_globals in .htaccess?
Comment #8
alternativecatII commentedI added the line
AddType x-mapp-php5 .phpat the first line of .htaccess after commented out section ended, and now my site turns into a totally blank white page if I click on anythingI took
AddType x-mapp-php5 .phpout and I was able to click on links again.Did I do something wrong?
If so, please explain.
Comment #9
Morn commentedThe only difference I see is that I inserted AddType .. as line Nr. 4, but that should make no difference.
Did you made more changes in .htaccess ? I used the original of 6.4 and it works.
By the way the DB Performace of 1 and 1 (regular shared Webserver) was too low for Drupal so I changed to a provider with better performance and with register globals off .
Comment #10
alternativecatII commented[Corrected typos 20091228]
I feel like such a block head. I put php.ini files all over the place because I was getting the error that only 32M of RAM was allocated, and 64M was recommended.
I changed this line from 32M to 128M in the php.ini
memory_limit = 128M ; Maximum amount of memory a script may consume (8MB)Since the register_globals issue is a PHP problem, I looked in the php.ini and sure enough, there it was. I changed the value from On to Off
register_globals = Off ; Whether or not to register the EGPCS variables as globalNo more
error message.
The php.ini file I changed that got rid of the error was at the root.
Unfortunately the instructions I had read on my hosting providers forum said to upload the php.ini into every folder to get rid of the 32M memory limit problem :-( yuck. I haven't managed to pull that off, but I have put a lot of php.ini files all over the place. I assume I should modify or over write all of them so they all have the same memory allocation.
At any rate, updating the file in the root did get rid of the error message.
I've attached a copy of the php.ini (compressed that is)
Comment #11
ainigma32 commentedSolution provided so setting to fixed.
- Arie