From: http://spservices.codeplex.com/discussions/348892
Add an option to allow passing in a URL to the function rather than simply picking up the current context. This will help where custom list forms are stored outside the list context.
Just to make sure I wasn't crazy, I tested $().SPServices.SPListNameFromUrl() from a Document library form, and it returns the correct GUID. So I think my function already works correctly. I'll add a new task for the next release to allow you to pass in the listName (or GUID) in as an option.
M.
Comments: I am using jquery 1.8.2 and SPServices 0.7.2. $().SPServices.SPListNameFromUrl("My List Name") does not return anything. What am I missing ? Thanks.
Add an option to allow passing in a URL to the function rather than simply picking up the current context. This will help where custom list forms are stored outside the list context.
Just to make sure I wasn't crazy, I tested $().SPServices.SPListNameFromUrl() from a Document library form, and it returns the correct GUID. So I think my function already works correctly. I'll add a new task for the next release to allow you to pass in the listName (or GUID) in as an option.
M.
Comments: I am using jquery 1.8.2 and SPServices 0.7.2. $().SPServices.SPListNameFromUrl("My List Name") does not return anything. What am I missing ? Thanks.