From: https://spservices.codeplex.com/discussions/444799
I have an issue with a function not running async when upgrading SPServices to the new version. The issue I found was at line 1220 of SPServices. In the previous version, the async value was set to the async option I provide. In the new version, it defaults to false if a completefunc exists. In my case, I have a completefunc and still need it to be true for async. Is there something I am not seeing to do this? When I delete the "thisHasCompletefun ? false : " from that line, everything works for me but rather than changing spservices on my system, I'd rather understand the intent better.
Comments: For now, I have made a "version 2013.01a" and modified line 1220 from: ``` async: thisHasCompletefunc ? false : opt.async ``` to: ``` async: opt.async ``` I don't recommend others do this without understanding the implications but we needed other new functionality so this works for us. If I can do anything to assist in finding a true solution long term, let me know.
I have an issue with a function not running async when upgrading SPServices to the new version. The issue I found was at line 1220 of SPServices. In the previous version, the async value was set to the async option I provide. In the new version, it defaults to false if a completefunc exists. In my case, I have a completefunc and still need it to be true for async. Is there something I am not seeing to do this? When I delete the "thisHasCompletefun ? false : " from that line, everything works for me but rather than changing spservices on my system, I'd rather understand the intent better.
Comments: For now, I have made a "version 2013.01a" and modified line 1220 from: ``` async: thisHasCompletefunc ? false : opt.async ``` to: ``` async: opt.async ``` I don't recommend others do this without understanding the implications but we needed other new functionality so this works for us. If I can do anything to assist in finding a true solution long term, let me know.