JigmeDatse

I think I got it working now. I seem to be having an odd week in terms of breaking (but managing to fix them) things over and over (different things, so far not broken the same thing…) Thank you.

It seems that maybe the best thing is to use a theme which is known to support WooCommerce. It seems that you either need to have a developer familiar with WooCommerce, or you need to use an already created theme which supports WooCommerce. I’m not sure. It seems that it could be a big deal to “fix” these issues. I haven’t spent enough time looking at it yet. I have something that “mostly works” but not well at all.

Yeah, I really do understand that. I guess the issue that I was seeing is that your “theme integration guide” really doesn’t talk very much about what a person might need to look at in order to do so. When doing what was suggested it broke it even worse than I expected. It’s fine really. You guys really are doing a great job. It’s just that because all of these projects (WordPress, Themes, WooCommerce) are so large that unless things are really well documented it is next to impossible to know where you have to go to fix an issue.

One of the things which I found when I was dealing with issues, is that a lot of the “problems” that come up, end up pointing not to the file causing the problem, but the file which is doing what it is *supposed* to do, but because something else did something “wrong” earlier, you get a message which makes things hard to debug.

I guess, maybe I am *not* a developer that I think I am. I’m the developer who wants other people to develop in a similar way that I do. “Get it right first” rather than “get it out first”.

Which might be why I really don’t so much want to work with other people for anything I’m developing. I ask questions about what the *right* way things are done, and usually get answers which are what the *fastest* way to get things done.

Fortunately, a lot of the time, I find through digging deeper that I might be able to figure out what the *right* way to get things done is.

Not sure that really fixes the issue. At least, it doesn’t go far enough. I may have to play around a bit with things it seems. Like quite a lot. That’s OK. More learning to be made.

This appears to have fixed the issue. Thank you so much for looking into this so quickly, and giving me a solution. It appears you have pushed two versions since I posted this, or at least the version is reporting as 8.0.5

Jigme Datse Yli-Rasku

I’m not sure if this is related, or even identical to the issue which I am having, I have a <div id=”main”> which contains my main content (including a couple of sidebars if I am correct), inside that the WooCommerce content is in a <section id=”main”> and it appears that whatever is generating this code, is setting things up so that unless the CSS treats <section id=”main”> and <div id=”main”> differently there is likely to be an issue.

This shows up for me on the Store page, but from what I can see, not on other pages. Cart, Checkout, and Account pages seem to not have this issue.

I have tried to figure out where that is being generated, but having two elements with the same ID causes validation to fail. Now, I might be wrong that even though they are different element types <div> and <section> it *still* fails.

Looking it *may* be that on the shop page, I haven’t overridden the theme’s way of producing pages, so I am getting things setup the way the theme wants, in conjunction with how WooCommerce is “calling” things. Will look at my child theme.

I’ve found where for the “shop” page that is being set, but I see nothing clear which is telling me why the shop page is getting that call, while the other WooCommerce pages are *not*.

Yoast SEO in this case seems to be somewhat unaware of how Google will see a WooCommerce product, or at least based on what you are saying. Changing the way things are displayed is *not* going to change how Yoast SEO reports to you, but it *might* affect your SEO ratings.

At least that is my understanding of what is going on. I will look to see how Yoast SEO is reporting stuff in a Product tab, but I think your problem might be that Yoast (as you have it configured) is not aware enough to handle WooCommerce products fully.

My understanding is that Yoast looks at input in the editor, *not* the resultant page, and if the resultant page “looks” different than what Yoast is looking at, Yoast is unable to fully understand what SEO is going to work.

It *does* seem that Yoast may well be the best SEO package, as the 1, 2 ratings when people talk about SEO, are Yoast, and All in one SEO. But *most* of the people who are promoting All in one SEO, are very closely related to the development of All in one SEO, and so far, *no* sign that anyone connected with Yoast is promoting in that way.

This was not really *ever* a WooCommerce issue. This is more for information for those who might be looking at why they might be having issues.

There were a few settings which were displaying. What I noticed is that the current settings did display very briefly, then disappeared after a fraction of a second. After playing with disabling and enabling plugins, I got them back. I haven’t looked yet at the current version which I just upgraded to.

I think that there seems to be a lot of issues with the latest version of WordPress with a number of plugins, so the issue *might* be one with things which have happened with that.

Jigme Datse Yli-Rasku

Are other emails from the site working?

What version of WooCommerce are you using?

I know with another unrelated plugin, I have “admin” emails working, but for some reason the messages which were sent to the “client” never showed up at all. Not even in the spam folder.

I wish I could help you. I wish I could help me. Good luck.

This is with WordPress 3.2.1 and WordPress eCommerce MarketPress version 2.1.3. I really hope to be able to get this working today. Seems like a few people are having recent issues with it. Maybe this is a new version with new issues? I hope this can be figured out quickly.

I’m trying to setup this myself. I’m having trouble with an internal server error. Trying to get as much information as possible about what is going on will really help.

For me, I get PayPal and Manual Payments, with other payment gateways being greyed out. I don’t know what the issue is. Could be some conflict with another plugin?

It was posted at the exact same time, with the same format. And I don’t have anything going to Plurk except my blogs.