- Crazy Post - cannot edit it!
- V 6.6.6 Some errors when upload files and create category in Chinese name
#1 Jan 19, 2016 02:01
I have got an crazy error now. I' using version 6.6.7 with the Tealpro Skin.
If I'm using the search function with the word "gez" all works fine. If I'm using the search function with the word "häring" I got this error:
Warning: Division by zero in [...]/blogs/inc/collections/_search.funcs.php on line 902
I don't know why this will be.
#3 Jan 20, 2016 13:22
you can search with the 2 words above. You will get this error as I described.
And the thing in debug mode I will try in the evening.
#4 Jan 20, 2016 21:28
#5 Jan 21, 2016 00:22
Dude, you are crazy! ;) The screenshot is a long, very, very long screenshot. And its size is in compressed mode 2,8 MB. So its to big to upload here.
And I saw, there were almost 120 queries in it - but my screenshot tool only snaps until #62 o.O
<del>What do you need from this? All above the queries? Would that be enough?</del>
Ah ok, I see - until 20 MB are allowed here. So you will get this crapped screenshot ...
#6 Jan 22, 2016 06:51
@ednong that's right, the screenshot is not useful because I can't read a word on it :D. I removed it from your comment.
The thing is that in debug mode you get extra information about the search results displayed just below each one of them. Maybe if you screenshot only that section, we could find something useful there to identify the issue. The best way would be to see all the debug result by ourselves, so it would be great if you set a password to the debug mode and share it via pm.
#7 Jan 22, 2016 15:39
Oh it was too much information? ;)
Okay, here I will go - a new screenshot with the details I guess you want. I hope, this are the right details.
#8 Jan 22, 2016 15:43
less than 60 chars for a filename are allowed only? My names are longer ;)
#9 Jan 23, 2016 10:36
less than 60 chars for a filename are allowed only? My names are longer
Well, thanks for the screenshot, it was less helpful than I expected but I guess we can extract some information. We will keep trying to reproduce the issue in order to find a fix.
Did you find any other example of search term producing that output?
PS. I deleted your screenshot to avoid fullpath disclosure.
#10 Jan 23, 2016 14:28
[quote=]PS. I deleted your screenshot to avoid fullpath disclosure.[/quote]
Ah okay, I forgot to pixelate the path ...
Other terms with same output - I don't know. This term I looked for randomly - and I found the bug ... ;)