Chris Eilander

@rudolfl by any chance, do you use an Apple device with the Safari browser?

I might have the same issue. However it works fine on Windows and Linux, but on Safari it shows the placeholder instead. I don’t own a Apple device myself but someone who visited our site today pointed out they didn’t work.

Same problem, disabling Advanced Coupons for WooCommerce Free seems to fix the problem.

I’ve answered on the github issue with my system status file.

I saw the updated and indeed it has been fixed. Thanks!

Ik heb natuurlijk voor de zekerheid de overschreven plugin code bewaart en weer terug gezet. Maar snap je punt.

Ik zou je net de debug log sturen en vertellen over een ander probleem wat ik vond, tot ik me 1 punt herinnerde die ik was vergeten. De cache plugin. Cache legen en ik krijg nu WEL de juiste elementen en het andere probleem was ook verholpen.

Het rare was wel dat als de feed hergenereerde zonder de Sale Price Field Mapping dat dat element wel uit de XML verdween.

Ja, ook als ik het veld verwijder, opnieuw genereer, en daarna weer toevoeg blijft het <sale_price>. Ik heb daarna ook geprobeerd een custom field van te maken om het te omzeilen, maar wegens de restricties op de naam van het veld is dat niet mogelijk.

Ik heb verschillende settings veranderd om te kijken wat de oorzaak kan zijn, alle strings in de Sale Price array veranderd naar g:sale_price in class-google_shopping.php (want je weet nooit. Veranderde wel de naam van de field mapping maar niet in de XML), zelfs de XML zelf verwijderd uit upload om vervolgens weer opnieuw te genereren.

Het hielp niets, altijd weer <sale_price>.

So even recreating a new feed with all the same settings always does it correctly, but the older feed always does it without the g:.

I think I’ll just have to recreate the feed and redo all the things in merchant center, which sucks.

Yes the existing XML feed shows <sale_price>1869.45 EUR</sale_price> while the one I just created shows <g:sale_price>1869.45 EUR</g:sale_price> for the same product.

As far as I can tell only sale_price is affected. When I added sale_price_effective_date on the existing one it does show it with g: in front of it.

I’m looking if I can recreate it on my test feed by removing the sale_price field mapping and adding it back.

I can confirm now that a newly created feed with the sale_price added during setup, does show <g:sale_price>, while an edited feed always shows <sale_price>.

• This reply was modified 4 years ago by Chris Eilander.

This is when the feed already exist, and we add the sale price field later by changing the settings and then choose field mapping. Perhaps its different when creating an new feed?

Here is an second opinion. I haven’t opened your xml feed before so it wasn’t cached in my browser.

The gtin for 25224 is <g:gtin>5710570005170/D1-PPRC2-E13</g:gtin> and seems also incorrect for any product thats older (lower item ids).
Also your identifier still says no for every product. Even newer products than 25224.

Do you still have the g:identifier_exists on plugin calculation? That doesn’t seem to work with the free version of the plugin so you need to change it to the static value of yes to have the plugin report the gtin’s. At least that was so in my case.

The debug info shows active_languages”:[“en”,”nl”], so they both seem active. We already have several pages with english translations, just not the products yet.

Relevant code would be

<?php namespace App\Libraries;
use Automattic\WooCommerce\Client;

/**
 * Class WebshopConnect
 *
 * @package App\Libraries
 */
class WebshopConnect
{
    private $woocommerce;

    public function __construct(){
      $url = getenv('woocommerce.url');
      $key = getenv('woocommerce.consumer_key');
      $secret = getenv('woocommerce.consumer_secret');
      $this->woocommerce = new Client($url, $key, $secret);
    }

    public function createProduct(array $productData){
      return $this->woocommerce->post('products', $productData);
    }
}

[edit]
Apparently one of my colleagues put the English language on hidden (I also didn’t know this was a thing), and this solved it.

However, I expected it to be a translation for an existing product when I add the translation, but instead it gets added as an new “Dutch” product.

View post on imgur.com

The top one should be a translation of the bottom one, if I understood the documentation here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/using-wordpress-rest-api-woocommerce-multilingual/

• This reply was modified 4 years, 9 months ago by Chris Eilander.
• This reply was modified 4 years, 9 months ago by Chris Eilander.