site transfer /manager/ errors

6 Posts

f16d5s Reply #1, 14 years, 8 months ago

Good day everyone.

I am trying to transfer modx from dev to production servers.
What i do:
http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server
The site works BUT when i visit the manager panel i get:

Fatal error: Call to a member function getMessage() on a non-object in /***/***/***/core/model/modx/modmanagercontroller.class.php on line 552

Then i run update (normal update & advanced update give the same result) and get a new error:

Fatal error: Uncaught exception 'SmartyException' with message 'Unable to load template file 'header.tpl'' in /***/***/***/core/model/smarty/sysplugins/smarty_internal_template.php:162 Stack trace: #0 /***/***/***/core/model/smarty/sysplugins/smarty_internal_template.php(537): Smarty_Internal_Template->isExisting(true) #1 /***/***/***/core/model/smarty/Smarty.class.php(335): Smarty_Internal_Template->getRenderedTemplate() #2 /***/***/***/core/model/modx/modmanagercontroller.class.php(252): Smarty->fetch('header.tpl') #3 /***/***/***/core/model/modx/modmanagercontroller.class.php(443): modManagerController->fetchTemplate('header.tpl') #4 /***/***/***/core/model/modx/modmanagercontroller.class.php(161): modManagerController->getHeader() #5 /***/***/***/core/model/modx/modmanagerresponse.class.php(117): modManagerController->render() #6 /***/***/***/core/model/modx/modmanagerrequest.class.php(173): modManagerResponse->outputContent(Array) #7 /***/***/***/core/model/modx/modmanager in /***/***/***/core/model/smarty/sysplugins/smarty_internal_template.php on line 162

system specs:
development: unknown
production: XAMPP for Linux 1.7.4
Apache 2.2.17
MySQL 5.5.8
PHP 5.3.5
phpMyAdmin 3.3.9
modx version: modx-2.2.0-pl2 revolution

I googled, but didn't find much relevant information to the second error.
I really don't know where to go with this, any help will be really appreciated.

Hm... I seem to have found relevant errors.
At the update screen after the update succeeds i get the following:

Your assets/ directory was not created at: /home/***/assets/
You will need to create this directory and make it writable if you want to use Package Management or 3rd Party Components.

Your assets/components/ directory was not created at: /home/***/assets/components/ 
You will need to create this directory and make it writable if you want to use Package Management or 3rd Party Components.

If i create this directory and chmod it to 0777 && chown it to nobody:nobody (the web user) then the manager works.
I guess now i have to find out where in the configs this directory is.

yep. a grep -lir "/home/***/assets/" * from base directory gave me:
core/packages/ditsnews-0.2.0-alpha3/preserved.php
core/config/config.inc.php
core/cache/setup/settings.cache.php

Somehow the core/config/config.inc.php
MODX_ASSETS_PATH (Line 77) value wasn't being changed when i followed the guide.
Just to be sure i manually changed all the other defines:
$modx_base_path=
$modx_manager_path=
which still seemed to have the old /home/***/* paths.

The
$modx_core_path
$modx_processors_path
$modx_connectors_path
paths changed to correct ones when i upgraded i believe, or earlier.

Thread can be marked as solved. [ed. note: f16d5s last edited this post 14 years, 8 months ago.]

45 Posts

ram Reply #2, 14 years, 6 months ago

Hi there all–

I’m having very much the same issues as seen by the poster above.

System info:

Apache/2.2.9
PHP Version 5.2.6-1+lenny16
MODX 2.2.0pl2 upgraded to MODX 2.2.1

I archived and moved from development server to live and saw the same errors as shown here, so proceeded to run setup of 2.2.1.

Following setup I am able to use the front end of the site, excepting one page. The manager is currently inaccessible giving the error:

Fatal error: Uncaught exception 'SmartyException' with message 'Unable to load template file 'header.tpl'' in /path/to/web/core/model/smarty/sysplugins/smarty_internal_template.php:162 
Stack trace: 
#0 /path/to/web/core/model/smarty/sysplugins/smarty_internal_template.php(537): Smarty_Internal_Template->isExisting(true) 
#1 /path/to/web/core/model/smarty/Smarty.class.php(335): Smarty_Internal_Template->getRenderedTemplate() 
#2 /path/to/web/core/model/modx/modmanagercontroller.class.php(257): Smarty->fetch('header.tpl') 
#3 /path/to/web/core/model/modx/modmanagercontroller.class.php(448): modManagerController->fetchTemplate('header.tpl') 
#4 /path/to/web/core/model/modx/modmanagercontroller.class.php(166): modManagerController->getHeader() 
#5 /path/to/web/core/model/modx/modmanagerresponse.class.php(121): modManagerContr in /path/to/web/core/model/smarty/sysplugins/smarty_internal_template.php on line 162

Not sure where to go from here, the only access I have to this server is via FTP.

I have been unable to make one change noted in the above post, CHOWN. Other than that I did everything (and saw the same issues apart from the defines issue which I had already changed manually) in the post above.

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

Have tried setup from the archive but this time 2.2.0pl2 to 2.2.0pl2 on a separate server, this one showed a "500 Error. A fatal application error has been encountered.". I have seen this error previously doing the same install transferring another site onto the same server but clean installs of 2.2.0pl2 seem to work fine on it.

Going to revert back to 2.2.0pl2 archive and have a go with the 2.2.0pl2 setup on the client’s server. [ed. note: last edited this post 14 years, 6 months ago.]

☆ A M B ☆
3,141 Posts

Mark Hamstra Reply #3, 14 years, 6 months ago

Definitely move first and then upgrade, or upgrade and then move. Don't upgrade and move at the same time. Changes to the database and files used occur during upgrade, so you're skipping a step if you do it at the same time. Plus you wont be able to figure what caused the problem if a problem occurs during the move/upgrade.

The assets directory is not used by the MODX core, only as a default location to store components in, so that really shouldn't be part of the equation...

Those errors seem to me like there are files missing, or that the php process doesn't have access to the template files. Could also be that the paths in the config file are wrong or that there's wrong info left in the cache (though running setup clears that as well).

Perhaps there's more useful information pointing to an error in the error log at core/cache/logs/error.log.

Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.

45 Posts

ram Reply #4, 14 years, 6 months ago

Right! Got it sorted thanks. Transferred and set up with 2.2.0pl2. I think that there were some issues with file transfer that ended with some files not getting uploaded.

Having made sure the files on the server were synchronised with my local archive I managed to get it to install properly.