Settings → General. Settings shared by the whole panel, arranged in groups.
Interface
Panel language. The list is built from the files in core/Lang — to add a language, put another file there.
Store
Only the things the program cannot work out on its own; the rest it determines and shows under Diagnostics.
- Where to put attributes. Into catalogue filters — where attributes are used to narrow the catalogue; or into product options — right on the product card. What these are called depends on the engine.
- Attribute names that mean the manufacturer (brand). One name per line; case and surrounding spaces do not matter. A name that is not listed ends up as an ordinary attribute and the product’s manufacturer stays empty.
- Attributes not to transfer. One name per line. This is usually where things that are unique per product go — “Model”, “SKU”: there is nothing to filter by, and they bloat the value list.
- Supplier currency rates. One line per currency, like
USD=41.5— “one dollar is 41.5 in the store currency”. Needed where the store has a single currency and cannot convert. A currency not listed goes through unchanged.
Price update
Products per pass — the batch size the queue is processed in. Lower it if a run does not fit the hosting limits. Empty means the value from config.ini.
Scheduled runs
Periods and the scheduler URLs are covered in the cron article.
Diagnostics
The neighbouring Settings → Diagnostics shows the environment: PHP version, extensions, hosting limits, the database, the state of the queue and what the program worked out about the store. Next to every value it says what that value affects.
A yellow line does not stop the work: the program adapts to the limit and does less per request. A red one is something without which part of the work cannot happen.