AttributeSlugRepository cannot save non existing slug

[sparkable-agency]

In version v8.8.0 of the tweakwise/magento2-tweakwise module. The following happens.

When visiting a categorie with filters i get the following exception:

[2025-12-23T12:42:23.116453+00:00] main.CRITICAL: Magento\Framework\Exception\CouldNotSaveException: Die Seite konnte nicht gespeichert werden: Verletzung einer "Unique" Einschränkung gefunden in /data/web/apps/deploy.mysteel.hypernode.io/releases/12/vendor/tweakwise/magento2-tweakwise/Model/AttributeSlugRepository.php:107

It looks like the Save() function is trying to save an already existing slug to the tweakwise_attribute_slug table. When i dump: $attributeSlug->getSlug(); i get pulverbeschichtetem-stahl-1.

But when i than look in the table this slug does not exist:

The result of this is that on this category page no filters are loaded. To temporarily fix this is disabled the CouldNotSaveException thrown on line 107 of vendor/tweakwise/magento2-tweakwise/Model/AttributeSlugRepository.php

[ahuininga-orisha]

@gerrits-ecommerce Nevermind. I think may earlier comment may be wrong. There should not be two slug values for the same attribute. So this is not the problem. This is the original problem again. Only it should not be an problem anymore because there should not be two ways to write the attribute.

I think this may be triggered if the attribute is changed in tweakwise itself. I look into it.

[ahuininga-orisha]

@gerrits-ecommerce The value doesn't seem to be changed by tweakwise.

Can you check the value of $attributeSlug->getAttribute()? I want to know why the check on line 85 fails. vendor/tweakwise/magento2-tweakwise/Model/AttributeSlugRepository.php

if ($existingSlug->getAttribute() === $attributeSlug->getAttribute()) {

Based on my data, it should not fail. I think it may be an capital letter problem. The code should not reach the save function in the first place. I found the error in the cache lookup table that may indicate it may be an problem with capital letters. I'll make an fix for that. But to be sure, can you confirm the check on line 85 fails because of this?

[ahuininga-orisha]

@gerrits-ecommerce I think i found the cause. It is not the spelling. But you have two attributes both with the exact same option. material_type and import materiaal. And one of them seems to have an space after the value. The space in combination with the duplicate value causes the error. I'll see if i can find an solution for this.

In the mean time. If you remove the space after Pulverbeschichtetem Stahl for option_id 6446, it should solve the issue.

[sparkable-agency]

@ahuininga-orisha I fixed the option ID mentioned by you in the database and removed the space.

However if i enable the CouldNotSaveException thrown on line 107 of vendor/tweakwise/magento2-tweakwise/Model/AttributeSlugRepository.php the exception is still thrown, resulting in no filters on my category page.

[ahuininga-orisha]

@gerrits-ecommerce What is the attribute value when the exception is thrown? It may be that more attributes have the same problem.

[sparkable-agency]

@ahuininga-orisha I checked and the value of $attributeSlug->getSlug() is pulverbeschichtetem-stahl-1 when i re-enable the error . I also rechecked the option_id 6446. There is no space anymore in the database.

[LeonidasJP]

We have a similar issue on our end: Also the CouldNotSaveException at AttributeSlugRepository:107, but for a different reason: The store_id field does not exist.

Running setup:upgrade or setup:db-schema:upgrade has no effect, and the \Tweakwise\Magento2Tweakwise\Setup\Patch\Schema\ChangePrimaryKeyTweakwiseAttributeSlugTable patch does not show up in patch_list after running setup:upgrade...
Any idea how to fix this?

[ahuininga-orisha]

@LeonidasJP Not sure, you can try lowering the version nr or removing it from the setup_module table. And than running setup:upgrade again and see what happens

[LeonidasJP]

@ahuininga-orisha Apologies, after further research here we noticed a Schema Upgrade in another module did not go as planned, crashing setup:upgrade before the patch adding store_id could execute...

Note to self: Don't alter a field that had a constraint on it without properly removing that constraint first... And do that in separate releases...

[pmzandbergen]

Encountered the same issue on saving eav options. Created a local patch as (temporary) workaround.

[pmzandbergen]

Encountered the same issue on saving eav options. Created a local patch as (temporary) workaround.

Wasn't using the last version, will try that first.

[pmzandbergen]

Encountered the same issue on saving eav options. Created a local patch as (temporary) workaround.

Wasn't using the last version, will try that first.

Upgrading does not fix this issue. The issue itself has been resolved, however existing data is not patched since no such patch exists.

Suggestion: Add a patch trimming and lowercasing all existing slugs, removing any duplicates.

[pmzandbergen]

Possible solutions

1. Using a NO PAD collation
See: https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html_
This would require a patch and a check on information schema for the available collations and may cause issues when using non-default MariaDB / MySQL configurations.

2. Ignore padding spaces
Probably the easiest / best solution.

1. Create a patch updating the existing attributes removing the trailing spaces:

UPDATE `tweakwise_attribute_slug_clone3` SET `attribute` = TRIM(TRAILING ' ' FROM `attribute`);

2. Update AttributeSlugRepository:

    public function save(AttributeSlugInterface $attributeSlug): AttributeSlugInterface
    {
// ...
                if (strtolower(rtrim($existingSlug->getAttribute())) === strtolower(rtrim($attributeSlug->getAttribute()))) {
                    //same attribute, no need to change anything
                    return $attributeSlug;
                }
// ...
    }

3. Update AttributeSlugCollection to rtrim any attribute filters

---

Note: To resolve this issue for now I'll patch the repository and leave the collection as-is.

[pmzandbergen]

Also:

            throw new CouldNotSaveException(
                __(
                    'Could not save the page: %1',
                    $exception->getMessage()
                )
            );

Looks like a copy-pasta job from the Magento CMS module 😆