Parsing From Site
It often happens that the supplier's price list is not informative enough to fill your site with full-fledged products: images, attributes, product descriptions, or product names.
But it will be enough for the plugin if the price list contains links to product pages. If there are no links in the price list, then they can be added manually.
Here is an example of a very simple price list:
Manually adding links to the price list is not as hard work as it might seem at first glance. Usually, 500 - 800 links can be added in 1 working day, without much stress. Another way to collect the site donor product URLs is to use their sitemap if available.
The main goal is to ensure the product SKUs and product links connection. So that the product SKUs in your store match the SKUs in the supplier's price list. This is necessary so that later, the plugin can automatically update product prices and quantities according to price lists.
How to set the parser to collect data
The parser task is to find the desired fragment in the page source code using your settings. You can set only 4 settings:
1. The column number containing the product page link (in this case, column number 4)
2. Parsing parameters: two texts in the page code, between which the desired fragment is located. In our example, the product name "Рюкзак Walker Ray Hype Black, 30x50x16 см" is between parameters content=" and "
so the parsing parameters will be like this:
However, according to these parameters, the plugin will parse the text website, since it occurs before the product name Рюкзак Walker Ray Hype Black, 30x50x16 см (see page code).
To refine the parsing "Keytext to begin, end parsing" is used.
3. They tell the plugin which piece of text to cut out of the page code in order to look for parsing parameters in this fragment.
If you cut a fragment from the page code from the text property="og:title to the page end, then the parsing result will be correct because the search for parameters will start from the text property="og:title:
4. It is possible to use "The number of occurrences" for the first parameter instead of "Keytext to begin, end parsing". In our example, the first parameter - the text content=" occurs twice in the page code, so this parsing setting will also be correct:
Parsing a password-protected website
If you are a supplier's official partner, and the supplier's website is protected from unauthorized viewing, then you must have a login and password to access the site pages.
This means that you can parse the supplier's site. More precisely, not you, but your server (website) on which the plugin is installed. And to be more precise, the form of the supplier in which you specified the parsing parameters is parsed.
The login and password for accessing the "closed" site should be set in the supplier's form, in the "Cron" tab in the "Main task" section:
even if you don't use cron.
Cron jobs can be disabled:
Parsing a price list cell
Sometimes suppliers add product attributes, not in separate price list columns, but in the "Description" column as a table under the description text:
The plugin will be able to parse this text into attributes in the same way as it does when parsing a web page. The settings will be like this:
1. The price list column number containing such descriptions should be set here:
2. Enable product attributes adding:
3. Parsing parameters set up: