Allow Custom or Truncated Category Names for Product Set Sync

[CalzaFino]

Currently, when syncing Magento categories to Meta Commerce (Facebook/Instagram), the module uses the full category name or path (via $category->getName() or similar logic) to generate the Product Set name.

Meta enforces a strict 100-character limit on Product Set names. However, in Magento stores that use SEO-optimized long category names or full breadcrumb-style paths, this limit is easily exceeded, causing sync errors such as:
{
"error_user_title": "Product set name is too long",
"error_user_msg": "The name of the product set you're trying to access is longer than our allowed limit of 100. Please reduce the length to continue using it.",
"error_subcode": 1798252
}

Why This Matters
Magento merchants commonly use:

Descriptive or SEO-rich category names (often >100 characters)

Nested category structures with long paths

Multiple store views (with different naming needs)

Since the module builds Product Sets automatically from category names, these setups often break syncs and require manual edits or core hacks to avoid exceeding the character limit.

Suggested Solution
Introduce a configurable or extensible method for determining the Product Set name, such as:

✅ Use a custom category attribute (e.g., meta_set_name or fallback to name)

✅ Allow a plugin/hook to filter or truncate the Set name before it’s pushed

✅ Automatically truncate Set names >100 chars and log a warning

✅ Expose logic in a public or protected method, so merchants can override it

Benefits
Prevents sync failures without hacks

Maintains compatibility with Magento SEO practices

Enables localization and flexibility across store views

Reduces support overhead for long-name errors

Example Workaround (Current Hack)
We’re currently patching:

$name = $category->getData('custom_breadcrumb') ?: $category->getName();
if (mb_strlen($name) > 100) {
$name = mb_substr($name, 0, 97) . '…';
}
…but this logic belongs in the module itself, ideally as a configurable or overridable behavior.

Request
Please consider making the Product Set naming logic:

Pluggable (via DI or config)

Attribute-aware (custom name field)

Resilient (auto-truncate long names)

This will help more Magento merchants maintain compatibility with Meta’s catalog limits while preserving their SEO structures and store view strategies.

Thank you!

[CalzaFino]

I am testing the Example Workaround (Current Hack), but apparently it does not work as expected.

[CalzaFino]

✅ Update: Confirmed Root Cause & Working Fix — Suggest Configurable Option

Root Cause:
After deeper debugging, the 100-character error originates from the method:

Meta\Catalog\Model\Category\CategoryCollection::pushCategoryWithFBRequestJson()
Specifically from this line:

'name' => $this->categoryUtilities->getCategoryPathName($category, $storeId, $isVisibleOnMeta)

This method constructs a full category path (e.g., Men's Boots > Exotic Print > Bullhide), which often exceeds Meta’s 100-character limit for product set names — causing the error:

"Product set name is too long"

✅ Confirmed Fix (Safe and Working)
In our use case, replacing the full path with the last-level category name resolves the issue completely:

$name = $category->getName();
if (mb_strlen($name) > 100) {
$name = mb_substr($name, 0, 97) . '…';
}

This change applied to both:

pushCategoryWithFBRequestJson() (for creating sets)

updateCategoryWithFBRequestJson() (already using getName())

After applying this fix, category syncs are successful and no longer fail due to the name length restriction.

🔄 Why This Should Be Configurable
While this solution works well for us, other merchants may rely on the full path to distinguish categories with the same name in different branches (e.g., Men > Shirts vs. Women > Shirts).

Therefore, we recommend adding a new configuration option in the module admin settings:

Use full category path for product set name (recommended for complex category structures)
- If disabled, uses only the last-level category name
- Automatically truncates names longer than 100 characters

With this, merchants can choose the approach that best fits their catalog structure and avoid sync errors in both scenarios.

🧠 Optional Enhancement
Additionally, supporting a fallback like a custom attribute (meta_set_name) would give merchants full control over naming:

$custom = $category->getData('meta_set_name') ?: $category->getName();

✅ Summary
The hardcoded use of full paths is breaking syncs for many Magento stores

Replacing it with getName() solves the issue in most cases

This should be optional via configuration to preserve compatibility and flexibility

Thank you for your consideration and for making this extension better for the Magento community!

[pradeepkanaka]

@CalzaFino Thanks for reporting, we will have a look and revert back.