Well, I can’t really tell you much. The guy looked at the source code and found things that looked out of place. He read off some of the code and asked me if I had added it. I told him that I mostly only added words and pictures through Rapid Weaver - although I did add a bit of code for PayPal. He then ran a malware cleanup program. It still didn’t work until they totally reloaded something (not sure what) to the IP address. It took quite a while for him to sort it all out. He also thought the SEO that I had purchased might have caused a bit of trouble. A friend had looked at the code via Safari last night and noted that there were some odd things, but we didn’t try to pursue it. Wish I could give you more info, but mostly I waited while he worked! He also showed me where the malware cleanup link is on the Go Daddy site. Something new every day! Linda K
I remain skeptical about Godaddy’s explanation then. In the past I had sites hosted on godadddy and they suffered php injection attacks due to Godaddy’s very poor security (or the lack of it). Then they tried to obfuscate the cause with some vague explanation and deflect the blame away from themselves.
Not trying to convince you one way or the other - they got it working. I am not sure what you can see and what they can see. I do pay for some security on the site. This is the first time anything like this has happened. I do not do marketing for them! L
I realize you’re not try to convince me one way or the other, nor that you do marketing for them - not sure why you’d think so. Just that Godaddy’s explanations have to be taken with a grain of salt as they often are either not accurate or entirely fabricated as excuses for their poor security or other corner cutting. If you could articulate the relevant details as to what their explanation was, or post what they wrote as their explanation, that would help to see if they’re blowing smoke or not.
I did not write down what was said, nor can I repeat it with any accuracy. All I can say is that they were able to fix the problem, which you were not able to do. It probably wasn’t a rapid weaver issue so why do you care? I can’t tell you any more, but I will say that My goal was solution of the problem. I consider this closed. L
That’s exactly why - the problem may have been a RW issue, may have been user error, or may been Godaddy, or any combination of those. But since that was not clarified, anyone who has a similar issue in the future and asks for help here will not gain any insight into the problem.
OK fair enough, but you guys were no help. Told me it was an FTP provider problem. Basically sent me back to go daddy. What was I supposed to do? Sorry. Can’t give five stars to RW support this time. LK
Let me also remind you that I have used both rapid weaver and go daddy for more than ten years with few problems. This was a very recent problem and, as I said, it was fixed. I don’t think it is very professional of you to be so overtly hostile about a service I am using, or so defensive about rapid weaver ( comment that thousands use it with no problems). I am going to consider this conversation over, as I cannot be any help to you. LK