Jump to content

Paul C

Members
  • Posts

    801
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Paul C

  1. Tina, No not quite yet. I still have work to do on sections 4 (attributes) and 5 (specifics for apparel in US) and then section 6 (Tax and shipping) and 7 (Nearby stores - which ties in with Google Places for "bricks and mortar" retailers). Weight now comes in under the tax/shipping section it would appear. I'm basically trying to get as much done as possible without starting to require additional data entered, although this will be required for the "Google Product Category" field under the basic information section (1) - currently not implemented either. I also have code contributed that allows uploading to Google from within the module, which I have still to add in. The document I'm using for reference is: http://www.google.com/support/merchants/bin/answer.py?answer=188494 Paul
  2. Many thanks. Uploaded now.... fingers crossed lol Tried to fix a problem with French/German feeds, but ended up breaking them all...
  3. Ah. It's bloomin' obvious what the problem is now that I think about it...... We can consider 0.7.3.1 a non-starter then About to upload a tweak that will hopefully solve it.... 0.7.3.2 Paul
  4. Version 0.7.3.1 Uploaded as another attachment to the first post in this thread. This is just to clean up a few things. Change log - Removed html entity conversion on product name and manufacturer name (both should be text only anyway) - Fixed bug with selection of gtin field - Added "None" option to gtin field (now EAN/UPC/NONE) - Minor code restructuring to support additional features later Paul
  5. Looks like a bug. Hmm. I'll have a look and post something shortly. Paul
  6. Yes, sorry the terminology is all messed up. Prestashop "Manufacturer" name field gets mapped to the <g:brand/> element Prestashop "UPC" or "EAN" gets mapped to the <g:gtin /> element Prestashop "Supplier Reference" gets mapped to <g:mpn /> Regards, Paul
  7. They only insist on 2 out of the three pieces - 0.7.3 has an option to omit the EAN/UPC completely. Will post it up soon once I've tried out a couple of other changes Paul
  8. Better to leave out the UPC/EAN (if there isn't one/the number you have is invalid) and use the supplier reference (manufacturer/your part no) and a manufacturer. Paul
  9. Note that in the UK it will be the EAN number (also referred to as EAN13; usually the number on the barcode). It's one of the things that can get you ahead of the competition I guess in some cases it won't be as important, but it does allow google to group products/ If you search for "canon digital camera" in google for example, you should see a link with "Shopping results for canon digital camera". If you click on one of the product images you'll see that all the sellers (well the top ones anyway) are displayed below the description. It's more likely that someone will click one of the pictures in my opinion, than the link above... Paul
  10. The problem is that you could but it doesn't necessarily mean you'll get your products viewed/they will do you as much good as they would if Google could show your products alongside other retailers. The higher the quality of information, then the more benefit you'll get basically. Paul
  11. If you're in the US then as of next month all clothing items must be listed individually by attributes (i.e. each colour/size combination) with two of the following: 1. Manufacturer 2. Manufacturer part number 3. UPC code (EAN in the EU/elsewhere as applicable) Paul
  12. @umadbro Can you send me a link to an example of what's being generated please so I can have a look (also the store address where the products are displaying correctly would be good, if not at the same url). Regards, Paul
  13. @devilsown Did you have an older version of the module installed previously or is this the first time you've installed it? Have you also tried refreshing the page to see if it subsequently shows as installed? Paul
  14. Tina, these are currently required for US users only but yes I'll be adding for support for them shortly... at the moment they're still optional for non-clothing items though (but will generate warnings; plus, if your competitors are using them, then it stands to reason that you'll need to as well...). Paul
  15. @mgamer20o0 You need to register with Google Merchant Center and then upload your xml file. Currently there is no automated generation or ftp upload. Paul
  16. @magpole 1. The shipping weight warnings should be solved in future releases when I add the logic to include shipping (and tax) information. Should be soon. You don't need the UPC or EAN13 code (so the gtin choice of EAN13 or UPC will also include an optional "None" in future releases) as long as you DO have BOTH the Manufacturer and the Manufacturer Part Number (MPN). The MPN value is taken as the "Supplier Reference" field currently, so you can fill in those values -- I'm considering making this also a choice i.e. between "Reference", "Supplier Reference" or "None" (the latter is only for people specifying an EAN13/UPC code!), again in the next sub-release or two. Can you send me the url of the feed on your site so I can see what's happening with the UPC field please? A note of what's entered in the database for one of the affected products would be good too. The Google Product Category is a little more tricky, although not impossible (I'm deliberately ignoring it for now as it is optional). This will require a mapping between the store category and the "official" Google categories (at category level) or will need a second category structure somehow so a product can be placed in the Google categories individually. Paul
  17. The UPC number is padded out to 12 digits (leading 0's) It HAS to be a number - are you using numeric UPC codes, or using that field for something else? Paul
  18. @jovil That's really weird. I have noticed that in 1.4.4 (and I assume earlier versions) if you click "delete" against an installed module, then copy the files back to the server via ftp, then refresh the Back Office page, it thinks it's still installed.... I would have thought it would have run uninstall() on the module first before deleting but looking at the code, it doesn't... The whole uninstall could be deleted as the only reason for having it is because I don't like the config table filling up with module settings for modules that are no longer in use. For that reason I delete them in the uninstall function. Nobody else appears to though, so maybe I should just give up on that lol Paul
  19. I don't have a 1.3 install currently (am building one now) so many thanks for that jovil. Uploaded 0.7.2 to the first post. 1. Not absolutely sure why it's not appearing in tools, have added {compat=xx} text to the title at the top of the config screen and it would be good if you could let me know what that is saying... I have changed the logic for compatibility a little just in case anyway. 2. There are differences in the table. Hoping it's fixed now.... 3. There should be a CDATA around i to ensure that the feed is valid, but I'm not certain whether html is allowed or not.... 4. Image links should be fixed - I assumed that 1.3 generated similar to 1.4 Doh. 5. What happens at uninstall? There's nothing particularly complex going on in there... Paul
  20. @magpole What version of Prestashop are you using, and did you enter a description for the feed? You need to enter something in the description box and click the "Update Settings" box at the bottom the first time you use it. I'm wondering if a default might have been a good idea... Paul
  21. Can you post a screen shot - that doesn't sound like what I get in 1.4.4.0... Paul
  22. You could try this one for me: http://www.prestashop.com/forums/topic/124794-module-google-base-new-beta-version/ If you have more than one image for the product it will also use a second one (and seems to generate the correct links... at least on my 1.4.4 test). Paul
  23. Hi Folks, Finally, after a long, long time I've updated my take on the Google Product Search feed generator. The intention is to extend it to take account of all the various country rules and regulations, but for now this implements the current minimum for most cases (Sorry to folks in the US, but the additional requirements for Clothing and Variations aren't in there yet). The main outstanding issue that I would expect to see is blank pages when running on shared hosting and having a large product inventory. This is often due to memory and/or execution time limits on the server. I'm hoping to add more features to help mitigate this in future versions. I was going to hold off releasing this until it was a bit more developed, but had second thoughts, and here it is. In pre 1.4 versions it should appear under "Tools" and in 1.4+ under "Advertising & Marketing". Any help testing is most appreciated. EDIT: I've added a page on my site with a form at the bottom to submit bug reports: Google Product Search Beta Information and Bug Reporting *** Latest Versions will always be attached to this first post *** Paul googlebase_0_7_1.zip googlebase_0_7_2.zip googlebase_0_7_3_1.zip googlebase_0_7_3_2.zip googlebase_0_7_3_3.zip googlebase_0_7_3_4.zip googlebase_0_7_3_5.zip
  24. It should be a text link in the Tools tab, if not don't worry I've seen admin tabs go awol before, but it's (relatively) simple to fix. There are two different things going on here though. If the tab is Missing, then you need to add it in: In the Back Office you need to go to Employees --> tabs and click "Add New" Name : Upgrade Class: AdminUpgrade For the image Browse to the 1.4.4 distribution on your PC and select : /img/t/AdminUpgrade.gif Parent: Tools That should add it in. If it's greyed out, then it may be that the access permissions are wrong. Unfortunately you can't modify the administrator permissions..... From phpMyAdmin you can modify the ps_access table though to get it to work properly. I'll go through it manually step by step, so you can see what's happening: 1. Go to the table ps_employee and note the id_profile value for one of the administrator accounts (they should all the the same) default will likely be '1'. You can next verify that the user is an administrator by looking in the ps_profile_lang table for the record(s) that correspond to a profile_id the same as you've just obtained. There will be one for each language (each id_lang). 2. Next execute the following SQL: SELECT id_tab FROM `ps_tab_lang` WHERE `name` LIKE '%upgrade%'; ...and then note down the value returned - there could be more than 1 result but all should return the same number (e.g. '93') 3. Go to the ps_access table and execute the following (remember to replace the placeholders with the values you got from steps 1 and 2 respectively): SELECT * FROM `ps_access` WHERE `id_profile` = '<number from step 1>' AND `id_tab` = '<number from step 2>' e.g. SELECT * FROM `ps_access` WHERE `id_profile` = '1' AND `id_tab` = '93' You will either get a row returned or not. If you do get a row returned: 3a. Edit the row and set the values for 'view', 'add', 'edit' and 'delete' to 1. If they already are and the fields are still grey, then post back If you don't get a row returned then: 3b. while viewing the ps_access table click on the 'Insert' tab at the top of the main listing area, and enter the following values for the fields (in the first set of boxes, you may be offered more than one) and click the 'Go' button below: id_profile: <enter number from step 1> id_tab: <enter number from step 2> view: 1 add: 1 edit: 1 delete: 1 4. That should have fixed it Paul
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More