Error Editing Pages in Admin Area, Error with Module Manager

For questions and problems with the CMS core. This board is NOT for any 3rd party modules, addons, PHP scripts or anything NOT distributed with the CMS made simple package itself.
Post Reply
Yvetzky
New Member
New Member
Posts: 5
Joined: Wed Jun 13, 2012 10:47 pm

Error Editing Pages in Admin Area, Error with Module Manager

Post by Yvetzky »

Hi! I read a similar thread but I'm not sure it's exactly the same problem. Lets start with basic info:

1. Running CMSms 1.3.1(Havana) on PHP 5.2.17, mySQL 5.1.63cll, Apache 2.2.20, on a Linux box.

2. My config.php file:

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

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

$config['db_password'] = '*****';
$config['db_name'] = '******';

#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://roostersfoundation.org';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}

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

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

#Where do previews get stored temporarily? It defaults to tmp/cache.
$config['previews_path'] = '/home/yvetzky7/public_html/tmp/cache';

#Where are uploaded files put? This defaults to uploads.
$config['uploads_path'] = '/home/yvetzky7/public_html/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'] = 2000000;

#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;

#CMSMS Debug Mode? Turn it on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;

#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;

#------------
#URL Settings
#------------

#Show mod_rewrite URLs in the menu? You must enable 'use_hierarchy' for this to work for modules
$config['assume_mod_rewrite'] = true;

#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';

#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism? This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = false;

#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 ... ge_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/yvetzky7/public_html/uploads/images';
$config['image_uploads_url'] = $config['root_url'] . '/uploads/images';


#------------------------
#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'] = '';
$config['admin_encoding'] = 'utf-8';

#---------------------------------------------
#Use the old stylesheet logic? It's much slower, but it works with older
#versions of CMSMS. You'll also need this set to true if there is a module
#that uses a stylesheet callback. Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;

# URL of the Admin Panel section of the User Handbook
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php ... dmin_Panel';

#Enable backwards compatibility mode? This basically will allow some
#modules written before 1.0 was released to work. Keep in mind that this
#will use a lot more memory and isn't guaranteed to fix the problem.
$config['backwards_compatible'] = false;

#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
3. The errors I'm having...

Error 1:
The most urgent error is that when I try to edit any of the pages via the admin area, I get this error:
Fatal error: Call to undefined method ErrorPage::RemoveProperty() in /home/yvetzky7/public_html/lib/classes/contenttypes/ErrorPage.inc.php on line 66

This install was done originally on a server with PHP 5.2.17, and I did not have this problem. But the host upgraded the server last weekend to 5.3.16, and I got this error along with these:

Warning: get_class() expects parameter 1 to be object, string given in /home/yvetzky7/public_html/admin/editcontent.php on line 322

Warning: Cannot modify header information - headers already sent by (output started at /home/yvetzky7/public_html/admin/editcontent.php:322) in /home/yvetzky7/public_html/lib/classes/class.admintheme.inc.php on line 161

Warning: Cannot modify header information - headers already sent by (output started at /home/yvetzky7/public_html/admin/editcontent.php:322) in /home/yvetzky7/public_html/lib/classes/class.admintheme.inc.php on line 164

and so on.

But... the "Warning" errors went away when I asked the hosting service to switch me back to a 5.2.16 server. However the "Fatal error" remained.

So why won't it work now?

I'm expecting you to tell me to upgrade the CMSms version, but I'm hoping there's a quick fix for now so I can do some edits for the client quickly.

Error 2:
When I go to the Modules section I get this warning:
"The modules folder is not writable, if you would like to install modules by uploading an XML file you need to make the modules folder have full read/write/execute permissions (chmod 777). Safe mode may also be in effect."

I have checked the permissions, and the Module file was changed to 777 recursively, and the Safe mode is not on.

Please help.

Error 3:
When I go to the Module Manager section I see these errors preceding the module lists.

(This is just a snippet, the whole error is very long.)
WARNING: Insufficient directory permissions to install modules. You may also be experiencing problems with PHP Safe mode. Please ensure that safe mode is disabled, and that file system permissions are sufficient.

Followed by a lot of:
Array ( [name] => AceEditor [filename] => AceEditor-0.2.4.2.xml [md5sum] => bcad8d59c8f8da239f317d0b518ab391 [version] => 0.2.4.2 [mincmsversion] => 1.9 [description] => AceEditor is a Syntaxhighlighter module using Ace a standalone code editor written in JavaScript. [date] => 0000-00-00 00:00:00 [size] => 3957075 [status] => notinstalled )

Array ( [name] => AComments [filename] => AComments-1.1.1.xml [md5sum] => c0ef5d0626a912b75608852e94cf1599 [version] => 1.1.1 [mincmsversion] => 1.7 [description] => The comments module allows visitors to leave comments on your website. [date] => 0000-00-00 00:00:00 [size] => 132473 [status] => notinstalled )

Array ( [name] => AdvancedContent [filename] => AdvancedContent-0.9.3.xml [md5sum] => 18d0d422bd6fa7c94917f4484d5d34ee [version] => 0.9.3 [mincmsversion] => 1.10.3 [description] => Advanced content type with custom fields for the add/edit page panel and some additional functions. [date] => 0000-00-00 00:00:00 [size] => 1775892 [status] => notinstalled )

...
I know I need to upgrade the CMS software. Should I upgrade step to step (one version at a time) or can I go straight to 1.11.1?

And should I also upgrade the modules first before the core? I can simply overwrite the module files with the newest version (after backing up the old)?

Thank you for any help! :-)
Post Reply

Return to “CMSMS Core”