Forums / Install & configuration / How to upgrade when your host does not provide shell access

How to upgrade when your host does not provide shell access

Author Message

Greg McAvoy-Jensen

Friday 12 January 2007 9:42:55 am

Could someone verify that if you don't have shell access to your web host, the easiest way to do an upgrade is to:

1. migrate the whole system to a local PC (http://ez.no/ezpublish/documentation/configuration/backup_restore/move_to_new_provider)
2. perform the upgrades
3. migrate it all back

My Details
I use ipowerweb.com as a web host for our tiny non-profit. We're trying to move from 3.7.3 to 3.8.0 and then 3.9.0. ipowerweb.com allows cron jobs but not shell access. When I tried to run the language upgrade script using cron (cd /public_html; php update/common/scripts/updatemultilingual.php -s corporate), it runs in the top level ezpublish directory, but I get a stream of errors:

X-Powered-By: PHP/4.4.2
Content-type: text/html

<br />
<b>Warning</b>:  main(lib/ezutils/classes/ezcli.php): failed to open 
stream: No such file or directory in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line <b>63</b><br />
<br />
<b>Warning</b>:  main(): Failed opening 'lib/ezutils/classes/ezcli.php' 
for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> 
on line <b>63</b><br />
<br />
<b>Warning</b>:  main(kernel/classes/ezscript.php): failed to open 
stream: No such file or directory in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line <b>64</b><br />
<br />
<b>Warning</b>:  main(): Failed opening 'kernel/classes/ezscript.php' 
for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> 
on line <b>64</b><br />
<br />
<b>Warning</b>:  main(kernel/classes/ezcontentlanguage.php): failed to 
open stream: No such file or directory in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line <b>65</b><br 
/>
<br />
<b>Warning</b>:  main(): Failed opening 
'kernel/classes/ezcontentlanguage.php' for inclusion 
(include_path='.:/usr/lib/php:/usr/local/lib/php') in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line <b>65</b><br />
<br />
<b>Warning</b>:  main(kernel/classes/ezcontentobjectversion.php): 
failed to open stream: No such file or directory in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line 
<b>66</b><br />
<br />
<b>Warning</b>:  main(): Failed opening 
'kernel/classes/ezcontentobjectversion.php' for inclusion 
(include_path='.:/usr/lib/php:/usr/local/lib/php') in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line <b>66</b><br />
<br />
<b>Fatal error</b>:  Undefined class name 'ezcli' in 
<b>/home/friends/public_html/update/common/scripts/updatemultilingual.php</b> on line 
<b>88</b><br />

Hence I've given up trying to upgrade on the host's server, and instead am downloading it to my own Debian maching (which is running some less important ezpublish sites already).

Any better suggestions? Is this the best route? Any reason not to do the first upgrade as part of the migration from ipowerweb to my server? Thanks!

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Greg McAvoy-Jensen

Wednesday 17 January 2007 6:59:20 am

Never mind. I just realized ipowerweb uses PHP 4.3, not 4.4, so it's a non-issue. I'll have to host it myself, and I'm upgrading to Etch.

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog