[SOLVED] Had to go back to CMS 1.5.4 and now it's broken

[cweese]

Hello - I recently upgraded one of my sites to 1.6.x. I was adding a lot of archived content at the time, and because TinyMCE was working so much better, I added a bunch of content.

However, I have had to downgrade back to 1.5.4 because I had used Cataloger as a key part of the site and had paid a good chunk of money to have some custom code developed around it.

Now the back end is broken - when I try to add new pages, I get this message:

Fatal error: Call to undefined method ErrorPage::RemoveProperty() in /home/spmagzn/public_html/lib/classes/contenttypes/ErrorPage.inc.php on line 48

Here is the system info:

CMS Install Information:

CMS Version

1.5.4

Installed Modules

CMSMailer

1.73.14

FileManager

1.0.1

MenuManager

1.6.2

ModuleManager

1.3.1

News

2.10.3

nuSOAP

1.0.1

Printing

1.0.3

Search

1.6.1

ThemeManager

1.1.1

TinyMCE

2.4.13

Banners

2.2.1

Calendar

0.8.2

EventsListing

1.3

TemplateManager

0.2

Cataloger

0.7

Config Information

php_memory_limit:

process_whole_template: true

max_upload_size: 64000000

default_upload_permission: 664

assume_mod_rewrite: false

page_extension:

internal_pretty_urls: false

use_hierarchy: false

debug: false

output_compression: false

root_url: http://www.sportponymagazine.com

root_path: /home/spmagzn/public_html (0750) Success

previews_path: /home/spmagzn/public_html/tmp/cache (0777) Success

uploads_path: /home/spmagzn/public_html/uploads (0777) Success

uploads_url: http://www.sportponymagazine.com/uploads

image_uploads_path: /home/spmagzn/public_html/uploads/images (0777) Success

image_uploads_url: http://www.sportponymagazine.com/uploads/images

use_smarty_php_tags: true

locale:

default_encoding:

admin_encoding: utf-8

PHP Information:

Current PHP Version (phpversion): 5.2.9 Success

md5 function (md5_function): On (True) Success

GD version (gd_version): 2 Success

tempnam function (tempnam_function): On (True) Success

Magic quotes in runtime (magic_quotes_runtime): Off (False) Success

PHP Effective Memory Limit (memory_limit): 64M Success

Maximum Execution Time (max_execution_time): 30 Caution ?

PHP Safe Mode (safe_mode): Off (False) Success

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

Checking if the httpd process can create a file inside of a directory it created (create_dir_and_file): Success

PHP register_globals (register_globals): On (True) Caution ?

PHP output_buffering (output_buffering): On Success

disable_functions in PHP (disable_functions): dl Success

PHP Open Basedir (open_basedir):  Success

Test for remote URL (test_remote_url): Success
fsockopen: Connection ok! Success
fopen: Connection ok! Success

File uploads (file_uploads): On (True) Success

Maximum Post Size (post_max_size): 64M Success

Maximum Upload Size (upload_max_filesize): 64M Success

Basic XML (expat) support (xml_function): On (True) Success

Test file_get_contents (file_get_contents): On (True) Success

Test ini_set (check_ini_set): On (True) Success

Server Information:

Server API (server_api): cgi-fcgi

Server Database (server_db_type): MySQL (mysql)

Server Database Version (server_db_version):

5.1.30 Success

Server Software (server_software):
Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8i DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635

Server Operating System (server_os): Linux 2.6.28.9 On i686

Permission Information

tmp: /home/spmagzn/public_html/tmp (0777) Success

templates_c: /home/spmagzn/public_html/tmp/templates_c (0777) Success

modules: /home/spmagzn/public_html/modules (0755) Success

File Creation Mask (umask): /home/spmagzn/public_html/tmp/cache (0777) Success

config_file: 0644 Failure
config.php writable. It is more safe if you change permission to read-only
(I am not sure why it is saying the config.php is set to 644. When I check in Fetch it is clearly at 444).

I have backups from both the previous 1.5.x version and the 1.6.x version (both a database backup and a full home directory backup), so I could use either backup, but with the 1.6.x version Cataloger doesn't work, and if I go back to the 1.5.x verison, I lose a bunch of content.... any suggestions? I know I've made some stupid mistakes, am just trying to get the site working again... whatever it takes.

[Jeff]

Pay the person who developed your custom code for the Cataloger or someone else to update/fix the module so that it will work with 1.6.x.

[cweese]

Can you even update Cataloger to work with 1.6? From what I read in the upgrade info, it's fundamentally flawed for working with the new system.

[Dr.CSS]

If you read the release notes you will see that {content} has been rewritten, but most all modules that use it should work now, but whatever custom work you had done to cataloger may not work in the new content api...

[calguy1000]

Can you even update Cataloger to work with 1.6? From what I read in the upgrade info, it's fundamentally flawed for working with the new system.

Doing a simple search of the release notes in Module Manager tells me that Cataloger has had 3 releases since 1.6
and one of those was specifically a compatibility release.

[cweese]

OK, yay - I hadn't seen any new Cataloger releases when I upgraded to 1.6... my developer advised to go back to the previous CMS version so that's what I attempted. I am also looking at this patch here, which was recommended on another thread:

http://forum.cmsmadesimple.org/index.ph ... #msg183422

It's in Italian but goes nicely through Google translate. THANKS EVERYONE!!