|
Author
|
Message
|
|
Mauricio Taslik
|
Tuesday 27 February 2007 12:24:50 pm
Hi, I'm a total newcomer to eZ. The company's website is running under version 3.5.0 and there is a problem when trying to display images (eg. from the media section)... there seems to be something wrong since there is something that displays:
>Fatal error: eZ publish did not finish its request
>
>The execution of eZ publish was abruptly ended, the debug output is present below. There is no debug info at all... I'd like to know if this is a known problem of 3.5.0. Thanks in advance, Mauricio.
|
|
Łukasz Serwatka
|
Wednesday 28 February 2007 10:38:21 pm
Hi Mauricio, To get more information about error, you will need change error reporting in php.ini (if you have access to it) or put in second line in index.pnp following command: error_reporting( 6143 ); Then you should see full error description. eZ Publish 3.5 is no longer supported, if your server meets requirements [1] for 3.9 I suggest to take a while and follow upgrade path [2]
[1] http://ez.no/ezpublish/requirements
[2] http://ez.no/doc/ez_publish/upgrading
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
|
Mauricio Taslik
|
Thursday 01 March 2007 6:09:25 am
Thanks Lukasz, I am looking at the php_log file and there are a lot of: [01-Mar-2007 10:56:25] PHP Fatal error: Call to undefined function: convert() in /www/docs/grupoclave.net/public_html/site/lib/ezimage/classes/ezimagemanager.php on line 895 I want to set up parallel testing environment... do you know how can I know the versions of Apache, mySQL, PHP that are running at the production environment? Thanks in advance, Mauricio.
|
|
Łukasz Serwatka
|
Thursday 01 March 2007 9:36:20 am
Some information you can find in admin->setup->System information, you can also make an test.php file where you call phpinfo(); (note that some hosting providers block it)
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
|
Mauricio Taslik
|
Thursday 01 March 2007 10:21:02 am
Thanks Lukasz, I had already found out what versions are running at the production site:
Apache 1.3.37
PHP 4.4.4
MySQL 4.1.12-Max (*) (*) do you know what does the "Max" stand for? Now the question is: how can I make a copy of the site from the production environment to the testing environment? Thanks in advance, Mauricio.
|
|
Łukasz Serwatka
|
Thursday 01 March 2007 11:06:46 am
MySQL max [1] is version of MySQL server that includes additional features.
You server configuration fits for 3.9.
Depends what access do you have to server. Basically you can make:
- enter eZ Publish folder
- make database dump
- compress whole eZ Publish folder (with database dump)
- download is via "scp", or FTP
Then in new environment
- extract all files
- create database
- import database dump
- change INI files of eZ Publish
- set correct permissions See also "Move to new provider" page [2] It should be still valid. If your site has a lot of content, you can skip var directory, where are all files like cache, images, binary files, etc. uploaded or created by system.
[1] http://dev.mysql.com/doc/refman/4.1/en/mysqld-max.html
[2] http://ez.no/ezpublish/documentation/configuration/backup_restore/move_to_new_provider
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
|
Claudia Kosny
|
Thursday 01 March 2007 11:57:47 am
Hi Mauricio
In addition to Lukasz' last post: You definitely should skip the cache directories as they might contain cached files that refer to the old server name. So better let eZ create the cache from scratch again. (Unless you set up a virtual host with the same name and everything, in this case the cached files should be fine.)
On the other hand I would copy the var/storage directory over, even if it is big. Otherwise you will get messages about missing images/missing files which just clutter up your debug information and error logs. Claudia
|
|
Łukasz Serwatka
|
Thursday 01 March 2007 1:06:25 pm
On the other hand I would copy the var/storage directory over, even if it is big. Otherwise you will get messages about missing images/missing files which just clutter up your debug information and error logs.
That can be problematic since huge sites like ez.no usually has var dirs size in GB's (6 GB or even more). As long as you have control and you understand what you are doing that might be skipped and info about missing files/images can be ignored. Depends on needs.
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
|
Claudia Kosny
|
Thursday 01 March 2007 1:57:53 pm
Hi Lukasz Is there a way to suppress specific error messages e.g. the ones coming from the imagehandler? Then the error logs would not be so full of expected errors if you don't have the var directory. Claudia
|
|
Łukasz Serwatka
|
Friday 02 March 2007 12:20:45 am
Unfortunately this is not possible, there is no INI setting that controls it in details. It will require add some changes in ezdebug.
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
