Rudo,
So the issue was in the CaSe of cfsSearch in many of the files where is was looking for the path of a fiel you had cfssearch (all lower case) which was not a valid path as JS is case sensitive. No all the locations where you had cfssearch for a css class name or css rule that was fine because convention is that class names are all lower case. So with a little tweaking it now works fine (as far as adding the widget without error). I could not test your layer obviously as it is a local url to your machine and not a public url. I did remove the blanks you inserted in the uselists as there is code in the widget to do this if the field is not marked as required.
Just FYI, you have 7 other posts out there about the eSearch that I have answered and you have not marked as answered.
And is there a particular reason you are still using 1.2?... Each new release the fix bugs and the product gets better. It will always be in your best interest to keep up to date.