Check out the LimeSurvey source code on GitHub!

JS code displayed in preview and published survey after installation

More
5 years 9 months ago #59446 by screencaffeen
I've installed LimeWire and the installation seemed to go just fine, however after I created my survey, the preview (and published view) shows the following code before each question:

click="if(typeof(jsCall)=='function'){jsCall();}else{setTimeout('jsCall()',500);}" />

Anyone have any ideas about this problem? This is hosted on GoDaddy. I've installed LimeWire on another server and have the same problem.

Version 1.90+ Build 9642

Please Log in to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #59447 by c_schmitz
Maybe you should install LimeSurvey instead of LimeWire?

Seriously, this is no Javascript code like that in LimeSurvey. Looks like something infected your webspace.

Best regards

Carsten Schmitz
LimeSurvey project leader
Last Edit: 5 years 9 months ago by c_schmitz.

Please Log in to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #59453 by screencaffeen
Total Brain Freeze. I installed LimeSurvey not Limewire. Can't be something that infected my webspace, happens with installations located on two different hosting companies.

I downloaded LimeSurvey, unzipped it, then ftp'd it across to the server. Then set up the mySql databse,edited the config.php file, and ran the install script.

Any other ideas?
Last Edit: 5 years 9 months ago by screencaffeen. Reason: Adding more details

Please Log in to join the conversation.

More
5 years 9 months ago #59698 by screencaffeen
I spent some time tonight searching through the SQL database, and sure enough, my hunch was correct. The strange code that was popping up throughout the survey had populated various fields in the database (mostly in the question and answer tables).

Cleaning the miscellaneous code out of the various tables solved the problem. Not sure where the code came from, but based on research that I did, I suspect the Firefox Browser Highlighter may have been the culprit that introduced the issue to begin with.

Please Log in to join the conversation.

Imprint                   Privacy policy         General Terms & Conditions         Revocation information and revocation form