Forums / Setup & design / problem with links eZ 3.5.1 -> 3.6.1

problem with links eZ 3.5.1 -> 3.6.1

Author Message

Marko Žmak

Thursday 11 August 2005 2:30:07 pm

I have an old installation of eZ 3.5.1. I created another installation of eZ 3.6.1. Then I've dumped the database from the old install and restored it in the new install. After that I have run the update scripts and everything worked O.K.
The new installation is working fine except for one thing. All the links in the XML Fields were broken. When I disabled the Online Editor I found out that all the link tags are missing the href attribute.

Does anyone know how to fix this?

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Georg Franz

Thursday 11 August 2005 2:40:01 pm

Hi Marko,

you need to run the update/scripts/common/convertxmllinks.php program after the update. (Clear cache after that)

Then it should work again.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Marko Žmak

Thursday 11 August 2005 2:43:45 pm

I found a forum post that adresses my problem but it doesn't solve it. When I run the:

update/common/scripts/convertxmllinks.php

script I get the following error:

Fatal error: eZ publish did not finish its request
The execution of eZ publish was abruptly ended, the debug output is present below.

And nothing else. How can I find what's wrong? I checked the

var/log/error.log

file but there's nothing there.

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Georg Franz

Thursday 11 August 2005 4:05:22 pm

Hi Marko,

did you call the script like:

php -C update/scripts/common/convertxmllinks.php -s yoursiteaccess

If it's a fatal error, it should be stored in the php-error log file. Do you have such a log file?

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Marko Žmak

Friday 12 August 2005 4:21:07 pm

Yes I tried like this but no effect. I didn't check the PHP error log file, but there's nothing in the eZ error.log...

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Bruce Morrison

Friday 12 August 2005 5:25:37 pm

Hi Marko

Did you update the databases as well as running the update scripts? Links in 3.6.x require some new tables that are created by the database update scripts.

Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Marko Žmak

Friday 12 August 2005 5:27:58 pm

Yes, I have run all the update scripts for the databse. The problem is that the convertlink script dosen't want to run.

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Marko Žmak

Thursday 18 August 2005 8:32:26 am

I'm trying to solve this for some time now but with no success. I tried everything tha I could think of:

- executing the script with all the --db-* parameteres
- executing with debug on and verbose messages
- executing with --logfiles script parameter
- setting php errorlog on php command line (-d error_log=my_log_file)
- setting log_errors=On and error_reporting=E_ALL in php comand line parameters
- setting permissions to 777 to error log file and it's parrent directory
- running the script with "-s mysiteacces"
- changing the default siteacces

But there's still no effect. I always get the same result:

Fatal error: eZ publish did not finish its request
The execution of eZ publish was abruptly ended, the debug output is present below.

And no other info is dsiplayed neither in some log file nor on standard output. I looked in the global error log file defined in php.ini and there's nothing there also.

Then I did a little manual research (by puttting some echo commands on some points in the script) and found out that the problem occurs on this command (line 101):

$db =& eZDB::instance( $dbImpl, $params, true );

when script is used with --db-* command line parameters, and on this (line108):

$db =& eZDB::instance();

when used without --db-* parameters.

Could anyone help me with this. How do I solve this problem, and why there are no errors logged?

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Xavier Dutoit

Thursday 09 March 2006 1:03:04 am

Since I've had the same problem today and for the record:
The mysql extension isn't activated by default on php-cli (debian sarge).

You have to modify: /etc/php4/cli/php.ini
uncomment:
extension=mysql.so

and while you're at it:

memory_limit = 80M ; the default 8 is way too low, 80 is probably too much, but better be safe than sorry ;)

X+

http://www.sydesy.com