Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter scotte68

    (@scotte68)

    kstadden,

    Glad to help. If you ever have a sub-domain, there is another fix for that. I had to rename the top level htaccess and the sub-level htaccess. Took me many hours to figure out the sub-domain fix. :d

    B.Rgds,
    Scott
    MaricopaMinutes

    Maybe, If I understand your requirements correctly… maybe try s2Member? ( Membership w/ PayPal? ). Powerful (free) membership capabilities. Protect members only content. The s2Member Framework (free) integrates w/ PayPal? (very easy), and fully supports recurring billing. s2Member supports custom Pages for registration (including Custom Registration Fields), account access, and a lot more.

    B.Rgds,
    Scott
    MaricopaMinutes
    ScottsWebTips

    Are you using a plugin called “PageMash”?

    I had a similar issue. I clicked on the “Add” button but the button did not work.

    My issue was a New plugin I had installed was conflicting with DataFeedr.

    I know the DataFeedr ADD button was working in the past. So, I deactivated several of my plugins that were new and then my Add button started to work again.

    Then, I re-activated each plugin one by one until the ADD button stopped working.

    For me the plugin that was conflicting with DataFeedr was PageMash.
    I have de-activated pagemash and everything is working fine.

    B.rgds,
    Scott
    MaricopaMinutes
    ScottsWebTips

    I had the same issue. I clicked on the Add button and the button did not work.

    My issue was a New plugin I had installed was conflicting with DataFeedr.

    I know the DataFeedr ADD button was working in the past. So, I deactivated several of my plugins that were new and then my Add button started to work again.

    Then, I re-activated each plugin one by one until the ADD button stopped working.

    For me the plugin that was conflicting with DataFeedr was PageMash.
    I have de-activated pagemash and everything is working fine.

    B.Rgds,
    Scott
    MaricopaMinutes
    ScottsWebTips

    Thread Starter scotte68

    (@scotte68)

    Okay, just spent 30 min with my host and we figured it out.

    For Sub-domains, we had to rename the .htaccess file in the top level domain folder AS WELL AS the .htaccess in the sub-domain folder.

    I was then able to open a validation request and validate my sub-domain.

    Also, you may need to de-activate all plugins and use the default TwentyTen theme. I de-activated all my plugins and requested verification using the default theme.

    STEPS for TOP LEVEL DOMAIN
    – Deactivate all Plugins
    – Use the default theme TwentyTen
    – rename the .htaccess to .htaccessold
    – Go Back to McAfee SiteAdvisor and click “Request Verification File”
    * You should now see the McAfee Validation File name.
    – Create the file and upload to your host in the root directory
    – Go Back to McAfee SiteAdvisor and click the “Verify” Button
    – rename the .htaccessold to .htaccess

    STEPS for SUB-DOMAIN
    – Deactivate all Plugins
    – Use the default theme TwentyTen
    – rename the top level htaccess to .htaccessold
    – rename the sub-domain .htaccess to .htaccessold
    – Go Back to McAfee SiteAdvisor and click “Request Verification File”
    * You should now see the McAfee Validation File name.
    – Create the file and upload to your host in the root directory
    – Go Back to McAfee SiteAdvisor and click the “Verify” Button
    – rename the Top level domain .htaccessold to .htaccess
    – rename the sub-domain .htaccessold to .htaccess

    Thread Starter scotte68

    (@scotte68)

    I finally got it to work. here is what worked for me.

    – Deactivate all Plugins
    – Use the default theme TwentyTen
    – rename the .htaccess to .htaccessold
    – Go Back to McAfee SiteAdvisor and click “Request Verification File”
    You should now see the McAfee Validation File name.
    – Create the file and upload to your host in the root directory
    – Go Back to McAfee SiteAdvisor and click the “Verify” Button
    – rename the .htaccessold to .htaccess

    Done. ??

    Thread Starter scotte68

    (@scotte68)

    I’m using the default Theme “Twenty Ten 1.2”.

    Thread Starter scotte68

    (@scotte68)

    I tried a Fresh install of WordPress 3.1.3 (ScottIdeas) and I’m getting the same error from McAfee Site Advisor. I have absolutely no plugins installed. I deleted “Hello Dolly” and “Askimet”

    I have already submitted a request to McAfee. I’m hoping someone else may have any insight into this bug.

    Sincerely,
    B.Rgds,
    Scott

    Thread Starter scotte68

    (@scotte68)

    I have already tried….

    WHAT I HAVE TRIED:
    – I tried renaming .htaccess to .htaccessold and re-submitting (failed)
    – I tried the suggestions from this link (404 pages)
    I added the following to my header.php but they did not work :
    <?php header(“HTTP/1.1 404 Not Found”); ?>
    <?php header(“Status: 404 Not Found”); ?>
    <?php ob_start(); ?>

    – Downloaded CURL and checked the results:
    C:\CURL>curl -s-D – -o /dev/null https://www.scotts2012gear.com/no-one-here.html

    The CURL results clearly show that a 404 NotFound is returned.

    Thread Starter scotte68

    (@scotte68)

    Hmmm, well, I clearly listed what I have tried under the heading “WHAT I HAVE TRIED”.

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