UI appears to totally freeze and not allow editing of anything (only Chrome)

[bunglehaze]

Version i = currencydisplay error when product price set to no in modules still.

Editing existing products leaves me with a page I can do nothing with, all options do nothing other than back on browser - even the joomla admin menu links have no hover over or function

[PRO]

Version i = currencydisplay error when product price set to no in modules still.

Editing existing products leaves me with a page I can do nothing with, all options do nothing other than back on browser - even the joomla admin menu links have no hover over or function

RE: Module. I do not get this. Are you sure the modules are up to date?


RE: saving options. Do you have a java error? I do not get this at all either

[bunglehaze]

Modules all uninstalled, AIO installed and then core updated so the modules are all up to date - unless there is something in the overriden template file that is causing this.
** Must be something in the previous template - removed the override and the error vanishes - however the template was only the default.php that came in release G with an inline style put in of margin and padding

No Java errors either, infact release G worked fine in the backend and was used only minutes prior to installing the new core

[bunglehaze]

The product issue is an odd one, it only affects a couple of specific products and as far as I can tell only the ones where I have specified a product detail page override. Others seem to load and operate fine

[bunglehaze]

Right then, I have gone through all the products in my shop, the issue ONLY occurs within one category for ALL products - in the backend the UI appears to totally freeze and not allow editing of anything, if I were to back on the browser I get stuck in a loop and the site frontend also freezes from loading. The only way to use the site in this situation is either initially close down the backend tab (instead of pressing back) and then reopen a new tab to go the admin CP URL again.

[bunglehaze]

Hopefully finally, the issue only seems to occur in Chrome too - FF and IE are fine.