View Issue Details

IDProjectCategoryView StatusLast Update
0002002OXID eShop (all versions)4.08. Cachepublic2012-12-10 13:39
Reporterandreas_ziethen Assigned To 
PriorityimmediateSeverityblockReproducibilityalways
Status resolvedResolutionunable to reproduce 
Product Version4.4.0 revision 28699 
Summary0002002: Content Caching does produce white pages if UTF-8 is used
DescriptionReason is the same as in https://bugs.oxid-esales.com/view.php?id=1800

In class oxcache again there is a $oStr->preg_replace() which causes the same problems as in 0001800.

Perhaps this should be fixed in oxstrmb class ...
TagsCache, UTF-8
Theme
BrowserAll
PHP Versionany
Database Versionany

Activities

dainius.bigelis

2010-07-28 11:37

reporter   ~0003317

Reminder sent to: andreas_ziethen

Hi,

Is it possible to have access to debug such case on some shop, where you reproduced it?
Also - are you sure that in there content (on UTF8 shop) there no non-utf chars? This would cause the problem for sure.

Best regards,

andreas_ziethen

2010-07-28 17:38

reporter   ~0003318

Hi,

I may ask the shop owner if we could demonstrate that on a time where the shop is not very busy - I let you know.
For the second thing I am not really sure what you mean. You may have a look at this page which for example caused a white page befor we changed the preg_replace stuff: http://www.bobshop.de/Frauen/

As far as I see there is some UTF-8 stuff in the META description? Do you mean that?

dainius.bigelis

2010-07-29 11:25

reporter   ~0003320

Reminder sent to: andreas_ziethen

Hi,

No.
The fix in bug 1800 solved the case when: shop is UTF8, but in the content there are some non-utf8 chars (in this case white page occured).
So maybe there are some NON-utf8 chars in this case also, which may cause the problem. Could you please check that?

Best regards,

dainius.bigelis

2010-08-09 15:25

reporter   ~0003371

Reminder sent to: andreas_ziethen

Hi,

Do you have any more details about this case?
As tried to reproduce such case on our local test systems, and had no success.

Best regards,
Dainius Bigelis

andreas_ziethen

2010-08-09 18:51

reporter   ~0003372

Sorry ... very busy at the moment, but I'll try to delivers some more info and perhaps a testshop soon.

dainius.bigelis

2010-09-01 15:13

reporter   ~0003465

Reminder sent to: andreas_ziethen

Hi,

As we cannot reproduce this case - this entry will be closed for now. If you will have some more info about the case later - please REopen the bug, or send details to our support with reference to this bug.
Thank you.

Best regards,

dainius.bigelis

2010-11-09 08:38

reporter   ~0003675

Bug reopened as we waiting more info about how to reproduce the case from reporter.

stanglmeier.peter

2010-11-15 10:37

reporter   ~0003697

We had the problem that, on unknown occasion, while active EE Caching, we saw the homepage being completely blank, throwing no errors. Our shop serves UTF-8 characters, while keping the shop files (templates, php-code) being ANSI formatted.
We had UTF-8 characters (German umlauts) in the ANSI-formatted templates causing the problem. Still we have no idea why this problem occurs not consistently, but only occasionally.

dainius.bigelis

2010-11-24 10:50

reporter   ~0003729

Reminder sent to: stanglmeier.peter

Hi,

The fix for bug 0001800 was included in the eShop 4.3.2. Do you experience this problem (blank page) on 4.3.2 or later version?
If so - could you please organize possibility for us to debug the issue on your system? as we cannot reproduce this case on our local systems.

Best regards,

stanglmeier.peter

2010-11-25 09:59

reporter   ~0003736

We have never user 4.3.x, just 4.4.x EE
Of course we cannot set the production evironment back to the problem status.
But we have seen the problen on production only.
Nevertheless I set our dev environment the the problem status: UTF-8 chars in an ANSI format template-file with OXID EE Caching active. So far, we have not reproduced the problem. If so I will let you know.

dainius.bigelis

2010-11-29 10:02

reporter   ~0003748

Reminder sent to: stanglmeier.peter

Hi,

So we will close this entry for now as "cannot reproduce". If you will reproduce this case in your development environment - please ReOpen this bug entry and let us know with all the details. Or just write an email to our support with the link to this bug entry.
Thank you.

Best regards,