Hi Stefano,
Thanks for using our plugin and reaching out to us. Do you happen to have a document from Trovaprezzi with their official feed requirements in it? If so, we can possibly create a template for it.
All the best,
Eva
Hi Eva,
thx for your answer 🙂
there is no official english documentation, but at this page you can see a precise description of the nees:
https://feedonomics.com/trovaprezzi-feed-specifications/
and in this page you get a preview of the feed structure, that has the same requirements of the one i added in my first statement:
https://www.merlinwizard.com/integrare-e-commerce-trovaprezzi.htm
if you look at the default xml of the plugin, you have a <product> tag as delimiter ofeach prodcut, but trovaprezzi requires this tag to be <Offer>, and the names must be in upper case on the first letter and so on.
if there is some documentation about creating templates, please link it to me 🙂
thx,
s.
Hi Stefano,
Thanks for the links! We just started on creating the template but we already run into an issue. The two links you copy/pasted say different things, especially when it comes to the field names.
For example:
Feedonomics says: links
Merlinwizard says: Product Url
And this happens for a lot of fields. So, which one to use when creating a template?
All the best,
Eva
Hi Eva,
and thx a lot for your help 🙂
just refer to my first structure: it’s the one i already created for the project, but now i’m looking for a more flexible solution, so i’m trying to use plugin, but a working feed has been already created, and the structure is the following (i’ll give you the entire xml/php code, so you can see how the feed is now working: there are custom taxonomies, custom fields, and an “if” selector on the price):
<products>
<?php while(have_posts()) : the_post(); ?>
<offer>
<name><![CDATA[<?php the_title_rss(); ?>]]></name>
<brand><![CDATA[<?php echo do_shortcode(‘[wpv-post-taxonomy type=”product_brand” separator=”;” format=”name” order=”asc”]’); ?>]]></brand>
<description><![CDATA[<?php the_content_rss(); ?>]]></description>
<price><![CDATA[<?php
$sale = get_post_meta( get_the_ID(), ‘_sale_price’, true);
$regular = get_post_meta( get_the_ID(), ‘_regular_price’, true);
if ($sale)
echo $sale;
else
echo $regular;
?>]]></price>
<![CDATA[<?php echo $sku = get_post_meta( get_the_ID(), '_sku', true); ?>]]>
<link><![CDATA[<?php the_permalink_rss(); ?>]]></link>
<stock><![CDATA[<?php echo $stock = get_post_meta( get_the_ID(), ‘_stock’, true); ?>]]></stock>
<categories><![CDATA[<?php echo do_shortcode(‘[wpv-post-taxonomy type=”comparatori” separator=”;” format=”name”]’); ?>]]></categories>
<image><![CDATA[<?php echo do_shortcode(‘[wpv-post-featured-image size=”medium” raw=”true”]’); ?>]]></image>
<shippingcost><![CDATA[7.90]]></shippingcost>
<partnumber><![CDATA[<?php echo $pn = get_post_meta( get_the_ID(), ‘wpcf-codice-produttore’, true); ?>]]></partnumber>
<eancode><![CDATA[<?php echo $ean = get_post_meta( get_the_ID(), ‘wpcf-codice-ean’, true); ?>]]></eancode>
</offer>
<?php endwhile; ?>
</products>
hope this can describe enough the needs 🙂
thx,
s.
oh, i noticed the line with the “code” (sku) values has been stripped, so i try to insert again with some spaces to trick the engine 🙂
< code ><![CDATA[<?php echo $sku = get_post_meta( get_the_ID(), ‘_sku’, true); ?>]]>< / code >
Hi Stefano,
We have created our own very flexible template engine so making changes in the PHP-code of the plugin itself is not something we prefer. We just need to make sure we are using the correct and official field- & header names for the template to be created. So, you are sure the first one you described is the correct one that is being accepted by Trovaprezzi?
All the best,
Eva
Hi Eva,
if you prefere you can directly download yourself here:
http://www.lascienzadellasalute.it/trovaprezziok.xml
this is “Trovaprezzi validated” and is being working since 1 year ago 🙂
ciao,
s.
Hi Stefano,
No news yet unfortunately. It is still on our to-do list. As we are currently working on a big new feature (adding Dynamic Remarketing features to the plugin) we do not have much time to pick up other issues.
Anyhow, we did not forget about it 🙂
All the best,
Eva
