Problem

Next topic

Author	Message
Jacek Olszak	Monday 20 December 2004 2:46:21 am Hi... I've successfully installed ezpublish 3 (and made my own website) on my local machine. Now I want to send these files to the remote server (Linux, PHP 4.3.8, MySQL). I've sent all the files (and import data to mysql) but the website isn't working. I see the following error: Fatal error: Call to a member function on a non-object in /home/w/i/wiedzanet-www/public_html/kernel/classes/ezcontentobjecttreenode.php on line 956 Fatal error: eZ publish did not finish it's request The execution of eZ publish was abruptly ended, the debug output is present below. What I'm doing wrong? Please help...
Łukasz Serwatka	Monday 20 December 2004 3:23:30 am Hi Jacek, It`s nice to see polish name on ez.no forum ;-) Did you clear the cache and set right permissions to var/design/settings dirs? Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Jacek Olszak	Monday 20 December 2004 3:41:18 am Did you clear the cache and set right permissions to var/design/settings dirs? Yeah, I've clear the cache. I've also set 777 permissions to <i>var</i> directory and 755 to design and settings dirs. But this doesn't help. Any other ideas?
Conor Murray	Monday 20 December 2004 6:31:53 am Try turning on debug output (in site.ini for your siteaccess, see the default site.ini for info). Often this output makes tracing problems very easy, although this isn't always the case! You should clear all caches again also when you change this setting. The 'clearcache.sh --clear-all' command line method of clearing the cache seems to be more reliable than the web admin method, by the way. Language is a virus - William S Burroughs
Roy Bøhmer	Monday 20 December 2004 11:48:12 am Do you always get this message? (I.e all siteaccesses/urls return the same error) Have you checked the line in the php-file (/kernel/classes/ezcontentobjecttreenode.php on line 956)if this gives you any hint of where the problem is? Roy
Jacek Olszak	Tuesday 21 December 2004 2:50:29 am Thanks everyone for help me. I've found the problem. I had a wrong database configuration (be precise a wrong name of database). The problem was really silly but those fatal errors misguide me.