Page 1 of 1

[SOLVED]Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 3:14 pm
by chrisbar
Hello,

I just upgraded form 1.9.2 tot 1.9.4.1.
I have set the config.php back tot CHMOD 444 and now when opening the website I get the following errors:

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/index.php on line 168

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/index.php on line 169

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/index.php on line 170

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/index.php on line 171

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/index.php on line 172

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/index.php on line 281

The site is visible however with the errors mentioned in top and the content isn't shown as before (over the whole page instead of within a smaller contentblock.

In the Admin (inlog) panel I also get the follwing errors:

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/admin/login.php on line 287

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/config.php:1) in /home/users/r/e/redeag/www/admin/login.php on line 288
What to do? Thanks for the help!

Chris

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 6:43 pm
by Dr.CSS
Step by step how did you do the upgrade?...

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 6:52 pm
by chrisbar
I copied all files of the version 1.9.4.1 to the server overwriting the version of 1.9.2. I then changed the CHMOD of config.php tot 666. Then I let the upgrade do it's job and at the end I changed the config.php back CHMOD 444.

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 6:57 pm
by Wishbone
I'm concerned about config.php trying to update header information (according to the error).. Can you check the config.php and see if it starts with <?php

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 7:03 pm
by chrisbar
Details on how:

I typed in www.red-eagles.nl/install/upgrade.php and followed all steps. In the last step I choose for opening the website (instead of opening the admin panel). I changed the config.php to 444 (was changed to 666 before I started the upgrade process).

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 7:07 pm
by chrisbar
Underneath you find the config.php

Code: Select all

<?php


#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'] = '64M';

# 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 true.
$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;

# Timezone setting
# PHP 5.3 requires that timezones be set at the server level.
# This variable can be used to set your sites timezone.
# Valid values for this variable can be found at:
# http://www.php.net/manual/en/timezones.php
# If this field is empty, no timezone will be set
$config['timezone'] = '';

#-----------------
#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'] = 'xxx';
$config['db_username'] = 'xxx';
$config['db_password'] = 'xxx';
$config['db_name'] = 'xxx';
#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://www.red-eagles.nl';

#SSL URL.  This is used for pages that are marked as secure.
$config['ssl_url'] = 'https://www.red-eagles.nl/';

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/home/users/r/e/redeag/www/';

#Name of the admin directory
$config['admin_dir'] = 'admin';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/home/users/r/e/redeag/www/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = '/home/users/r/e/redeag/www/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'] = 10000000;

#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 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'] = '/usr/bin/ImageMagick/';

#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/home/users/r/e/redeag/www/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'] = 'https://www.red-eagles.nl/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 

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 8:22 pm
by Wishbone
You might want to rename your install directory since it's now public knowlege... You wouldn't want someone else to install your site. ;)

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 8:43 pm
by Wishbone
I was searching for this error message and found a thread of yours from last year:

http://forum.cmsmadesimple.org/viewtopi ... hp#p239746

it looks like you had that same issue when upgrading from 1.6.7 to 1.9.2... How did you fix that?

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 8:48 pm
by chrisbar
I upgraded to 1.9.2 directly form 1.6.7 and that did it then.
Maybe I should reinstall CGExtensions as that was one of the possibilities then?

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Mon Mar 21, 2011 10:02 pm
by chrisbar
When I try to open the website now I start directly in the install upgrade mode????? When I follow all steps I have to fill in all database and website information again?? Seems that the config.php is completly empty now. In order to prevent that anyone who tries to visit the site starts to 'upgrade' I have replaced the empty config.php with the old config.php. When I visit the site now I get the following errors:
Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/include.php on line 40

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/include.php on line 40

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 169

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 170

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 171

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 172

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 282

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/lib/content.functions.php on line 521

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/lib/content.functions.php on line 522

De website van de Red Eagles is wegens onderhoud even niet bereikbaar. Excuses voor het ongemak, wij zijn zo snel als mogelijk weer in de lucht.


Any idea to solve this?

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Tue Mar 22, 2011 7:42 am
by chrisbar
OK,

I have re-upgraded the CMSMS and still the following errors appear:

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/include.php on line 40

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 169

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 170

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 171

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 172

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/users/r/e/redeag/www/index.php:1) in /home/users/r/e/redeag/www/index.php on line 282

The system information presents the following:

CMS Versie 1.9.4.1

Geïnstalleerde ModulesCMSMailer 2.0.1

FileManager 1.1.0

MenuManager 1.7.6

ModuleManager 1.4.2

News 2.11.2

nuSOAP 1.0.2

Printing 1.1.2

Search 1.6.10

ThemeManager 1.1.4

TinyMCE 2.8.4

Album 0.9.3

FormBuilder 0.7

Calendar 0.8.2

FCKeditorX 1.1.0

Showtime 2.0.3

BlankOfTheMonth 1.1

youtubeplayer 1.3

CGExtensions 1.24.1

GoogleCalendar 0.1.1

AjaxMadeSimple 0.3.1

Banners 2.5

Banners 2.5

Chat 0.3.0

vimeoplayer 1.0

TeamSportScores 1.1.7

MediaCenter 0.4

Guestbook 1.3.2

Captcha 0.4.3

Advertise 1.0

Smileys 0.2.0

Uploads 1.11.6

CMSForms 0.0.10

CMSUsers 0.0.6

HostedVideoAlbums 2.0.1

PHPMyAdmin 3.1.1

CGEcommerceBase 1.2.4

CGSimpleSmarty 1.4.8

FrontEndUsers 1.12.12

JQueryTools 1.0.10

Availability 1.7.12

Gallery 1.4.4

FEmessages 1.1

SelfRegistration 1.6.7

jQuery 1.1.2

Config Informatiephp_memory_limit: 32M

process_whole_template: false

output_compression: false

max_upload_size: 10000000

default_upload_permission: 664

url_rewriting: none

page_extension:

query_var: page

image_manipulation_prog:GD

auto_alias_content: true

locale:

default_encoding: utf-8

admin_encoding: utf-8

set_names: true

debug: false

root_url: http://www.red-eagles.nl

ssl_url: https://www.red-eagles.nl/

root_path: /home/users/r/e/redeag/www/ (0701)

previews_path: /home/users/r/e/redeag/www/tmp/cache (0777)

uploads_path: /home/users/r/e/redeag/www/uploads (0701)

uploads_url: http://www.red-eagles.nl/uploads

image_uploads_path: /home/users/r/e/redeag/www/uploads/images (0701)

image_uploads_url: http://www.red-eagles.nl/uploads/images

ssl_uploads_url: https://www.red-eagles.nl/uploads

use_smarty_php_tags:false


PHP Informatie:

Huidige PHP versie (phpversion): 5.2.8

md5 functie (md5_function): Aan (Waar)

GD versie (gd_version): 2

tempnam functie (tempnam_function): Aan (Waar)

Er bevinden magic quotes in de runtime (magic_quotes_runtime): Uit (Onwaar)

Is E_STRICT uitgeschakeld in error_reporting (E_STRICT):


PHP Memory Limit (memory_limit): 32M

Maximale Uitvoertijd (max_execution_time): 30

PHP output_buffering (output_buffering): 0

PHP Safe Mode (safe_mode): Uit (Onwaar)

Bestand uploads (file_uploads): Aan (Waar)

Maximale Post Grootte (post_max_size): 10M

Maximale Upload Grootte (upload_max_filesize): 2M

Session Save Path (session_save_path): /tmp (1777)

Gebruik sessie-cookies (session_use_cookies): Aan (Waar)

Basis XML (expat) ondersteuning (xml_function): Aan (Waar)

Controle of het httpd proces een bestand in de aangemaakte directory kan maken (create_dir_and_file):

PHP register_globals (register_globals): Uit (Onwaar)

disable_functions in PHP (disable_functions):


PHP Open Basedir (open_basedir):


Testen van externe URL (test_remote_url):

fsockopen: Verbinden geslaagd!
fopen: Verbinden geslaagd!

Controleer ini_set (check_ini_set): Aan (Waar)
Server Informatie: Server API (server_api):

cgi

Server Database (server_db_type): MySQL (mysql)

Server Database Versie (server_db_version):5.0.77

Server Software (server_software): Apache

Server Operating System (server_os):Linux 2.6.9-89.0.18.ELsmp Aan i686

Autorisatie informatietmp: /home/users/r/e/redeag/www//tmp (0701)

templates_c: /home/users/r/e/redeag/www/tmp/templates_c (0777)

modules: /home/users/r/e/redeag/www//modules (0701)

Bestandscreatiemasker (umask): /home/users/r/e/redeag/www/tmp/cache (0777)

config_file: 0666
config.php is beschrijfbaar! Het is veiliger om dit in te stellen als 'alleen-lezen' (chmod 444).



In the controlpanel when I try to go to the content/pages I get the follwoing error:

Output has already been sent to the browser at /home/users/r/e/redeag/www/config.php:1. Please make sure the command $xajax->processRequest() is placed before this.

This is the situation by now. Hope this information helps to solve the problem.

Chris

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Tue Mar 22, 2011 3:03 pm
by Wishbone
In a side folder, Try installing a fresh copy of 1.9.4.1, connect it to your database (I would use a copy of the database), but tell it not to install the content.. Then copy over all your non-CMS files. See if that works.

Re: Upgrade form 1.9.2 to 1.9.4.1

Posted: Tue Mar 22, 2011 3:20 pm
by chrisbar
I had contact with my provider and they told me that my database didn't function yet because I had not installed phpmyadmin yet in the root?? Wonder if you need the databse anyhow? I'm a bit confused now.

I'm reupgrading now. The upgrade mentions that Output Buffering is off. Where and how do I change that?
Where can I change PHP time from 30 to 60 and Max upload form 2M to 10M. Thought I could change that in config.php?

I have continued the upgrade process and it works !!! ;D ;D ;D
Probably with overwriting the 1.9.2 files something has gone wrong so I reuploaded it through another ftp-programme (file by file ...pffff).

Still although interested in the solutions for Output Buffering etc. (see above).

Thanks for the help!