When using the Content Picker datatype on a website with uCommerce, the js from uCommerce interferes with the treepicker.aspx that loads the content tree in then popup-window, when selecting a node from the content-tree on a page.
This in effect means, that the content-picker is not usable when uCommerce is installed, which is a problem. How do I solve this so I can use the Content Picker datatype?
Umbraco version: 4.5 uCommerce version: 1.0.4.0
The JS bug when loading the content-tree for the Content Picker is:
The generated page (clicking the url in the error console) looks like this:
This problem seems to occur in all instances where the content-tree is loaded in a popup-window.
- E.g. it also occurs when using Umbracos built-in content picker when selecting a starting-point in the window Visualise XSLT. - Also occurs when using the Media Picker content type
I really need to solve this problem, any help is appreciated.
Using content picker data type with uCommerce
When using the Content Picker datatype on a website with uCommerce, the js from uCommerce interferes with the treepicker.aspx that loads the content tree in then popup-window, when selecting a node from the content-tree on a page.
This in effect means, that the content-picker is not usable when uCommerce is installed, which is a problem. How do I solve this so I can use the Content Picker datatype?
Umbraco version: 4.5
uCommerce version: 1.0.4.0
The JS bug when loading the content-tree for the Content Picker is:
The generated page (clicking the url in the error console) looks like this:
This problem seems to occur in all instances where the content-tree is loaded in a popup-window.
- E.g. it also occurs when using Umbracos built-in content picker when selecting a starting-point in the window Visualise XSLT.
- Also occurs when using the Media Picker content type
I really need to solve this problem, any help is appreciated.
Hi Karina,
I'll look into this and get back to you.
- Lasse
Hi
Just tested with uCommerce 1.4.0.1 and Umbraco 4.5. And the bug is now fixed. Thanks!
Best regards
Emil
is working on a reply...