Page 1 of 1

Content Manager inaccessabile

Posted: Mon Jan 23, 2017 10:19 pm
by pwg
I moved a site from one server to another and now can't access the Content Manager. All other functionality and modules seem to be working ok.

Install process was, by installing 2.15 ( the version on the other server), checking it was working, then extracting all server files and importing the DB. All seemed to be until I removed the cmsms-2.1.5-install files and cleared cache. I actually did the install process twice (wiping server, so clean install) just to see if there had been any mistakes the first time. I did update to 2.16 hoping this would fix issue but no go.

I've moved quite a few sites with no issues previously.

Any ideas why content Manager is inaccessible?

System info below, and thanks for any help.
----------------------------------------------
Cms Version: 2.1.6
Installed Modules:
AceEditor2: 1.05
AdminSearch: 1.0.2
Album: 0.9.3
Backup: 0.5
CGBlog: 1.14.1
CGExtensions: 1.53.17
CGFBPost: 1.0.0.1
CGFeedMaker: 1.0.20
CGSimpleSmarty: 2.1.6
CGSmartImage: 1.21.5
CMSContentManager: 1.1.4
CMSMailer: 6.2.14
Comments: 1.9.2
DesignManager: 1.1.1
DewPlayer: 0.2.1
FLVPlayer: 1.0.3
FileManager: 1.5.2
FormBuilder: 0.8.1.4
JMFilePicker: 1.0
JQueryFU: 1.0.5
JQueryTools: 1.3.9
MenuManager: 1.50.2
MicroTiny: 2.0.3
ModuleManager: 2.0.5
Navigator: 1.0.3
News: 2.50.6
RSS: 1.1
SEOTools2: 1.2.1
Search: 1.50.2
ThemeManager: 1.1.8
TinyMCE: 2.9.12
Twitter: 0.0.6
avplayer: 1.0
simpletagging: 0.2.1

Config Information:
php_memory_limit:
max_upload_size: 10000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Australia/Sydney
permissive_smarty: false

Php Information:
phpversion: 5.5.29
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_ALL: 22519
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference: No time difference found
test_db_timedifference: No time difference found
create_dir_and_file: 1
memory_limit: 256M
max_execution_time: 60
register_globals: Off (False)
output_buffering: On
disable_functions:
open_basedir:
test_remote_url: Success
file_uploads: On (True)
post_max_size: 10M
upload_max_filesize: 10M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
check_ini_set: On (True)
curl: On

Performance Information:
allow_browser_cache: Off (False)
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: On (True)
Server Information:
Server Software: Apache
Server Api: cgi-fcgi
Server Os: Linux 2.6.32-642.3.1.el6.x86_64 On x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.52
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

Permission Information:
tmp: /home/accessprcom/public_html/tmp (0755)
tmp_cache: /home/accessprcom/public_html/tmp/cache (0755)
templates_c: /home/accessprcom/public_html/tmp/templates_c (0755)
modules: /home/accessprcom/public_html/modules (0755)
uploads: /home/accessprcom/public_html/uploads (0755)
File Creation Mask (umask): /home/accessprcom/public_html/tmp/cache (0755)
config_file: 0444
----------------------------------------------

Re: Content Manager inaccessabile

Posted: Mon Jan 23, 2017 10:22 pm
by Rolf
Clear *browser* cache too

Re: Content Manager inaccessabile

Posted: Mon Jan 23, 2017 10:39 pm
by pwg
Thanks, Rolf, but done many times, even to the point of clearing cache and an added DNS flush. I tried different browsers and all no go.

Re: Content Manager inaccessabile

Posted: Mon Jan 23, 2017 10:41 pm
by pwg
One thing to add to my question, the content Manager not being accessible isn't affecting the content being displayed. I can see the complete website, all pages, news and blog articles.

Just hard to hand back to the client, without them being able to edit any pages!

Thanks for any help.

Re: Content Manager inaccessabile

Posted: Mon Jan 23, 2017 10:43 pm
by Rolf
Any ideas why content Manager is inaccessible?
what do you mean with inaccessible?

Looked into Error log?

Re: Content Manager inaccessabile

Posted: Mon Jan 23, 2017 10:56 pm
by reneh
I can think of a reason for CM not accessible - that is if the site had page hierarchy error before upgrade. With this I mean if one or more pages are orphans (missing connection up to first level in hierarchy). Afaik this error can make the CM unavailable.
I know no auto fix for this that work but you can first try the Fix hierarchy in admin.
If that not work AND this is reason - you sadly has to edit/hack in database manually. You will need to find page items that is orphans and fix them to a known page id.
Backups first!

Re: Content Manager inaccessabile

Posted: Tue Jan 24, 2017 12:09 am
by pwg
Hi Rolf, by inaccessible I mean, not displaying at all. i get a blank section where the content hierarchy is normally laid out.
See: Image

Thanks reneh, I did try and update the hierarchy, but no luck. The site does have child pages whose parent pages are internal page links, so maybe I do need to look at this further.

Odd that it does affect the current site? Thanks for the help.

Cheers Paul

Re: Content Manager inaccessabile

Posted: Tue Jan 24, 2017 10:13 am
by PinkElephant
Hi Paul
pwg wrote:by inaccessible I mean, not displaying at all. i get a blank
section where the content hierarchy is normally laid out.
It's sounding very much like 1.12.1 -> 2.1.5 Content Manager empty where you'd see javascript errors about mixed content.

[Solved] Re: Content Manager inaccessabile

Posted: Tue Jan 24, 2017 10:15 pm
by pwg
Thanks to all that replied.

Rolf, I really should have paid more attention and immediately checked the error log - turns out the problem was a file permission issue preventing a jQuery plugin from being downloaded causing a terminating javascript error.

Basically, some of the scripts needed had the wrong permissions. Simply changing them to 755 fixed the issue.

Thanks again to all that helped - I learnt a few more things along the way, and the issue is sorted, so I guess, not a bad result!

Cheers,

Paul