1. sandstorm871
  2. RO CSVI
  3. Wednesday, 10 August 2016
  4.  Subscribe via email
3 points here relate to the new/updated Google MC XML export that you have worked brilliantly on. We have pushed this live in on our sites this week & have these following notices. :pinch:


1 - Price needs to have the currency ie, GBP after the value not before, as per requirements from Google
currently <g:price><![CDATA[GBP 9.95]]></g:price>
needs to be <g:price><![CDATA[9.95 GBP]]></g:price>
------------------------------------------------------------------------------------------

2 - Shipping is wrong on any item that is 'out of stock'

In our case, this defaults back to RM 24 recorded with 4.50
<g:country>GB</g:country>
<g:service>Royal Mail 24 Recorded</g:service>
<g:price>4.50 GBP</g:price>
</g:shipping>
------------------------------------------------------------------------------------------

3 - Products with Price 0.00 are being exported
Please can products that have a price of 0.00 be excluded from the export
------------------------------------------------------------------------------------------

4 - When exporting URL's for images, product URL, etc the word "Helper" is added to the URL ,making all the URLs invalid.
i.e instead of http://mywebsite.com/images/myimage.jpg it exports as mywebsite.com/helper/images/myimage.jpg
Accepted Answer Pending Moderation
What this means is that for every child we also need to load the parent information as VirtueMart does. That is OK for VirtueMart as it only needs to load 1 parent per page load, we will need to do it for the complete dataset you are exporting, which is possibly the complete database. This will be a performance penalty.


Isn't this what you already do for children products for other ares such as;
categories, prices (where price is the same), image (where image is the same)
  1. more than a month ago
  2. RO CSVI
  3. # 21
Accepted Answer Pending Moderation
Hey Andy,

Isn't this what you already do for children products for other ares such as
That is what we do but these individual queries are becoming hard to maintain, so we are looking at a more solid solution. Advantage will be that we only need to load the parent once for all it's child products, that is some performance win we can get over the current implementation.
  1. more than a month ago
  2. RO CSVI
  3. # 22
Accepted Answer Pending Moderation
Hello Andy,
The patch for pulling manufacturer from parent to children is done. Please load the attached patch file and let me know how it goes.


patch_google_export_2016_09_09.zip
Attachments (1)
Kind regards,

Tharuna

=========================
If you use CSVI, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 23
Accepted Answer Pending Moderation
The patch for pulling manufacturer from parent to children is done.

Thanks Tharuna, I hadn't seen that until today so will test it later & let you know if there are any issues.

Also I am running a couple of versions behind, now & worried to update, because of so may patch files have been used.
If I update CSVi & the VM Plugin, are the patch files that you /roland have created all in the latest versions?

Thanks again,
Andy
  1. more than a month ago
  2. RO CSVI
  3. # 24
Accepted Answer Pending Moderation
Hello Andy,
The latest version of CSVI is 6.6.4 and it was released on 25 August 2016, all the fixes/patches till this date have been included with CSVI 6.6.4 version. Of course my latest patch is not in there and if you think if you have included any patches more after this date you may need to track them.
Kind regards,

Tharuna

=========================
If you use CSVI, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 25
  • Page :
  • 1
  • 2


There are no replies made for this post yet.
Be one of the first to reply to this post!