Paul

Oh. I forgot to mark this as resolved. Now it’s resolved.

Thanks again.

Aha! It seems that I can use the Month and Name common setting, if I switch the Product Permalink base setting to Default.

That seems to be working fine now.

Thanks again for your help.

-paul

It is worth noting that all the OTHER pretty permalinks worked fine before I went back to default. (That is to say “blog” and “calendar” and such were all pretty URLs and worked fine. In fact n7hrc.org/shop worked fine. It was just everything lower down than /shop/ that had trouble.)

My host is Hostgator.com, and they do have mod_rewrite turned on. I can’t access my .htaccess file directly while I’m at work, so I’ll have to see if the rewrite codes are in there after I get home.

I’ll check into that. Thanks for the direction. I’ll post back tomorrow — or whenever I hear back from my webhost.

Thanks! That works. When the first option is set to Default, the shopping cart works like I expect.

If I change it to anything but default, it goes back to not working.

Leaving it at default is a passable solution, but I’d love to figure out how to use pretty permalinks, if possible.

Common Settings: Month and name

Optional:
* Category base: [blank]
* Tag base: [blank]
* Product category base: product-category
* Product tag base: product-tag
* Product attribute base: [blank]

Product Permalink base:
* Custom Base: /shop

(The last one was set by WooCommerce. I had initially set it to “Shop base”)

Thanks for the advice. I don’t care too much about the caching, so I just deleted the plugin.

After deleting the plugin, I saved permalinks twice, like you suggested. Since I no longer have a cache plugin, there is nothing to reset.

Pages still show “404 Page Not Found”.

By the way, I just tried deactivating all plugins except for WooCommerce, then I re-generated the permalink structure, but that didn’t make any of the pages show correctly. All WooCommerce pages (except the product page) still return 404 errors.

Since plugins don’t appear to be the problem, I re-enabled all my plugins again as they were earlier today.

I’m having the same error message. It appears on my checkout page next to the sales tax line (tax is calculated for my state but not anywhere else).

Did you find a solution? I’m desperate to figure out what to do to fix this.

Thanks.

If I’ve got a blog on 2.2.2 (for plugin reasons) do I need to update that one as well? What release is vulnerable?

Thank you.

Upgraded to 2.0.1 on two blogs with no problems at all.

Quick question, though. Where in my interface can I verify that I’ve upgraded to 2.0.1? It only says I’m at 2.0. Did the footer of my control panel not get updated properly?

Um, I’d say, no. MT is not a better software package. I think WP is far better. But I admit that I’m very biased. Besides, WP is completley free. MT will cost you money. Make the “obvious choice” (your words ?? ).

As for WP not working properly, I don’t know that you’ve provided enough information for people to be very helpful. Maybe you could include information about where you are hosting your account, and what versions of PHP and MySQL you are running. I assume you are talking about a WP 2 installation.

I’d first try to get WP running without themes. Then once you are getting posts to display like you like, then you can mess with the themes. But we won’t know if it is a theme problem or a site problem or what if you don’t get it working first with the default theme.

You might have a database problem. You might try a fresh installation if you don’t already have content.

I’m pretty new to WordPress myself, and I’m a PHP novice. But I’ve learned enough to get by. And the forums here are pretty helpful, when you provide enough information that the experts here can actually help you. ??

Hmmm… I kept refreshing the page, and then I would get a error -1 and then an error 28. It was switching back and forth. So I contacted my host and told them that I was getting the mySQL error 28 (space) error (thinking if they could resolve the 28 error, then we could focus on the -1 error), and five minutes later the problem had dissappeared.

Now the site seems to be working fine. I wonder if the -1 error is the same thing as the 28 error, and the host was able to fix it.

I dunno. But I guess its working now, and I don’t know what fixed it, or I’d tell you.

If I find out that it was indeed my host that solved the problem, I’ll post back so others may know what worked for me.