Page 1 of 1

Content manager error after upgrade from 1.12.1 to 2.0

Posted: Fri Sep 11, 2015 10:54 am
by almustone
Hi!

I get this kind of error:

Debug: (0.080963) - (usage: 8426008) - (peak: 8459112)

Number of elements: 4
Array
(
[content_id] => 242
[parent_id] => 241
[item_order] => 1
[content_alias] => varaus-ja-vuokraus
)

foo2

I have tried reinstalling with no help.

I get checksum errors:

8 Files Not found
Files Not found:
/admin/lang/ext/so_SO.php
/admin/lang/ext/rm_CH.php
/admin/lang/ext/fa_FA.php
/admin/lang/ext/eo_UY.php
/admin/lang/ext/mn_MN.php
/admin/lang/ext/vi_VN.php
/admin/lang/ext/gl_GL.php
/admin/lang/ext/iw_IL.php

27 Files failed md5sum check:
/lib/lang/tasks/ext/rm_CH.php
/lib/lang/tasks/ext/fa_FA.php
/lib/lang/tasks/ext/vi_VN.php
/lib/lang/tasks/ext/gl_GL.php
/lib/lang/cms_selflink/ext/fa_FA.php
/lib/lang/cms_selflink/ext/vi_VN.php
/lib/lang/cms_selflink/ext/gl_GL.php
/modules/CMSMailer/lang/ext/fa_FA.php
/modules/CMSMailer/lang/ext/iw_IL.php
/modules/MenuManager/lang/ext/rm_CH.php
/modules/MenuManager/lang/ext/fa_FA.php
/modules/MenuManager/lang/ext/iw_IL.php
/modules/News/lang/ext/fa_FA.php
/modules/News/lang/ext/mn_MN.php
/modules/News/lang/ext/vi_VN.php
/modules/News/lang/ext/iw_IL.php
/modules/MicroTiny/lang/ext/fa_FA.php
/modules/MicroTiny/lang/ext/vi_VN.php
/modules/MicroTiny/lang/ext/iw_IL.php
/modules/FileManager/lang/ext/fa_FA.php
/modules/FileManager/lang/ext/iw_IL.php
/modules/Search/lang/ext/rm_CH.php
/modules/Search/lang/ext/fa_FA.php
/modules/Search/lang/ext/iw_IL.php
/modules/ModuleManager/lang/ext/rm_CH.php
/modules/ModuleManager/lang/ext/fa_FA.php
/modules/ModuleManager/lang/ext/iw_IL.php

Any help?

Here is my system information:



----------------------------------------------

Cms Version: 2.0

Installed Modules:

CMSMailer: 5.2.4
AdminSearch: 1.0
FileManager: 1.5
MenuManager: 1.50
MicroTiny: 2.0
ModuleManager: 2.0
News: 2.50
Search: 1.50
ThemeManager: 1.1.8
Gallery: 2.0.2
TinyMCE: 2.9.12
Showtime: 3.4
CGSimpleSmarty: 1.9.1
JQueryTools: 1.3.7
FormBuilder: 0.8.1.1
CMSContentManager: 1.0
DesignManager: 1.0
Navigator: 1.0


Config Information:

php_memory_limit:
max_upload_size: 32000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Europe/Helsinki
permissive_smarty: false


Php Information:

phpversion: 5.4.41
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference:
test_db_timedifference:
memory_limit: 128M
max_execution_time: 120
output_buffering: 4096
file_uploads: On (True)
post_max_size: 32M
upload_max_filesize: 32M
session_save_path: /tmp (0777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)


Performance Information:

allow_browser_cache: On (True)
browser_cache_expiry: 0
php_opcache: Off (False)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
smarty_cache_udt: Off (False)
auto_clear_cache_age: Off (False)

Server Information:

Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.45
Server Db Grants: Could not find a suitable "GRANT ALL" permission, this does not necessarily lead to problems... But if you have problems installing/removing modules or adding and deleting items/pages this could be the cause!
Server Time Diff: No file system time difference found


----------------------------------------------

Best regards

Aleksi

Re: Content manager error after upgrade from 1.12.1 to 2.0

Posted: Fri Sep 11, 2015 2:56 pm
by calguy1000
This probably means that there was a problem with database integrity before you upgraded.

Though the error message is obtuse, it does indicate a problem in the database structure.

Try 're-ordering' your content before you upgrade.

Re: Content manager error after upgrade from 1.12.1 to 2.0

Posted: Mon Sep 14, 2015 5:51 am
by almustone
Hi! I made new fresh upgrade to 1.12.1 version. Before upgrading I updated page hierarchy positions and routes. After that I cleared cache. All with no errors.

There was no errors while upgrading, but still gives me the same error at Content Manager.

Best Regards

Aleksi