Page 1 of 2
[SOLVED] Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 11:13 am
by oliveramoros
Hi - i'm having trouble with the local install on a mac...
At stage 2 of install this item is failing:
Testing error_reporting to ensure E_DEPRECATED is disabled
E_DEPRECATED is enabled
I have tried adding these two lines to my config.php file but didn't help

:
error_reporting(E_ALL);
error_reporting(E_ALL & ~E_DEPRECATED);
Any advice appreciated! Thanks.
Oli
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 11:34 am
by RonnyK
You could write the line to the php.ini directly as it is local, then restart the webserver and the errors should be gone...
Check the php.ini for 'error_reporting', there is where the setting should be placed.
Ronny
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 11:45 am
by oliveramoros
Thanks Ronny but as this is a local [test server] install I don't think I have a php.ini file...
where would I find it / put it??
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 12:21 pm
by RonnyK
Check where you installed the PHP (I use wampserver f.e. and there it is in the tree under wampservers install....)
Ronny
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 1:19 pm
by oliveramoros
hmmm... i'm using xampp but also it's not showing up in a search.
Could it have anything to do with the fact i'm using php 5.3.1 or is that OK now?
Thanks
Oli
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 1:36 pm
by RonnyK
There should be a php.ini in the root of \xampp\php\
Ronny
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 2:34 pm
by oliveramoros
Nope! there is no \php dir in xampp.
I did try adding a php.ini to the xampp root but no good.
What am I doing wrong?? I'm almost tempted to go with WordPress
Oli
Re: Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Tue Apr 06, 2010 2:40 pm
by oliveramoros
OK SOLVED!
I am a noob but just realised i was missing "" in my config.php file. It now reads:
The installation can now proceed. HURRAH!
Thanks for your ideas Ronny.
Oli
Not solved for me
Posted: Wed Oct 27, 2010 4:42 am
by kendo451
I just installed the lastest version of XAMPP (w/ PHP 5.3.1) on Windows XP, installed CMS Made Simple 1.8.2 and now this has me completely stalled for hours.
Testing error_reporting to ensure E_DEPRECATED is disabled
E_DEPRECATED is enabled
I've tried all the suggested solutions here with no joy:
http://www.cmsmadesimple.org/about-link/blog/
Here is the relevant portion of my php.ini
Code: Select all
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; This directive informs PHP of which errors, warnings and notices you would like
; it to take action for. The recommended way of setting values for this
; directive is through the use of the error level constants and bitwise
; operators. The error level constants are below here for convenience as well as
; some common settings and their meanings.
; By default, PHP is set to take action on all errors, notices and warnings EXCEPT
; those related to E_NOTICE and E_STRICT, which together cover best practices and
; recommended coding standards in PHP. For performance reasons, this is the
; recommend error reporting setting. Your production server shouldn't be wasting
; resources complaining about best practices and coding standards. That's what
; development servers and development settings are for.
; Note: The php.ini-development file has this setting as E_ALL | E_STRICT. This
; means it pretty much reports everything which is exactly what you want during
; development and early testing.
;
; Error Level Constants:
; E_ALL - All errors and warnings (includes E_STRICT as of PHP 6.0.0)
; E_ERROR - fatal run-time errors
; E_RECOVERABLE_ERROR - almost fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_STRICT - run-time notices, enable to have PHP suggest changes
; to your code which will ensure the best interoperability
; and forward compatibility of your code
; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
; E_DEPRECATED - warn about code that will not work in future versions
; of PHP
; E_USER_DEPRECATED - user-generated deprecation warnings
;
; Common Values:
; E_ALL & ~E_NOTICE (Show all errors, except for notices and coding standards warnings.)
; E_ALL & ~E_NOTICE | E_STRICT (Show all errors, except for notices)
; E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR (Show only errors)
; E_ALL | E_STRICT (Show all errors, warnings and notices including coding standards.)
; Default Value: E_ALL & ~E_NOTICE
; Development Value: E_ALL | E_STRICT
; Production Value: E_ALL
; http://php.net/error-reporting
error_reporting = E_ALL & ~E_DEPRECATED
; This directive controls whether or not and where PHP will output errors,
; notices and warnings too. Error output is very useful during development, but
; it could be very dangerous in production environments. Depending on the code
; which is triggering the error, sensitive information could potentially leak
; out of your application such as database usernames and passwords or worse.
; It's recommended that errors be logged on production servers rather than
; having the errors sent to STDOUT.
; Possible Values:
; Off = Do not display any errors
; stderr = Display errors to STDERR (affects only CGI/CLI binaries!)
; On or stdout = Display errors to STDOUT
; Default Value: On
; Development Value: On
; Production Value: Off
; http://php.net/display-errors
display_errors = Off
; The display of errors which occur during PHP's startup sequence are handled
; separately from display_errors. PHP's default behavior is to suppress those
; errors from clients. Turning the display of startup errors on can be useful in
; debugging configuration problems. But, it's strongly recommended that you
; leave this setting off on production servers.
; Default Value: Off
; Development Value: On
; Production Value: Off
; http://php.net/display-startup-errors
display_startup_errors = Off
; Besides displaying errors, PHP can also log errors to locations such as a
; server-specific log, STDERR, or a location specified by the error_log
; directive found below. While errors should not be displayed on productions
; servers they should still be monitored and logging is a great way to do that.
; Default Value: Off
; Development Value: On
; Production Value: On
; http://php.net/log-errors
log_errors = Off
Here is my .HTACCESS file :
Code: Select all
DirectoryIndex index.php
Options +FollowSymLinks
RewriteEngine on
RewriteBase /
# 301 Redirect all requests that don't contain a dot or trailing slash to
# include a trailing slash
RewriteCond %{REQUEST_URI} !/$
RewriteCond %{REQUEST_URI} !\.
RewriteRule ^(.*) %{REQUEST_URI}/ [R=301,L]
# Rewrites urls in the form of /parent/child/
# but only rewrites if the requested URL is not a file or directory
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+)$ index.php?page=$1 [QSA]
php_value error_reporting 22527
Here is my CONFIG.PHP
Code: Select all
<?php
error_reporting(E_ALL);
error_reporting(E_ALL & ~E_DEPRECATED);
#CMS Made Simple Configuration File
#Please clear the cache (Site Admin->Global Settings in the admin panel)
#after making any changes to path or url related options
#-----------------
#Behaviour Settings
#-----------------
# These settings will effect the overall behaviour of the CMS application, please
# use extreme caution when editing these. Additionally, some settings may have
# no effect on servers with significantly restricted configurability.
# Warning: This option is deprecated and will be removed in later versions oF CMSMS.
# If you are experiencing problems with php memory limit errors, then you may
# want to try enabling and/or adjusting this setting.
# Note: Your server may not allow the application to override memory limits.
$config['php_memory_limit'] = '';
# In versions of CMS Made Simple prior to version 1.4, the page template was processed
# in it's entirety. This behaviour was later changed to process the head portion of the
# page template after the body. If you are working with a highly configured site that
# relies significantly on the old order of smarty processing, you may want to try
# setting this parameter to false.
$config['process_whole_template'] = false;
# CMSMS Debug Mode? Turn it on to get a better error when you
# see {nocache} errors, or to allow seeing php notices, warnings, and errors in the html output.
# This setting will also disable browser css caching.
$config['debug'] = false;
# Output compression?
# Turn this on to allow CMS to do output compression
# this is not needed for apache servers that have mod_deflate enabled
# and possibly other servers. But may provide significant performance
# increases on some sites. Use caution when using this as there have
# been reports of incompatibilities with some browsers.
$config['output_compression'] = false;
#-----------------
#Database Settings
#-----------------
#This is your database connection information. Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'localhost';
$config['db_username'] = 'fig_cms';
$config['db_password'] = 'fh39ta0h408hyfzm{ ';
$config['db_name'] = 'fig_cms';
#Change this param only if you know what you are doing
$config["db_port"] = '';
#If app needs to coexist with other tables in the same db,
#put a prefix here. e.g. "cms_"
$config['db_prefix'] = 'cms_';
#Use persistent connections? They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;
#Use ADODB Lite? This should be true in almost all cases. Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;
#-------------
#Path Settings
#-------------
#Document root as seen from the webserver. No slash at the end
#If page is requested with https use https as root url
#e.g. http://blah.com
$config['root_url'] = 'http://localhost/figenterprises.net';
#SSL URL. This is used for pages that are marked as secure.
$config['ssl_url'] = 'https://localhost/figenterprises.net';
#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = 'C:\xampp\htdocs\figenterprises.net';
#Name of the admin directory
$config['admin_dir'] = 'admin';
#Where do previews get stored temporarily? It defaults to tmp/cache.
$config['previews_path'] = 'C:\Documents and Settings\Kenneth\My Documents\My Dropbox\xampp\htdocs\figenterprises.net\tmp\cache';
#Where are uploaded files put? This defaults to uploads.
$config['uploads_path'] = 'C:\Documents and Settings\Kenneth\My Documents\My Dropbox\xampp\htdocs\figenterprises.net\uploads';
#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';
#---------------
#Upload Settings
#---------------
#Maxium upload size (in bytes)?
$config['max_upload_size'] = 128000000;
#Permissions for uploaded files. This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';
#------------------
#Usability Settings
#------------------
#Allow smarty {php} tags? These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;
#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;
#------------
#URL Settings
#------------
#What type of URL rewriting should we be using for pretty URLs? Valid options are:
#'none', 'internal', and 'mod_rewrite'. 'internal' will not work with IIS some CGI
#configurations. 'mod_rewrite' requires proper apache configuration, a valid
#.htaccess file and most likely {metadata} in your page templates. For more
#information, see:
#http://wiki.cmsmadesimple.org/index.php/FAQ/Installation/Pretty_URLs#Pretty_URL.27s
$config['url_rewriting'] = 'none';
#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';
#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy? (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = true;
#If using none of the above options, what should we be using for the query string
#variable? (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php/User_Handbook/Admin_Panel/Content/Image_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = 'C:/Program Files/VisualMagick/bin/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = 'C:\Documents and Settings\Kenneth\My Documents\My Dropbox\xampp\htdocs\figenterprises.net\uploads\images';
$config['image_uploads_url'] = $config['root_url'] . '/uploads/images';
#SSL URL. This is used for pages that are marked as secure.
$config['ssl_uploads_url'] = '/uploads';
#------------------------
#Locale/Encoding Settings
#------------------------
#Locale to use for various default date handling functions, etc. Leaving
#this blank will use the server's default. This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';
#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8. If you'd like this to be different, change
#both. Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding. This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = 'utf-8';
$config['admin_encoding'] = 'utf-8';
#This is a mysql specific option that is generally defaulted to true. Only
#disable this for backwards compatibility or the use of non utf-8 databases.
$config['set_names'] = true;
# URL of the Admin Panel section of the User Handbook
# Set none if you want hide the link from Error
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php/User_Handbook/Admin_Panel';
#------------------------
#Miscelaneous Settings
#------------------------
#Add performance information (in the form of an HTML comment) to the
#bottom of all generated pages. Note, this may cause problems with validation
#or with advanced AJAX requests where only portions of a page are requested.
#This variable just needs to exist, value is irrelevant.
#$config['show_performance_info'] = 'anything';
?>
Re: [SOLVED] Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Wed Oct 27, 2010 7:09 am
by cyberman
Have you tried a htaccess entry like this
Code: Select all
php_flag display_startup_errors 0
php_flag display_errors 0
php_flag html_errors 0
php_value docref_root 0
php_value docref_ext 0
Re: [SOLVED] Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Wed Oct 27, 2010 3:15 pm
by kendo451
Cyberman, I am going to try that now.
Here is the strange thing, though. My phpinfo() run in the same directory as the CMSMS 1.8.2 install, shows what appears to be the correct values, but it still is failing the Installation Script test.
This makes me wonder if the installation script test has a bug.
See screenshot:
Re: [SOLVED] Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Wed Oct 27, 2010 3:19 pm
by kendo451
Cyberman, I tried those .htaccess values you suggested, still no effect on the install test.
As I said, the phpinfo() looks correct, but it is failing the test of the install script.
Re: [SOLVED] Help! Install test fail - stage 2 - E_DEPRECATED is enabled
Posted: Wed Oct 27, 2010 3:35 pm
by kendo451
I decided to uninstall XAMPP and go back to version 1.7.1 which uses PHP 5.2.12.
Re: [SOLVED] Help! Install test fail - stage 2 - E_DEPRECATE
Posted: Sat Jun 04, 2011 8:50 pm
by replytomk3
cyberman wrote:Have you tried a htaccess entry like this
Code: Select all
php_flag display_startup_errors 0
php_flag display_errors 0
php_flag html_errors 0
php_value docref_root 0
php_value docref_ext 0
This breaks the website on 1and1 hosting.
Re: [SOLVED] Help! Install test fail - stage 2 - E_DEPRECATE
Posted: Mon Jul 11, 2011 1:43 pm
by gottelicious
I am having the same problem, but i dont understand some of the files. I easily found and corrected the php.ini file, but i have 5 different .htaccess files and they all contain just:
# To deny PHPs
<Files ~ "\.(php|php3|php4|php5|phtml|pl|cgi)$">
order deny,allow
deny from all
</Files>
And i have 2 different config.php, one is empty and the other contains just:
<?php
/**
* config.php
*
* @package MCManager.includes
*/
// General settings
$config['general.engine'] = 'GoogleSpell';
//$config['general.engine'] = 'PSpell';
//$config['general.engine'] = 'PSpellShell';
//$config['general.remote_rpc_url'] = '
http://some.other.site/some/url/rpc.php';
// PSpell settings
$config['PSpell.mode'] = PSPELL_FAST;
$config['PSpell.spelling'] = "";
$config['PSpell.jargon'] = "";
$config['PSpell.encoding'] = "";
// PSpellShell settings
$config['PSpellShell.mode'] = PSPELL_FAST;
$config['PSpellShell.aspell'] = '/usr/bin/aspell';
$config['PSpellShell.tmp'] = '/tmp';
// Windows PSpellShell settings
//$config['PSpellShell.aspell'] = '"c:\Program Files\Aspell\bin\aspell.exe"';
//$config['PSpellShell.tmp'] = 'c:/temp';
?>
Can someone please help me get this fixed.
Thanks a lot
Anders