Install 1.52 errors not seen on 1.50

[Kazimierz]

I just uploaded Joomla 1.52 for new site

Directive Recommended Actual

Safe Mode: Off Off
Display Errors: Off On
File Uploads: On On
Magic Quotes Runtime: Off Off
Register Globals: Off On
Output Buffering: Off Off
Session Auto Start: Off Off

The actual "Display Errors" and "Register Globals" are different then the recommended. I did not see this in 1.50.

What must I do to make this install will work properly.

Thank you

Oskar

[lerlacher]

Well, seems like you'll have to change the php options (on your server) for this. Maybe they were changed since you installed 1.50...

[franky reymenants]

actually I installed/removed a few joomla installations these last day's and I noticed different error statements on different occasions.

[Kazimierz]

Thanks, but change my php.ini to what?

[lerlacher]

Well, change it to not display errors and disable register_globals. Can't give you detailed instructions, it varies from server to server, and php options can be in the main php.ini, in htaccess files, in local php.ini...

[Kazimierz]

ok, I will check. Thanks

[Kazimierz]

I was able to turn register-globals OFF but I am still not able to to turn "Display Errors" OFF.

Any ideas. I am on a Godaddy Deluxe Account.

Thanks

[lerlacher]

would be a constant like "error_reporting", and it should be set to E_OFF.

[caesartg]

I noticed the same thing. I couldn't find the latest 1.5.2 version changes (maybe not on-line yet) so checked the bug tracker and found this suggesting that this was a change from v1.5.1 to v1.5.2:

http://joomlacode.org/gf/project/joomla ... em_id=9312

It seems that it is recommended that 'display errors' is on for development but off for production. You should be able to go ahead and install though as this is just a recommended setting.

Here's the relevant text from that link:

Open Date
2008-01-18 14:55:13 Close Date
2008-02-10 03:38:26
Summary
Pre-installation Check wrongly recommends Display Errors ON
Details

The Joomla! v 1.5 Pre-installation Check *should* recommend Display Errors be
OFF. Currently, it recommends it be ON.


From PHP Security Consortium: PHP Security Guide:

display_errors

This directive determines whether errors should be displayed on the screen
(included in the output). You should develop with this set to On, so that you
can be alerted to errors during development, and you should set this to Off for
production, so that errors are hidden from the users (and potential attackers).

Source: http://shiflett.org/php-security.pdf

[humvee]

Hi,

If you wish to turn off the display_errors setting and do not have access to the php.ini file you can try adding:

Code: Select all

php_flag display_errors "0"

(sometimes you may need to change the "0" to "Off")
to your .htaccess file in the joomla_root/ directory

hth

Andy

[petermatra]

Just want to add:

The code to add to the htaccess file (php_flag display_errors "0") worked.
My installation/installer/model.php already was set to off.
p

[tekcronic]

THIS IS A REPEAT POST BECAUSE IT IS WHAT IS FOUND IN GOOGLE WHEN SEARCHING FOR "DISPLAY ERRORS 1AND1"

After having the same issue I did some research and found what may be the root of the trouble for 1and1 users (though I am using the American side). What seems to be is that 1and1 has listed the example wrong in there FAQ section. I went and did a search for php.ini on the faq.1and1.com site and found the example php.ini file shows:

Code: Select all

allow_url_fopen = off;
memory_limit = 40M;
upload_max_filesize = 20M;
max_execution_time = 50000;
browscap = /usr/local/lib/browscap.ini
register_globals = off;
error_reporting  =  (E_ALL & ~E_NOTICE & ~E_WARNING);
url_rewriter.tags = “a=href,area=href,frame=src,form=fakeentry,fieldset=”;

If you notice the 5th line "browscap = /usr/local/lib/browscap.ini" needs a semi-colon at the end like:

Code: Select all

allow_url_fopen = off;
memory_limit = 40M;
upload_max_filesize = 20M;
max_execution_time = 50000;
browscap = /usr/local/lib/browscap.ini;
register_globals = off;
error_reporting  =  (E_ALL & ~E_NOTICE & ~E_WARNING);
url_rewriter.tags = “a=href,area=href,frame=src,form=fakeentry,fieldset=”;

Other wise everything underneath that line fails to get read. Assuming most use this as the example php.ini they started with an error and add the "display_errors = off;" line at the bottom like myself...

Any way using their example at 1and1 your php.ini file should have the following contents

Code: Select all

### Turn allow_url_fopen ON if you want to allow for site feeds ###
### to reach your site and other content as such ###
### Security Risk involved in allowing allow_url_fopen###
allow_url_fopen = off;
memory_limit = 40M;
upload_max_filesize = 20M;
max_execution_time = 50000;
browscap = /usr/local/lib/browscap.ini;
### Register Globals off for php 4 ###
###if you use an htaccess file to change to 5 this doesn't matter ###
register_globals = off;
error_reporting  =  (E_ALL & ~E_NOTICE & ~E_WARNING);
url_rewriter.tags = “a=href,area=href,frame=src,form=fakeentry,fieldset=”;
display_errors = off;

Then the php.ini file should be placed in the following folders:

• /
  /administrator
  /installation

The reason for only those 3 folders is because php should not be executing anywhere else on your Joomla site. If this is not the case add the php.ini anywhere else your browser can access content from the web. (or you have a problem and need to fix the code)

Also your .htaccess file should only be in the root folder "/" as it will effect all sub folders unlike the php.ini (this is for shared hosting on the 1and1 servers)

your .htaccess should contain (and can be added to the bottom of the joomla htaccess.txt)

Code: Select all

AddType x-mapp-php5 .php

example1.jpg

[shizzy]

Man its working that is awsome. You are a genious.

[jackson02127]

I could find the php.ini file, and I ran a search for it but could find any file that is matched to it. Can anyone out there please help?

Thanks

[drys]

i tryed make the .htacces and php.ini files and putted both files in
/public_html/
/public_html/administrator
/public_html/installation

looks like this
php.ini

Code: Select all

### Turn allow_url_fopen ON if you want to allow for site feeds ###
### to reach your site and other content as such ###
### Security Risk involved in allowing allow_url_fopen###
allow_url_fopen = off;
memory_limit = 40M;
upload_max_filesize = 20M;
max_execution_time = 50000;
browscap = /usr/local/lib/browscap.ini;
### Register Globals off for php 4 ###
###if you use an htaccess file to change to 5 this doesn't matter ###
register_globals = off;
error_reporting  =  (E_ALL & ~E_NOTICE & ~E_WARNING);
url_rewriter.tags = “a=href,area=href,frame=src,form=fakeentry,fieldset=”;
display_errors = off;

.htaccess

Code: Select all

##
# @version $Id: htaccess.txt 10492 2008-07-02 06:38:28Z ircmaxell $
# @package Joomla
# @copyright Copyright (C) 2005 - 2008 Open Source Matters. All rights reserved.
# @license http://www.gnu.org/copyleft/gpl.html GNU/GPL
# Joomla! is Free Software
##


#####################################################
#  READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE
#
# The line just below this section: 'Options +FollowSymLinks' may cause problems
# with some server configurations.  It is required for use of mod_rewrite, but may already
# be set by your server administrator in a way that dissallows changing it in
# your .htaccess file.  If using it causes your server to error out, comment it out (add # to
# beginning of line), reload your site in your browser and test your sef url's.  If they work,
# it has been set by your server administrator and you do not need it set here.
#
#####################################################

##  Can be commented out if causes errors, see notes above.
Options +FollowSymLinks

#
#  mod_rewrite in use

RewriteEngine On

########## Begin - Rewrite rules to block out some common exploits
## If you experience problems on your site block out the operations listed below
## This attempts to block the most common type of exploit `attempts` to Joomla!
#
# Block out any script trying to set a mosConfig value through the URL
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|\%3D) [OR]
# Block out any script trying to base64_encode crap to send via URL
RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [OR]
# Block out any script that includes a <script> tag in URL
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
# Send all blocked request to homepage with 403 Forbidden error!
RewriteRule ^(.*)$ index.php [F,L]
#
########## End - Rewrite rules to block out some common exploits

#  Uncomment following line if your webserver's URL
#  is not directly related to physical file paths.
#  Update Your Joomla! Directory (just / for root)

# RewriteBase /


########## Begin - Joomla! core SEF Section
#
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/index.php
RewriteCond %{REQUEST_URI} (/|\.php|\.html|\.htm|\.feed|\.pdf|\.raw|/[^.]*)$  [NC]
RewriteRule (.*) index.php
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
#
########## End - Joomla! core SEF Section
AddType x-mapp-php5 .php

Result nothing happens when activate php.ini
but when
AddType x-mapp-php5 .php is putted in .htaccess then IE7 says

Code: Select all

initialise(); // render the application $mainframe->render(); /** * RETURN THE RESPONSE */ echo JResponse::toString(); 

same error when .htacess is put only in root.


my best regards Hucks Denmark


OK FOUND OUT SOMETHING
i have no need for the .htaccess file
the problem is something in the code from joomla
if i delete all joomla lines and only have the
line
display_errors = off;
then it setting displayerrors to off
so there is something in the php.ini code from joomla thats not ok .

[dmagick]

Then the php.ini file should be placed in the following folders:

• /
  /administrator
  /installation

thanks all who replied to this one and others on this topic... the above snippet was what solved it for me on my new install