Ok Marc, I will try to explain a bit more. At the same web I have the following lists:
http://site.domain.com/path/subsite/lists/Sample/NewForm.aspx
But when I try this one:
http://site/path/subsite/lists/Sample/NewForm.aspx
The error appears on my Internet Explorer: 'childColumnStatic' is undefined and the cascade dropdown fails and all option of all combo box are enabled.
I really don't expect this for my users, because some of them type the full url, some not. At the same time a lot of sites that also uses SPServices doesn't have any problem, using both URLs.
Now I would like to know if different behaviors are expected or not using $().SPServices.SPCascadeDropdowns according to URL, because it's the result I'm having.
I never had this kind of problem when I did my own cascade drop down.
Appreciate for your time! Thanks again!
Group
-- Title (text)
Product
-- Title (text)
-- Group (lookup)
Sample
-- Title (text)
-- Product (lookup)
-- Group (lookup)
I'm not specifying any URL. Basically I'm using the following code:$().SPServices.SPCascadeDropdowns({
relationshipList: "Product",
relationshipListParentColumn: "Group",
relationshipListChildColumn: "Title",
parentColumn: "Group",
childColumn: "Product",
});
Well, it works fine when a try to use the following URL:http://site.domain.com/path/subsite/lists/Sample/NewForm.aspx
But when I try this one:
http://site/path/subsite/lists/Sample/NewForm.aspx
The error appears on my Internet Explorer: 'childColumnStatic' is undefined and the cascade dropdown fails and all option of all combo box are enabled.
I really don't expect this for my users, because some of them type the full url, some not. At the same time a lot of sites that also uses SPServices doesn't have any problem, using both URLs.
Now I would like to know if different behaviors are expected or not using $().SPServices.SPCascadeDropdowns according to URL, because it's the result I'm having.
I never had this kind of problem when I did my own cascade drop down.
Appreciate for your time! Thanks again!