TranslatedText cannot be converted to string when trying to create a product

[ElPootch]

When creating products via the Filament admin panel, I'm encountering the "Object of class
Lunar\FieldTypes\TranslatedText could not be converted to string" error.

This issue was originally reported for v1.0.0-beta21 and was marked as "resolved in v1.2.x" by
@alecritson on Dec 11, 2025. However, the issue persists in both v1.2.x and v1.3.0

Environment

• Lunar Versions Tested: 1.2.1 and 1.3.0 (both affected)
• Laravel Version: 11.48.0
• PHP Version: 8.4.1
• Filament Version: 3.x

Steps to Reproduce

1. Install Lunar 1.2.x or 1.3.x
2. Go to Admin Panel → Catalogue → Products → Create New Product
3. Fill in the product form and submit

Expected Behavior

Product should be created successfully.

Actual Behavior

Object of class Lunar\FieldTypes\TranslatedText could not be converted to string

Impact

Critical/Blocking - Cannot create or manage products, brands, or customer groups in the admin panel.

Please reopen and investigate. Happy to provide additional details or test any patches.

[alecritson]

Thanks for the issue, I just tried with a fresh install and was able to create a product jus fine. If you are able to provide any more information for your set up that might help. Was this a fresh install for you or an upgrade? If upgraded try clearing down Filament's cached components php artisan filament:clear

[ElPootch]

Hi @alecritson,

Thanks for looking into this!

I’ve tried running:

php artisan filament:clear-cached-components
php artisan optimize:clear

…but unfortunately, the issue persists.

Using Nightwatch, I captured the full stack trace:

Illuminate\Support\Str::slug()                
    → vendor/lunarphp/core/src/Generators/UrlGenerator.php:60
Lunar\Generators\UrlGenerator->createUrl()
    → UrlGenerator.php:46
Lunar\Generators\UrlGenerator->handle()
    → HasUrls.php:23

It appears that the error occurs when generating the URL slug for a new product. Specifically, Str::slug() receives a TranslatedText object instead of a plain string.

Setup:

• Type: Upgrade (1.0.0-beta.21 → 1.2.1 → 1.3.0)
• Lunar: 1.3.0
• Laravel: 11.48.0
• PHP: 8.3
• Database: PostgreSQL

Customizations that may be relevant:

• I extend Product and Brand models via ModelManifest::replace()
• Custom LunarPanel extensions for Order and Customer pages
• 2FA disabled via LunarPanel::disableTwoFactorAuth()

I’m wondering if my model extension via ModelManifest::replace() could be interfering, or if there’s something specific in my setup causing the name attribute to not resolve to a string before reaching the URL generator.

Happy to provide additional info or test patches if that would help!

Thanks in advance for any guidance.

[ElPootch]

Hi @alecritson,

Just to share an update from my side in case it helps.

Because this is affecting a production store, I tried isolating the issue by overriding the UrlGenerator. I’m fully aware this may be related to my own setup rather than a core issue, but the behavior was consistent enough that I wanted to document what worked for me

The core problem I’m seeing is that, in my case, the value passed to Str::slug() during URL generation can still be a TranslatedText object instead of a plain string. This seems to happen before the product name is fully resolved

Here’s the override that’s currently working reliably on my side :

<?php

namespace App\Generators;

use Illuminate\Database\Eloquent\Model;
use Lunar\Generators\UrlGenerator as LunarUrlGenerator;

class UrlGenerator extends LunarUrlGenerator
{
    public function handle(Model $model)
    {
        $this->model = $model;

        $name = $model->name ?: $model->attr('name');

        if ($name) {
            $nameString = $this->extractStringValue($name, $model);

            if ($nameString) {
                if ($model->urls()->count() === 0) {
                    $this->createUrl($nameString);
                }
            }
        }
    }

    protected function extractStringValue($value, Model $model): ?string
    {
        if (is_string($value)) {
            return $value;
        }

        if (method_exists($model, 'translateAttribute')) {
            return $model->translateAttribute('name');
        }

        return null;
    }
}

With this in place, product creation works consistently and only a single URL is generated per product

That said, my store runs a fairly complex configuration (multiple languages, multiple currencies, including Arabic), and I also extend core models, so it’s very possible this interaction is specific to my environment rather than a general issue in core

Possible core-level improvement

Beyond my workaround, I believe the underlying issue could potentially be addressed at the core level

One approach that might help avoid this class of issue altogether would be to allow TranslatedText to safely cast itself to a string and implement __toString() on TranslatedText, it would allow automatic string conversion anywhere a TranslatedText instance is implicitly used as a string (such as in Str::slug()), without requiring checks in each consumer

File: packages/core/src/FieldTypes/TranslatedText.php

/**
 * Returns string representation (first available translation).
 */
public function __toString(): string
{
    $collection = $this->getValue();

    if ($collection && $collection->isNotEmpty()) {
        $firstValue = $collection->first();

        if ($firstValue instanceof \Lunar\FieldTypes\Text) {
            return $firstValue->getValue() ?? '';
        }

        return (string) $firstValue;
    }

    return '';
}

This is just a suggestion based on what I’m seeing locally, and I may be missing some implications here, but I wanted to share it in case it aligns with how you’d prefer to handle this internally

Happy to test anything or provide more details if useful.