tomzorz

I’m eager to know this as well – but as I far as I could tell by my logic is that google simply can’t get these indexed. Since they aren’t to be found in the site’s sitemap (cause they are virtual posts and not actual post types to be found by wp’s ecosystem).

Perhaps if you were to link to each virtual post on the index or listing page… In that case google could pick it up and index it, since it follows all links on your site. But otherwise, I don’t think the pages will be indexed at all.

But I’m curious to the answer of the plugin’s developer.

@aaatex Have a look at this topic: https://github.com/woocommerce/woocommerce/issues/11996

… However we are not returning meta values / fields on the API. …

So, it’s maybe not possible at all with the current WC api?

@lukecavanagh using the filter /wp-json/wc/v1/orders?filter[meta_key]=your_meta_key&filter[meta_value]=required_meta_value indeed works to trim the orders down, thanks for that.

But is there also a way to display this meta data in the response?

• This reply was modified 8 years, 5 months ago by tomzorz.

Yeah, I believe it doesn’t have anything to do with plugins or theme settings, css won’t solve it either.
It’s really in the theme code, I’d guess it would be somewhere in the single-product.php that is used by your theme, or at least start looking there. Are you familiar with it?

I noticed there’s also a javascript error on the page preventing the image zoom functionality etc, probably also caused by the duplicate thumbnails.

Although I don’t quite understand perfectly why, but adding 'query_string_auth' => true as an option solved it.

Meanwhile, I have been able to make a successful GET request through a simple HTTP client with the following url: GET https://www.aromacorner.be/dev/wp/wp-json/wc/v1/orders/5600?consumer_key=ck_xxx&consumer_secret=cs_xxx

I changed the url to contain ‘www’, wich did the trick with this simple get request, but doesn’t change anything when trying in with the given php code.
So why would that work with the http client and getting it through the php library give an Unauthorized error?

• This reply was modified 8 years, 5 months ago by tomzorz.

Hi Andy,

Well it seems indeed that your product thumbnails are loaded twice. Looking at the source code, ‘product_thumbnails’ is in the DOM twice – the second instance being the faulty one.

Somewhere in your theme code it’s being called/implemented twice…

Bedankt voor de antwoorden (ik zie ze nu pas), maar ik heb toch een oplossing gevonden (WC 2.6) ??

Dit dmv een 2e (gratis) locatiekiezer als shipping method op te zetten in dezelfde zone in combinatie met een functie die erg gelijkt op de snippet waarnaar @pieterclaesen refereert.
Die functie heb ik aldus gewijzigd zodat enkel de gratis shipping methods getoond worden (dus ook de gratis locatiekiezer) wanneer aan voorwaarden voor free shipping voldaan zijn (net zoals in gerefereerde snippit wordt dit gecheckt ahv ‘free_shipping’ method_id). Indien niet aan free shipping voorwaarden voldaan, worden enkel de betalende shipping methods getoond (incluis betalende locatiekiezer).

Indien interesse kan de functie gedeeld worden.

• This reply was modified 8 years, 6 months ago by tomzorz.
• This reply was modified 8 years, 6 months ago by tomzorz.

I did some further testing and you seem to be right… I was testing it in Firefox’ private browsing mode, but this seems to be the only non-working way.

So I’ll blame Mozilla ??

Resolved. Thanks!

Thanks for your answer.

Strange… the screenshot you give is what I need, but don’t get… You can check it here: https://aromacorner.be/ (click on “Vragen? Stel ze hier!” in the bottom right corner).

Sweet. I actually saw the show_on_cb boolean in the example, wondering what it was for, and hadn’t seen the callback function yet… Silly I missed that.

So thanks alot, it works like a charm that way!

I can’t find the product you are referring to in your products … But anyway, oxy indeed always crops in square ratio. Thus I have all my product photos made square as well, so there’s no problem. I don’t think there is another way around it …

By the way, our two previous solutions for the search results was useless work after all … In the Oxy admin > General > Header is an option called ‘Enable product search’, which does exactly what we were looking for …
But I guess we learned a lot from searching our way in the code ??

Doens’t matter where in the fuctions, just make sure its the functions.php file of your child theme ??

That solution I also tried, and worked, but I think the functions solution is better. Because when the Oxy theme has an update the hidden field will be gone again … And the functions one will always work!

Aha okay. Luckily I have found a solution meanwhile; might be interesting for you as well then.
Add this to your functions.php:

function search_results_product_type( $vars ) {
  if( isset( $_GET['s'] ) )
    $vars['post_type'] = "product";
   return $vars;
}
add_filter( 'request', 'search_results_product_type' );

… and all the search requests will get product as post_type and thus results will be shown nicely.