:: does element14 query always crash? (solved)

[3roomlab]

as it always happens for me ... i wonder

(solved : using separate browser (in my case : opera) slight java glitch. as it happens, the older opera 11.xx seem to be faster than firefox and chrome)

[matseng]

Can't recall that I've ever seen that. I use the Malaysian version of E14, but my guess is that it shares exactly the same codebase as the Singapore version.

A tip that might come in handy- I've setup "E" as a Search Engine shortcut in Chrome to search in element14.  This is the URL I'm using:

Code: [Select]

http://my.element14.com/webapp/wcs/stores/servlet/Search?catalogId=15001&langId=83&storeId=10188&gs=true&st=%s
It probably needs some more adjustments in addition to change the "my" to something else, but I suppose that it would be easy to figure out by looking at the URL after a normal direct search on the site.

[David_AVD]

Do you have cookies enabled for E14 ?

Some web sites will crash in spectacular ways when cookies are disabled.

[3roomlab]

i see, snooping cookie munsters ! thanks

[adam1213]

this is an issue with element 14's website. Each time you visit a page element 145 adds the information on the page you have visited to a cookie. Eventually the cookie gets long enough that the request is too long. Solution: buy from another vendor / get element 14 to fix there site / clear the cookie manually. Note the key that gets long is likely bnTrail

[3roomlab]

yea, im quite used to it crashing.

it normally happens after about 10 steps into a detailed item search/filtering 

edit :: i think i will do an experiment, i will install opera browser, and use opera to browse e14 exclusively to see what happens.

[adam1213]

edit :: i think i will do an experiment, i will install opera browser, and use opera to browse e14 exclusively to see what happens.

It will likely work for a while until the cookie gets too big again.

[3roomlab]

the java is not happy lol