Extended tags

Instructions for Extended Tags

What the add-on does

The add-on extends standard CS-Cart tags: it adds language-specific tag names, uses these names when searching products and pages, displays the localized name on tag pages, and adds extended import/export schemas.

The add-on has no separate settings page in the add-on card. Once active, it works through standard CS-Cart tags, products, pages, layouts, and import/export tools.

Where to find it

The main tag workflow stays in the standard CS-Cart sections where product and page tags are managed. When a tag is edited, the add-on saves the tag name for the current language.

Storefront blocks are added through Design → Layouts → the required layout or page:

• MS: Page tags — displays page tags as a menu. The parent page ID controls where the block is displayed.
• MS: Blog tags — displays a blog tag cloud based on the standard tag block.

Import and export are available in the standard Administration → Import data / Export data sections. The add-on adds schemas for tags, tag links, and tag SEO data.

Working with multilingual tags

To set a tag name in another language, switch the administration panel language and save the required tag name. The add-on stores the value for the selected language and uses it on the storefront for the tag page, breadcrumbs, and blocks.

When a customer or administrator searches products or pages by a translated tag name, the add-on matches this name with the base tag and returns the linked objects.

Page tags block

Add MS: Page tags in layouts and set the parent page ID (default 186; replace it with your page ID). A nonempty ID is required: the block appears on that page and its immediate children. This controls visibility, not tag selection: tags come from text pages with a translation in the current language.

Tag filtering uses an existing ms_subpages list. The add-on does not create that list if it is absent. With no matches, the current handler does not replace the original list with an empty result.

Blog tag block

For the blog, use the MS: Blog tags template in the standard tag block. The add-on selects tags linked to Blog-type pages and displays them with localized names.

Import and export

The add-on adds separate data exchange schemas:

• Tags — exports and imports tag names with language data.
• Tag links — transfers links between tags and objects.
• SEO — exports and imports tag SEO fields when a compatible SEO add-on for tags is active in the store.

The import options include Skip creating new tags. Enable it when the import should update only existing tags and must not add new entries to the tag directory.

How to check the result

1. Create or open a tag in the default language and save it.
2. Switch the administration panel language, enter the translated tag name, and save the changes.
3. Open the storefront in the corresponding language and check the tag page: the title and breadcrumbs should be shown in the selected language.
4. Add the tag to a product or page, then search or open the tag on the storefront.
5. Add the MS: Page tags or MS: Blog tags block to a layout and make sure the required tags are displayed.
6. Run a test tag export and check that the file contains language data, links, or SEO fields depending on the selected schema.

If tags are displayed incorrectly

Check that the translated tag name is saved for the required language and that the tag is linked to a product, page, or blog post. For the page tag block, also check the parent page ID and the block placement in the required layout.

File fields and import limitations

Export a small sample from the required scheme first and retain it before importing. Import requires catalog management permission; export requires catalog viewing permission.

• Tags: tag_id, Language and tag are required; Language is a language code, tag is its translation, and Company is optional.
• Tag links: Name is the base tag name, Company is a numeric company ID, Object_id is the object ID, Type is P for products or A for pages. Name, Company and Type are required by the scheme; provide Object_id for a meaningful link.
• SEO: Name is required. AB:SEO:H1, AB:SEO:description, AB:SEO:page_title, AB:SEO:meta_description, AB:SEO:meta_keywords and AB:SEO:language are available only with active ab__seo_for_tags.

Do not create new tags is enabled by default and requests update-only handling for missing records. However, the Name converter in the links scheme can itself create a tag or activate a pending tag during matching. Do not treat the checkbox as a guarantee against new tags when importing links: use existing base names and test one row first.

Tag, company and object IDs may differ between stores; map them before importing. Check translations, links and storefront output after a sample row, then import the rest. Translations are not generated automatically: fill each required language separately.