Ok, I bet it's related to this issue, then:
https://spservices.codeplex.com/workitem/10175
There are two syntax options, one with fieldName and one with fieldNames. Note the "s" in the latter one. I added that second syntax in a later version than the first and wanted to maintain compatibility. One workaround might be to make 4 separate calls with fieldname, but obviously that will be inefficient.
It looks like the Name column is getting assigned the ID value. I'm still not sure why that is happening, but since it is a numeric object, the replace is failing. I'd like to understand what the issue is so that I can fix the bug. If you're comfortable debugging and can figure it out, everyone can benefit!
What if you do this?
M.
https://spservices.codeplex.com/workitem/10175
There are two syntax options, one with fieldName and one with fieldNames. Note the "s" in the latter one. I added that second syntax in a later version than the first and wanted to maintain compatibility. One workaround might be to make 4 separate calls with fieldname, but obviously that will be inefficient.
It looks like the Name column is getting assigned the ID value. I'm still not sure why that is happening, but since it is a numeric object, the replace is failing. I'd like to understand what the issue is so that I can fix the bug. If you're comfortable debugging and can figure it out, everyone can benefit!
What if you do this?
curUser = $().SPServices.SPGetCurrentUser({
fieldNames: ['Name','Title','EMail'],
debug: false
});
i.e., omitting the ID?M.