Quote Originally Posted by mc12345678 View Post
And as for this file, the only change(s) really were in the default text constants (as compared to the master version of the file in github) where that difference may just be "temporary" or recent. I would not expect that difference to really cause an issue though I would suggest checking to see if you have any debug logs generated as a result of using the plugin. I wouldn't be surprised if there is a missing definition that execution of the ajax code may stop and that could be preventing the next step from occurring and leaving the spinning circle... Just an idea...

Note that if no debug logs exist then there may be a separate issue preventing debug logs from being generated/written. I often will then try to force a debug log to be generated just to prove that it *can* happen which validates that the absence of a log is because there isn't a log worthy event occurring... Sort of "backwards" thinking but a logic principle.
Oh, and absent all of that logging issue/problem, while the initial claim was that this happened under version "3", was corrected and now is happening in version "4", indicates that if all else is good and correct (page validates, java code is sound, no php errors), then there is some problem with the way the data is being "handled" or processed that needs to be corrected... The fun part of that is figuring out what is erroring or not processing, when, and why...

Ideally though, perhaps you find some other modification had been made to the "older" site to make this work. It really could also be outside the scope of the plugin and instead something in another file that had to be modified to function. I saw that there were a lot of other scripts available/executed on the product page. Again I didn't have access to appropriate tools to follow the program flow to be able to see if one of other plugins might cause an issue with this... I mean, even loading sequence of those other plugins could make a difference as well... Etc...