Forum Replies Created

Viewing 15 replies - 16 through 30 (of 44 total)
  • Thread Starter MoonDog

    (@moondog)

    It doesn’t matter if it’s complete or quick scan, the result is the same. The scan page doesn’t load at all and it’s basically frozen. I have to close the browser as well. A screenshot wouldn’t do any good because it’s not going to show you anything other than the screen you see when you click on Run Scan.

    Is the newest version still compatible with WP 3.5.2?

    Thanks for the offer but I don’t allow anyone access to my WP Admin area.

    Maybe I’ll try deleting the plugin and reinstall it.

    Thanks.

    Thread Starter MoonDog

    (@moondog)

    Thanks for the reply. Part of the problem is the wp-login patch you referenced. I’ve already got my login redirected to a different url that helps prevent brute force attacks. Is there a way to disable that feature after your plugin has been installed?

    I think you’ve come up with a very useful plugin for WP users, but I’m not comfortable installing anything unless I know of other sites using it without issue.

    Thanks.

    That appears to be an issue with your SSL. If you’ve enabled “force SSL” in the Woo settings, all of the pages that use https must work with your SSL. If the pages don’t load, it could be an issue with your CDN, a plugin, or your .htaccess file.

    Thread Starter MoonDog

    (@moondog)

    I figured out the problem. For anyone using the uDesign theme, either remove the theme’s H1 tag for the Shop page or remove the H1 tag from wp-content/plugins/woocommerce/templates/archive-product.php

    You can use any number of the widgets that are supplied with Woo. You can insert widgets on the any page you like. I use “Best Sellers” and “Featured Products” on several pages, especially the Shop page.

    You might try using the Cart Notices plugin which allows you to isolate situations like those you described. I’m not saying it’s an absolute resolution, but it’s worth looking at.

    The base tax rate applies to your state, not another state. If someone from outside your state purchases something using the online checkout process, then the tax won’t populate. It doesn’t matter if that transaction is a local pickup or not. The tax won’t apply to anyone purchasing something via the online checkout process that resides outside your state.

    If someone picks up directly from your store, why would they use the online checkout anyway? You could log into the virtual terminal of your payment processor and run their card (or use a pos terminal, if that’s how you do it), or you could accept cash or a check.

    If someone residing outside your state chooses to pickup directly from you and pays in advance using the online checkout, you haven’t generated a sale to a resident of your state. Just because they choose to pickup directly from you doesn’t mean you have to collect the tax.

    In fact, I wouldn’t. If I paid for something online then have you try to charge me tax just because I’m picking up, I’d ask for a refund.

    It’s up to you, but that’s how I do it. I’m not losing any sleep.

    Just to understand what you’re saying, you’ve got the standard tax rate set up in the Woo general settings, correct? In doing that, you set up your state’s sales tax.

    Based on what you wrote, the tax rate only applies to your state. That’s the way it’s supposed to be. You wouldn’t charge your state’s tax to a resident from another state.

    Maybe I’m misunderstanding you. Let us know if we’re on the right track.

    It does, but not with Woo ver 2.0.11. If I were you, I’d stick with ver 2.0.10 and everything should be fine.

    Thread Starter MoonDog

    (@moondog)

    Let me know how to revise the title. I’ve got major issues with my site and haven’t had time to check back here.

    I replied to my Woo ticket late yesterday and received another “gee, I’m sorry, we’re working on version 2.0.12 that will solve everything” reply.

    I’d advise anyone that updated to version 2.0.11 to revert back to 2.0.10 and wait at least a month when they release 2.0.12. I’m not taking any chances again.

    Thread Starter MoonDog

    (@moondog)

    @normanbird – Well it hasn’t been easy for me. I’m having to reinsert every product image, reset all the basic settings, reinsert all of the shipping and payment gateway settings, reset all of my menus and reinsert all of the widgets. When an update costs me hours and hours of MY time, then I’ve got no problem calling them out. I’ve spent a lot of money buying plugins from them so they’ve more than made their money from me. They replied to my ticket and claimed it was a “slight” issue. Slight? Clearly not.

    Thread Starter MoonDog

    (@moondog)

    One other thing I’ve noticed with every Woo update is the inclusion of the Share Your Cart plugin, which I absolutely hate. Every time there is an update I have to delete that plugin via FTP. Why would a plugin be included that isn’t part of the core code? The Share Your Cart plugin is a piece of junk and I don’t want it included in new updates. Getting the drift Woo?

    I had the same issue as well, including those mentioned in the other thread.

    Thread Starter MoonDog

    (@moondog)

    @normanbird – Thanks for that info. I was reluctant to deactivate 2.0.11 until someone confirmed it’s okay to do it. Did you delete 2.0.11 entirely, then upload version 2.0.10?

    Thanks.

    Yes, I’m the one who started that ticket. But you know how Woo is. Thanks for adding yourself to those of us that have had issues with the update.

Viewing 15 replies - 16 through 30 (of 44 total)