Translation problem

Author Message

Valentina Ferrari

Wednesday 19 October 2005 6:55:48 am

I have a custom object (nothing special: just a title and a text handled by the eZ Online editor) and I have the need to handle a multilanguage site.

After publishing the german translation, it happened that in the content of the original object, the text area stopped showing. Checking in the database I noticed that the contentobject_attribute DATA_TEXT value for the object was incomplete, as if the xml output of the Online editor was truncated.

Until now, it has not been possible to replicate the problem.

Is it possible that in the german charset, used for the translation, exist some character that interferes with the xml generation?
Is it an "accident" that it's likely not to happen anymore?
Or other ideas?

Thanks

vale

Björn Dieding@xrow.de

Thursday 20 October 2005 1:48:35 am

I say:
You can only fix a bug, if you can reproduce it.

Since you can't reproduce it, it is not a bug.

The problem with your thing is that it is might be a bug, but it is to hard to reproduce. So again it is not a bug. "Finding a needle in the haystack"

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Marko Žmak

Thursday 20 October 2005 10:43:59 am

I agree with Bjorn. The truncation of the data could also occur because of the error in browser submiting the data for example.

If you cannot reproduce a bug it's always possible that something else than eZ caused the problem.

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

Hubert Farnsworth

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 04:35:41
Script start
Timing: Jan 31 2025 04:35:41
Module start 'layout'
Timing: Jan 31 2025 04:35:41
Module start 'content'
Timing: Jan 31 2025 04:35:41
Module end 'content'
Timing: Jan 31 2025 04:35:41
Script end

Main resources:

Total runtime0.0143 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0048 588.1328151.2109
Module start 'layout' 0.00480.0022 739.343836.6484
Module start 'content' 0.00700.0058 775.992290.1563
Module end 'content' 0.01280.0014 866.148433.9922
Script end 0.0143  900.1406 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002416.9205140.0002
Check MTime0.00117.7871140.0001
Mysql Total
Database connection0.00074.987910.0007
Mysqli_queries0.001913.090330.0006
Looping result0.00000.063410.0000
Template Total0.00117.410.0011
Template load0.00085.862010.0008
Template processing0.00021.511410.0002
Override
Cache load0.00063.980310.0006
General
dbfile0.001510.524680.0002
String conversion0.00000.048440.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs