Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Gungrinner

    (@gungrinner)

    Alas, no – I’m no coder, so tracking down whatever character or combination of characters is causing the warnings is beyond my ken. The clients insisted that there be an age verification function to the site to prevent anyone under the age of 21 from using the online shopping cart.

    We have a plug-in called ‘Terms of Use’ installed to that end. Could this be the culprit? Should we inquire of them?

    Thread Starter Gungrinner

    (@gungrinner)

    Yep, got plug-ins and zencart installed.

    We’re using a default wordpress theme – one of THE most default ones there is, the twelve-eleven theme.

    If the plug-ins or Zencart are the culprit, would then be the ones to supply this ‘patch’ that GoDaddy claims we need to be warning-free of these potential cross-scripting attacks?

    Thread Starter Gungrinner

    (@gungrinner)

    Given that the site was made through wordpress with no custom coding that I know of (I am no coder, and would not presume to even try tinkering with the code), where else would the code originate from?

    And if WordPress has nothing to do with it, then what might be done to resolve GoDaddy’s insistence that the coding is the cause? I’d love to see it fixed, but I’m sure any fiddling I try with the code would only make things worse…

    Thread Starter Gungrinner

    (@gungrinner)

    Yep – that was it. Thanks!

    Thread Starter Gungrinner

    (@gungrinner)

    Addendum: Switching to twenty ten DOES show the sidebar widgets. Why won’t twelve eleven play ball?

    (I have no inclination to switch themes at this juncture – the client is happy with the way it looks, except they want a sidebar widget that just won’t show up)

    Deactivating plug-ins doesn’t work.

Viewing 5 replies - 1 through 5 (of 5 total)