# etechflow/module-meta-templates

> Rule-based meta title/description/keywords templates with variables for Magento 2.

`composer require etechflow/module-meta-templates`

Canonical URL: https://packagento.com/etechflow/module-meta-templates

## At a glance

- **Vendor**: etechflow (https://packagento.com/etechflow.md)
- **Latest version**: 1.0.6 — released 2026-06-15
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/etechflow/module-meta-templates and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require etechflow/module-meta-templates:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

Rule-based meta title/description/keywords templates with variables for Magento 2.

## README

Rule-based **meta title / meta description / meta keywords** templates for Magento 2, with `{{variable}}` placeholders resolved per page at render time. Part of the **Etechflow SEO Suite**.

Define a rule once (e.g. `{{product.name}} | Buy at {{store.name}}`) and it applies across every matching product, category, or CMS page — no per-product editing.

### Features

- **Template rules** for `product`, `category`, and `cms_page` pages.
- **`{{object.attribute}}` variables** with optional fallback: `{{product.brand|Genuine Part}}`.
- **Any attribute** is available — `{{product.color}}`, `{{product.<any_code>}}`, dropdown labels resolved automatically.
- **Scoping**: per store view + optional "limit to category ID" for product rules.
- **Priority**: highest-priority matching rule wins.
- **Two modes**: *Fill empty* (never overwrites meta a product/category already has) or *Override* (always applies).
- **Title-safe**: applies the title via an `afterGet` plugin so it wins even when another extension also sets it.
- Admin grid + add/edit form under **Marketing → Meta Templates**. Master switch + mode under **Stores → Configuration → Etechflow → Meta Templates**.

### Variables

| Object | Variables |
|--------|-----------|
| Product | `{{product.name}}`, `{{product.sku}}`, `{{product.price}}`, `{{product.category}}` (deepest), `{{product.<attribute_code>}}` |
| Category | `{{category.name}}`, `{{category.description}}`, `{{category.<attribute_code>}}` |
| CMS | `{{cms.title}}` |
| Store | `{{store.name}}`, `{{store.url}}` |

Fallback syntax: `{{variable|fallback text}}` — used when the variable resolves to empty.

### Install

```bash
composer require etechflow/module-meta-templates
bin/magento module:enable Etechflow_MetaTemplates
bin/magento setup:upgrade
bin/magento setup:di:compile      # production mode
```

### Configure

1. **Stores → Configuration → Etechflow → Meta Templates** — set *Enable* = Yes and choose *Apply mode*.
2. **Marketing → Meta Templates** — *Add New Template*: name, applies-to, store view, optional category limit, priority, and the meta title / description / keywords templates.

### How it works

- A frontend plugin on `Magento\Framework\View\Result\Page::renderResult` resolves the matching rule for the current page and sets the description + keywords via `PageConfig`.
- A second plugin on `Magento\Framework\View\Page\Title::get` returns the templated title at read time, so it is authoritative.
- `Service/VariableProcessor` performs the `{{...}}` substitution; `Service/MetaResolver` picks the matching rule (type + store + category + priority) and honours the fill-empty / override mode.

### License

Proprietary — © eTechFlow.

## Changelog

All notable changes to this module are documented here.

### v1.0.0 — 2026-06-05

Initial public release.

Rule-based meta title/description/keywords templates with {{variable}} placeholders. Admin rule grid with conditions, per-store-view, dry-run preview.

## Recent Versions

| Version | Released |
|---|---|
| 1.0.6 | 2026-06-15 |
| 1.0.5 | 2026-06-15 |
| 1.0.4 | 2026-06-12 |
| 1.0.3 | 2026-06-12 |
| 1.0.2 | 2026-06-12 |
| 1.0.1 | 2026-06-11 |
| 1.0.0 | 2026-06-05 |

## Dependencies

### Require

| Package | Constraint |
|---|---|
| magento/framework | >=103.0 |
| magento/module-backend | >=102.0 |
| magento/module-catalog | >=104.0 |
| magento/module-cms | >=104.0 |
| magento/module-store | >=101.0 |
| php | ~8.1.0\|\|~8.2.0\|\|~8.3.0\|\|~8.4.0 |

## Quality

Latest release (1.0.6) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Pass | Pass | – | – |
| 2.4.8 | – | Pass | Pass | – |
| 2.4.9 | – | – | Pass | not tested |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 59 | 1 error, 58 warnings (ruleset: Magento2) — 4 auto-fixable with phpcbf |
| PHPMD | Warning | 15 | 15 rule violations (UnusedFormalParameter:4, NPathComplexity:4, CyclomaticComplexity:3, EmptyCatchBlock:3, ExcessiveClassComplexity:1) |
| Cpd | Pass | 0 |  |
| Composer validate | Info | 6 | valid; 6 advisory notes (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | 14 | 14 | – | – |
| 2.4.8 | – | 14 | 14 | – |
| 2.4.9 | – | – | 14 | N/A |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | Pass | 0 |  |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["etechflow/module-meta-templates"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

etechflow is a Magento 2 vendor on Packagento. See https://packagento.com/etechflow.md for their full catalogue.