http://www.magentocommerce.com/bug-tracking/ en MagentoCommerce Copyright {gmt_date format="%Y"} {gmt_date format="%Y-%m-%dT%H:%i:%s%Q"} http://www.magentocommerce.com/bug-tracking/issue?issue=6790 Posted: 2009-07-05 16:56:44
Category: Categories
Version: 1.3.2.2
Priority: high
Status: closed
Reported By: dsb68

Hi

Having upgraded from 1.3.2.1 to 1.3.2.2 I found a problem editing categories in my browser (IE8). The Error on Page note was appearing at the bottom left of the browser window.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.2; MS-RTC LM 8; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
Timestamp: Sun, 5 Jul 2009 20:52:10 UTC

Message: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)
Line: 0
Char: 0
Code: 0
URI: http://www.ingenso.com/index.php/admin/catalog_category/index/key/4227bd8912176fbbf712eb7543385998/

Message: Object expected
Line: 751
Char: 9
Code: 0
URI: http://www.ingenso.com/index.php/admin/catalog_category/index/key/4227bd8912176fbbf712eb7543385998/


I checked the diff files and by uploading the old file (which worked ok) I identified the file:
app/design/adminhtml/default/default/template/catalog/category/edit/form.phtml

and the last line:
updateTopButtonToolbarToggle();

as the problem.

If I comment it out, the page loads and seems to work fine.

However, I don't know the significance/importance of the line.

Hope this helps someone.

Dale

---

]]> #1 / Comment by dsb68

Following up on this, I found that my suggestion does not allow you to edit and save a category (it just removes the script error). Sorry for my mistake.

I tried moving the function updateTopButtonToolbarToggle() in /js/mage/adminhtml/tools.js below floatingTopButtonToolbarToggle().

This seems to work, but the 'please wait' box appears and does not go away. So something else is still wrong.]]> #2 / Comment by Magento Team

Hello dsb68,

This issue was fixed. The changes will be available in the next bugfix release.

Thank you.]]>