I think it would be a good idea to add a publishable configuration file to this package, which allows a user to specify:

• Words specific to their application they want to treat as "unclean"
• Words specific to their application they want to allow

The configuration files that are currently used are very general and will work for most cases, but I can imagine some applications would want to block/allow certain words, where it makes sense to do it in userland rather than at the package level.

Octane Version

2.11.0

Laravel Version

12.20.0

PHP Version

8.3.23

What server type are you using?

FrankenPHP

Server Version

1.8.0

Database Driver & Version

No response

Description

I have an octane app running inside a docker container and use a bind mount for the application code. When editing files, fs events are not sent across the bind mount to the container, so the watcher does not detect them. I have the same issue reported in #487. There is also an open issue on the frankenphp repository https://github.com/php/frankenphp/issues/1616.

A potential solution would be to add an option to octane:frankenphp, like --chokidar to use chokidar instead of frankenphp's watcher.

Steps To Reproduce

Same as #487, but using frankenphp.

using prompt engineering techniques provide enhancement to the Gemini service class in the Gemini prompt class, creating functions commonly used in Laravel applications.

• standard tags
• input fields
• components
• patterns

Add code snippets for each block

Let's try out Filament and move our own admin panels to it. This should provide us with a much more powerful admin backend.

https://filamentphp.com

Sulu CMS separates its assets into assets/admin and assets/website, this means when installing Encore within a Sulu CMS install you will have to change a bunch of paths: https://docs.sulu.io/en/latest/cookbook/webpack-encore.html

This isn't my main issue, I think this is acceptable for an initial setup. But I do think we can improve what happens when you composer require a symfony bundle that provides stimulus controllers.

In the Sulu + Encore setup, the controllers.json file lives in assets/website/controllers.json. But since this path is hardcoded here:

https://github.com/symfony/flex/blob/441f671b86a1b651e969dbc380bfee05e004780f/src/PackageJsonSynchronizer.php#L166-L170

The controllers.json is not updated automatically and there's no output telling you to manually do this either. So you're left a little lost in what is still missing. Also, figuring out what to manually add in controllers.json is quite tricky since most existing UX bundles don't document this manual setup.

Before I start hacking away at a PR, any suggestions how we can solve this properly? Or do we accept that this is not configurable and those who use custom paths just have to deal with it?

Thank you in advance.

Found the \Illuminate\Database\Eloquent\Concerns\HasAttributes::originalIsEquivalent() method during code diving and it should be usable for our trait! 🎉 This PR would be mainly reasearch when that method was added, if it's compatible with our version support rules and switching our own change detection logic with the core one.

We are logging activity of several models, some using SoftDeletes trait and others not.

When we set config option 'subject_returns_soft_deleted_models' => true then calling subject() on any model not using SoftDeletes trait throws an exception: Call to undefined method Illuminate\Database\Eloquent\Builder::withTrashed().

Can the subject() method below be made to check first whether the Model uses the SoftDeletes trait? Or perhaps check whether withTrashed() is a defined method on the Model? I tried a few things but couldn't figure out how to get the class of the Model..

https://github.com/spatie/laravel-activitylog/blob/68eb6e65382f94fe86ce5ff6572159f80d024ba9/src/Models/Activity.php#L28-L35

I would be good to support normalizer_get_raw_decomposition function that appeared in PHP 7.3. I've tried to implement it but seems that existing decomposition data is already optimized to get the final decomposition. Example test case is available here. Pinging @nicolas-grekas as he is the author of Normalizer polyfill.

I tried the example config from the docs to a Laravel/Inertia/Vue app, and it don't work.

If use the code (HandleInertiaRequests.php): 'messages' => flash()->render([], 'array'),

Error: Flasher\Prime\Flasher::render(): Argument #1 ($presenter) must be of type string, array given, called in D:\Laragon6\www\mobi-care\app\Http\Middleware\HandleInertiaRequests.php on line 36

And changing it to: 'messages' => flash()->render('array'), it loads the page, but, I only see the notifications if i press F5, with its not the desired state.

When using the addToMediaFromURL method, I'm receiving a Could Not Load Image error on the server, but not locally (I'm using Laravel Vapor) and not with other image formats.

The code below is where the error is occuring and that code is receiving an absolute file path to the image in s3, which is available.

public function addToMediaLibrary($file_path) { $media = $this->addMediaFromUrl($file_path) ->toMediaCollection("", 's3'); return $media; }

As an example the file path when logged out is https://s3.sitesforsaas.com/tenants/d221c93a-3757-466c-bf83-b74a9ee64c04/sites/9cfc24c7-cb2a-4c5a-8c0f-73ecdc79c166/2024/09/4e9854b0-4f2d-4931-a726-01f557bd7fc6.webp, but the error is looking for the image in local 'tmp' storage for some reason.

Could not load image at path /tmp/storage/tenantd221c93a-3757-466c-bf83-b74a9ee64c04/media-library/temp/j7pNMerUdReNx9MfAG5rKjcmGHWu4i99/LM2UYMTcYU0BO8sLsTfeOBpS9eXximejlarge.webp`",

Figure our a way to show a grayed out Laravel logo as a default avatar instead of the current default GitHub one.

Provide updates to new functionalities in the v2 of the package.

Hello,

I noticed that there is an incompatibility with the mbstring polyfill and PHP 8.1 / Alpine Linux, which breaks a lot of my projects as soon as the php81-mbstring is not installed, but php81-iconv is installed:

Example:

Warning: iconv(): Wrong encoding, conversion from "ASCII" to "UTF-8//IGNORE" is not allowed in phar:///var/www/localhost/htdocs/phpstan.phar/vendor/symfony/polyfill-mbstring/Mbstring.php on line 736

It looks like //IGNORE is not accepted since echo iconv('UTF-8', 'UTF-8', 'test'); works, while echo iconv('UTF-8', 'UTF-8//IGNORE', 'test'); doesn't

Laravel Version

12.19.3

PHP Version

8.4.10

Database Driver & Version

No response

Description

Hello,

The command artisan schedule:work run artisan schedule:run every minutes, but this works only if we are in the same directory than artisan

Steps To Reproduce

• Create laravel in /home/laravel.
• Go in /home/laravel run php84 artisan schedule:work it WORKS
• Go in / run php84 /home/laravel/artisan schedule:work it DOESN'T WORKS

It raise

...
Could not open input file: artisan
Could not open input file: artisan
Could not open input file: artisan
Could not open input file: artisan
... 

Example

[root@server /]$ /bin/php84 /home/laravel/artisan schedule:work
Could not open input file: artisan
^C
[root@server ~]$ cd /home/laravel
[root@server ~]$ /bin/php84 /home/laravel/artisan schedule:work
  2025-07-23 20:30:00 Running [TASK #1]  395.67ms DONE

Octane Version

2.8.1

Laravel Version

10.48.28

PHP Version

8.3.16

What server type are you using?

Swoole

Server Version

6.0.1

Database Driver & Version

No response

Description

I'm using Envoyer to deploy a Laravel Octane application, taking advantage of its zero-downtime deployment features.

However, Octane currently does not support zero-downtime deployment because it does not follow symlink directories. It always remains in the actual directory (instead of the symlinked one) where the Octane server was initially started. When the outdated release directory is deleted, Octane continues running in that location, causing errors on every request and resulting in 500 response codes on the live application.

Error thrown:

Warning: require(/var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/bootstrap.php): Failed to open stream: No such file or directory in /var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/swoole-server on line 18
Fatal error: Uncaught Error: Failed opening required '/var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/bootstrap.php' (include_path='.:/usr/bin/[email protected]/8.3.16/share/[email protected]/pear') in /var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/swoole-server:18
Stack trace:
#0 /var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/swoole-server(95): {closure}(Array)
#1 [internal function]: {closure}(Object(Swoole\Http\Server), 0)
#2 /var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/swoole-server(170): Swoole\Server->start()
#3 {main}
  thrown in /var/www/domain.com/releases/202502010200023/vendor/laravel/octane/bin/swoole-server on line 18
#1 [internal function]: {closure}(Object(Swoole\Http\Server), 1)
#1 [internal function]: {closure}(Object(Swoole\Http\Server), 3)
#1 [internal function]: {closure}(Object(Swoole\Http\Server), 2)
#1 [internal function]: {closure}(Object(Swoole\Http\Server), 4)
#1 [internal function]: {closure}(Object(Swoole\Http\Server), 5)

Steps To Reproduce

Use any 0-downtime deployment or test it manually using the following instructions:

1. Use the Swoole driver as an example.
2. cd one directory up from the project's base path.
3. Create a current symlink directory for your project using the command: ln -nsf ./octane-project-test ./current
4. Start the Octane server: php ./current/artisan octane:start
5. Copy your project to another directory: cp -R ./octane-project-test ./octane-project-test-new
6. Activate the new release: ln -nsf ./octane-project-test-new ./current
7. Reload the Octane server: php ./current/artisan octane:reload
8. Remove the original project directory: rm -rf ./octane-project-test

Cachet would benefit from upgrading to Tailwind v4. This could lead to a really powerful theming system beyond the accents feature we currently have.

https://tailwindcss.com/docs/upgrade-guide

Package

filament/filament

Package Version

4-beta6

Laravel Version

12

Livewire Version

3

PHP Version

8.4

Problem description

Not sure if I'm doing something wrong, but I can't get charts in nested non-active tabs to render properly on page load, or update properly. The video shows the problem using the reproduction repo.

I'm using this to render the chart in 3 places:

Livewire::make(StatChartWidget::class, fn ($record) => [
        'record' => $record,
    ])
    ->key(Str::random(10))

In the video, the following happens:

1. Page load

• Chart in the body loads ✅
• Chart in the visible tab loads ✅
• Chart in the non-visible nested "Data" tab is empty ❌

2. "Refresh data" to update the model's data attribute while the 'Data' tab is not active

• Chart in the body refreshes ✅
• Chart in the visible tab refreshes ✅
• Chart in the non-visible nested "Data" tab is not refreshed ❌

2. "Refresh data" to update the model's data attribute while the 'Data' tab is active

• Chart in the body refreshes ✅
• Chart in the visible tab refreshes ✅
• Chart in the non-visible nested "Data" tab refreshes ✅

I'm using #[Reactive] but I also tried refreshing via an event, and tried ->lazy(). Neither helped.

https://github.com/user-attachments/assets/6cb1cb43-8c9b-4f3e-ab62-face3931473a

Expected behavior

Charts / Livewire components in a page should render and update correctly regardless of what tab they're in.

Steps to reproduce

1. Clone repo
2. Run migrate:fresh --seed to seed statistics table
3. Go to Statistics resource
4. See video and steps outlined in description to reproduce

Reproduction repository (issue will be closed if this is not valid)

https://github.com/binaryfire/filament-bug-reproduction

Relevant log output

While working on the new version of https://github.com/symfony/stimulus-bridge, I noticed some dead code from https://github.com/symfony/webpack-encore/pull/1062:

Not PHPUnit 11 because we still need to support for PHP 8.1

e.g. at the moment we have stuff like:

1. Symfony\Flex\Tests\Configurator\CopyFromPackageConfiguratorTest::testConfigureAndOverwriteFiles The at() matcher has been deprecated. It will be removed in PHPUnit 10. Please refactor your test to not rely on the order in which methods are invoked.

Help wanted 🙏

Calling for help from Docker experts. We need to create the best possible docker-compose.yml file for this project. The application requirements are well defined (we use env vars, Webpack Encore, PHP 7.1, Symfony 4.1, SQLite database, etc.) so it should be possible to create that file.

Package

filament/filament

Package Version

v3.3

Laravel Version

v12.13

Livewire Version

v3.6

PHP Version

PHP 8.4.5

Problem description

My model need translations so I use a secondary table to store it. In this example, I have Sector (table: hike_sectors) and SectorTranslation (table: hike_sector_translations). I want in my table to search using default language name. I have created a service to custom automatically the searchable query. But there is an issue by using LEFT JOIN.

Here is my code :

class TranslatableTableService
{
    public function sortable(Builder $query, string $direction, string $attribute = 'id', $languageId = null): Builder
    {
        $languageId ??= LanguageHelper::getDefaultId();

        $model = $query->getModel();
        $translationModel = new ($model->getTranslationModelClass());

        $mainTable = $model->getTable();
        $translationTable = $translationModel->getTable();
        $alias = 't_' . $translationTable;

        $foreignKey = $model->translations()->getForeignKeyName();

        return $query
            ->leftJoin("{$translationTable} as {$alias}", function ($join) use ($alias, $foreignKey, $mainTable, $languageId) {
                $join->on("{$alias}.{$foreignKey}", '=', "{$mainTable}.id")
                    ->where("{$alias}.language_id", '=', $languageId);
            })
            ->orderBy("{$alias}.{$attribute}", $direction)
            ->select("{$mainTable}.*");
    }

    public function searchable(Builder $query, string $search, string $attribute, $languageId = null): Builder
    {
        $languageId ??= LanguageHelper::getDefaultId();

        $model = $query->getModel();
        $translationModel = new ($model->getTranslationModelClass());

        $mainTable = $model->getTable();
        $translationTable = $translationModel->getTable();
        $alias = 't_' . $translationTable;

        $foreignKey = $model->translations()->getForeignKeyName();

        return $query
            ->leftJoin("{$translationTable} as {$alias}", function ($join) use ($alias, $foreignKey, $mainTable, $languageId) {
                $join->on("{$alias}.{$foreignKey}", '=', "{$mainTable}.id")
                    ->where("{$alias}.language_id", '=', $languageId);
            })
            ->where("{$alias}.{$attribute}", 'like', "%$search%")
            ->select("{$mainTable}.*");
    }
}

public static function table(Table $table): Table
{
    return $table
        ->columns([
            Tables\Columns\TextColumn::make('name')
                ->label('Nom')
                ->state(function (Sector $record) {
                    return $record->translated('name');
                })
                ->searchable(query: function (Builder $query, string $search, TranslatableTableService $service): Builder {
                    return $service->searchable($query, $search, 'name');
                }),
            Tables\Columns\TextColumn::make('slug')
                ->label('Url')
                ->state(function (Sector $record) {
                    return $record->translated('slug');
                }),
        ])
        ->defaultSort('position')
        ->reorderable('position')
        ->filters([
            //
        ])
        ->actions([
            TranslatableEditAction::make(),
            Tables\Actions\DeleteAction::make(),
        ])
        ->bulkActions([
            //
        ]);
}

Here is the issue (don't pay any attention to the letter t at the beginning of the table name, it's an error handling of my service) : SQLSTATE[42S22]: Column not found: 1054 Unknown column 't_hike_sector_translations.name' in 'where clause' (Connection: mysql, SQL: select count(*) as aggregate from hike_sectors where ((t_hike_sector_translations.name like %tour%)))

This error come from filament/tables/src/Concerns/CanPaginateRecords.php:35 file : $total = $query->toBase()->getCountForPagination();

So I try to add a sortable to my column :

->sortable(query: function (Builder $query, string $direction, TranslatableTableService $service): Builder {
    return $service->sortable($query, $direction, 'name');
})

Same issue.

BUT using ->defaultSort('name') instead of ->defaultSort('position') that work perfectly !! I don't know why except that the LEFT JOIN is used when I make all this thing otherwise not. But to use a custom search using left join I have to use ->sortable to my column and ->defaultSort at my specific column to my table to make work the search.

Expected behavior

I just want to use ->searchable using custom query with LEFT JOIN independently at other query

Steps to reproduce

Try to use ->searchable in column of table using custom query with LEFT JOIN

Reproduction repository (issue will be closed if this is not valid)

https://github.com/Alpaweb/FilamentSearchableColumn

Relevant log output

If a pack lists things in its "replace" section, unpacking this pack should copy these rules into the "replace" section of the root composer.json.

I think that implementing this requires patching the Unpacker class only.

Anyone up to give it a try?

Immediately after installing php-flasher/flasher-laravel, the application breaks with the following error:

foreach() argument must be of type array|object, bool given Simply installing the package causes this fatal error.

Steps to Reproduce:

Create a fresh Laravel app.

Run:

composer require php-flasher/flasher-laravel

Load any page in the app — no usage of flasher() or flasher_render() yet.

Laravel crashes with a foreach() error.

Describe the bug I have a table which has an order column. When I reorder the elements I update each model with the new order. Because the table has some large JSON columns I select only id and order columns for efficiency. I set the new order and save the model.

foreach (Faq::query()->get(['id', 'order']) as $faq) {
    $faq->order = $newOrder[$faq->id];
    $faq->save();
}

The diffs created in the activity_log table look like this:

{
   "old": {
      "order": 1,
      "answer": null,
      "question": null
   },
   "attributes": {
      "order": 2,
      "answer": "long JSON content",
      "question": "long JSON content"
   }
}

From what I see laravel-activitylog fetches the model with all columns from the database before creating a log entry which kind of defeats the purpose of my "select list optimization" and produces an incorrect diff.

Generally I want these large JSON columns to be logged in case a user changes them but in this case I only change the order column so I would like to see only the order column in the diff.

I have tried running these updates straight off the Eloquent builder:

Faq::query()->where('id', $id)->update(['order' => $newOrder[$id]]);

but in this case nothing is logged.

I have the following activitylog configuration for my models:

public function getActivitylogOptions(): LogOptions
{
    return LogOptions::defaults()
                     ->logAll()
                     ->logOnlyDirty()
                     ->logExcept([
                         'id',
                         'created_at',
                         'updated_at',
                     ]);
}

To Reproduce Select a subset of columns from the database, change these columns, save the model and see that other (not initially selected) columns are present in the diff.

Expected behavior Only columns that've actually been changed should be present in the diff.

Versions

• PHP: 8.1
• Database: MySQL 8
• Laravel: 9.31.0
• Package: 4.6.0

Bug description

Chrome, Firefox, and Safari now support setting the width and height attributes on <source> elements within <picture> elements. You can read more about this in the web.dev article on optimizing CLS. This enhancement allows browsers to better handle layout shifts and varying aspect ratios for responsive images.

How to reproduce

Current Behavior:

Currently, Statamic Responsive Images does not take advantage of this browser capability. As a result, when multiple sources are provided, the appropriate width and height attributes are not applied to <source> elements, which may lead to layout shifts due to varying aspect ratios.

Proposed Enhancement:

Set appropriate width and height attributes on <source> elements based on their aspect ratios.

Benefits:

• Improved Visual Stability: Reduce Cumulative Layout Shift (CLS) by providing browsers with the correct dimensions upfront.
• Better Performance: Modern browsers can allocate the correct space for images during page load.
• Enhanced Responsiveness: Accurately reflect different image aspect ratios for a more consistent user experience.

Environment

Environment
Application Name: local
Laravel Version: 11.41.3
PHP Version: 8.3.16
Composer Version: 2.8.5
Environment: development
Debug Mode: ENABLED
URL: local.test
Maintenance Mode: OFF
Timezone: Europe/Paris
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: NOT CACHED

Drivers
Broadcasting: null
Cache: file
Database: sqlite
Logs: stack / single
Mail: smtp
Queue: redis
Session: file

Statamic
Addons: 3
Sites: 1
Stache Watcher: Disabled (auto)
Static Caching: Disabled
Version: 5.46.1 PRO

Statamic Addons
rias/statamic-redirect: 3.9.3
spatie/statamic-responsive-images: 5.2.1
statamic/seo-pro: 6.5.0

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

regex (default)

Additional details

Leveraging native width and height support on <source> elements can lead to significant improvements in layout stability and overall performance on modern browsers. This enhancement would allow the package to better handle responsive images by using up-to-date browser capabilities.

Thanks for considering this enhancement!

When calling mb_convert_encoding() with $fromEncoding === 'HTML-ENTITIES', the polyfill does not return functionally equivalent strings to the native function. This is because mb_convert_encoding() uses html_entity_decode() when $fromEncoding === 'HTML-ENTITIES' and that function does not return characters for many numeric entities 0-31 and 127-159. For example:

<?php

require "vendor/symfony/polyfill-mbstring/Mbstring.php";

use Symfony\Polyfill\Mbstring as p;

for($i = 0; $i < 1024; $i++) {
	$string = "&#" . $i . ";";
	$mbstring = mb_convert_encoding($string, 'UTF-8', 'HTML-ENTITIES');
	$polyfill = p\Mbstring::mb_convert_encoding($string, 'UTF-8', 'HTML-ENTITIES');
	if($mbstring != $polyfill) {
		echo "Mismatch: $string - mbstring: $mbstring; polyfill: $polyfill\n";
	}
}

outputs:

Mismatch: � - mbstring: ; polyfill: �
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring:; polyfill: 
Mismatch:  - mbstring:
                            ; polyfill: 
Mismatch:  - mbstring:
                            ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring:  polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch: ' - mbstring: '; polyfill: '
Mismatch:  - mbstring: ; polyfill: 
Mismatch: € - mbstring: €; polyfill: €
Mismatch:  - mbstring: ; polyfill: 
Mismatch: ‚ - mbstring: ‚; polyfill: ‚
Mismatch: ƒ - mbstring: ƒ; polyfill: ƒ
Mismatch: „ - mbstring: „; polyfill: „
Mismatch: … - mbstring: …; polyfill: …
Mismatch: † - mbstring: †; polyfill: †
Mismatch: ‡ - mbstring: ‡; polyfill: ‡
Mismatch: ˆ - mbstring: ˆ; polyfill: ˆ
Mismatch: ‰ - mbstring: ‰; polyfill: ‰
Mismatch: Š - mbstring: Š; polyfill: Š
Mismatch: ‹ - mbstring: ‹; polyfill: ‹
Mismatch: Œ - mbstring: Œ; polyfill: Œ
Mismatch:  - mbstring: ; polyfill: 
Mismatch: Ž - mbstring: Ž; polyfill: Ž
Mismatch:  - mbstring: ; polyfill: 
Mismatch:  - mbstring: ; polyfill: 
Mismatch: ‘ - mbstring: ‘; polyfill: ‘
Mismatch: ’ - mbstring: ’; polyfill: ’
Mismatch: “ - mbstring: “; polyfill: “
Mismatch: ” - mbstring: ”; polyfill: ”
Mismatch: • - mbstring: •; polyfill: •
Mismatch: – - mbstring: –; polyfill: –
Mismatch: — - mbstring: —; polyfill: —
Mismatch: ˜ - mbstring: ˜; polyfill: ˜
Mismatch: ™ - mbstring: ™; polyfill: ™
Mismatch: š - mbstring: š; polyfill: š
Mismatch: › - mbstring: ›; polyfill: ›
Mismatch: œ - mbstring: œ; polyfill: œ
Mismatch:  - mbstring: ; polyfill: 
Mismatch: ž - mbstring: ž; polyfill: ž
Mismatch: Ÿ - mbstring: Ÿ; polyfill: Ÿ

While many of these are control characters (and the native function does return them), the single quote (dec 39) is particularly problematic.

Package

filament/tables

Package Version

v4.0.0-beta1

Laravel Version

v12.19.3

Livewire Version

v3.6.3

PHP Version

8.4.5

Problem description

I’m using the spatie/laravel-permission package to manage user roles and permissions.

In my UsersRelationManager, which displays a table of users belonging to a Tenant (one-to-many), I have a ToggleColumn called is_admin. Its purpose is to assign or remove the "admin" role when toggled.

I want to make this column sortable to list admins first. However, when I use orderByRaw() in the sortable callback, sorting doesn’t work as expected (see attached image).

Here is my table configuration:

public function table(Table $table): Table 
{
    return $table
        ->columns([
            TextColumn::make('name'),
            TextColumn::make('email'),
            ToggleColumn::make('is_admin')
                ->updateStateUsing(function (User $record, bool $state): void {
                    if ($state) {
                        $record->assignRole('admin');
                    } else {
                        $record->removeRole('admin');
                    }
                })
                ->sortable(true, function (Builder $query, string $direction): void {
                    $query->orderByRaw(<<<SQL
                        exists(
                            select 1
                            from model_has_roles
                            join roles on roles.id = model_has_roles.role_id
                            where model_has_roles.model_id = users.id
                            and model_has_roles.model_type = ?
                            and roles.name = 'admin'
                        ) {$direction}
                    SQL, [User::class])->orderBy('name', 'asc');
                }),
        ])
        ->recordUrl(null)
        ->recordAction(null)
        ->recordActions([
            DeleteAction::make(),
        ]);
}

Problem:

Sorting does not prioritize users with the "admin" role as expected. Instead, the order remains unchanged when clicking the column header.

Expected behavior

The expected behavior is that the ToggleColumn sorting works correctly. When sorting in ascending order, all rows with the toggle enabled (checked) should appear first, followed by the unchecked rows.

Please see the attached image for reference.

Steps to reproduce

1. Create a Tenant resource.
2. Create a UsersRelationManager for the User model.
3. Configure the table as shown in the provided code snippet.

Note: When refreshing the page, the sorting initially renders correctly.

Reproduction repository (issue will be closed if this is not valid)

https://github.com/filamentphp/demo

Relevant log output

Bug description

Currently, the plugin calculates width/height incorrectly when swapping aspect ratios, leading to incorrect HTML output. When changing the aspect ratio of an image, the longest side should remain fixed, and the other side should be calculated accordingly.

How to reproduce

For an image of 3000x1688px as a source:

{{ responsive:image ratio="16/9" md:ratio="9/16" }}

it returns:

<picture>
    <source [...] >
    <source [...] >
    <source [...] >
    <img src="/img/asset/hash/image.jpg?w=3000&amp;h=1688&amp;s=9358bb54be5d388a9a2529a4196dcfc6" alt="" width="3000" height="1688">
</picture>

Now for the same image as source but with:

{{ responsive:image ratio="9/16" md:ratio="16/9" }}

it returns:

<picture>
    <source [...] >
    <source [...] >
    <source [...] >
    <img src="/img/asset/hash/image.jpg?w=3000&amp;h=5333&amp;s=6c5c0bb8447dbd7ff61a692f98b5f46d" alt="" width="3000" height="5333">
</picture>

The calculated aspect ratio is correct, but the dimensions are not. The generated values exceed the original image size.

In this last example, the correct height should be 3000px, and the width should be 1688px to ensure the image stays within its original dimensions.

Environment

Environment
Application Name: local
Laravel Version: 11.41.3
PHP Version: 8.3.14
Composer Version: 2.8.5
Environment: development
Debug Mode: ENABLED
URL: local.test
Maintenance Mode: OFF
Timezone: Europe/Paris
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: null
Cache: file
Database: sqlite
Logs: stack / single
Mail: smtp
Queue: redis
Session: file

Statamic
Addons: 3
Sites: 1
Stache Watcher: Disabled (auto)
Static Caching: Disabled
Version: 5.46.0 PRO

Statamic Addons
rias/statamic-redirect: 3.9.3
spatie/statamic-responsive-images: 5.2.1
statamic/seo-pro: 6.5.0

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

regex (default)

Laravel Version

12.x

PHP Version

8.3.x

Database Driver & Version

PostgreSQL 17.x

Description

When creating a table with two foreign keys using ->constrained(), if a composite unique index is also defined on the first foreign key, the B-tree index for the second foreign key is not created.

This appears to be a regression or a new edge case related to the bug that was supposedly fixed in Pull Request #49392. The schema builder's optimization logic seems to be too aggressive, incorrectly omitting necessary indexes.

Steps To Reproduce

1. Create a fresh Laravel 12 project.
2. Create the following migration:

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        // Parent table 1
        Schema::create('authors', function (Blueprint $table) {
            $table->id();
            $table->string('name');
            $table->timestamps();
        });

        // Parent table 2
        Schema::create('categories', function (Blueprint $table) {
            $table->id();
            $table->string('name')->unique();
            $table->timestamps();
        });

        // The problematic table
        Schema::create('books', function (Blueprint $table) {
            $table->id();

            // FK #1
            $table->foreignId('author_id')->constrained();

            // FK #2
            $table->foreignId('category_id')->constrained();

            $table->string('title');
            $table->timestamps();

            // Composite unique index
            $table->unique(['author_id', 'title']);
        });
    }
};

3. Run php artisan migrate.

4. Connect to the PostgreSQL database and run the following query to inspect the created indexes:

SELECT indexname, indexdef
FROM pg_indexes
WHERE tablename = 'books';

Expected Behavior

The query should return three indexes:

1. books_pkey (Primary Key)
2. books_author_id_title_unique (Composite Unique)
3. books_category_id_index (The index for the category_id foreign key)

Actual Behavior

The query only returns two indexes. The books_category_id_index is missing:

| indexname                  | indexdef                                                              |
| -------------------------- | --------------------------------------------------------------------- |
| `books_pkey`               | CREATE UNIQUE INDEX books_pkey ON public.books USING btree (id)       |
| `books_author_id_title_unique` | CREATE UNIQUE INDEX books_author_id_title_unique ON public.books USING btree (author_id, title) |

This confirms the index on the second foreign key was not created. Adding $table->index('category_id'); explicitly works as a temporary solution.

This issue was also independently reported in Discussion #54343.

Hi! If I use this package with my project I has a problem. My package.json has a "git dependency" like this:

{
  "peerDependencies": {
    "package": "git+ssh://[email protected]/team/project.git"
  }
}

And npm-install-peers breaks.

The docs aren't finished. This issue exists to track the missing pieces:

• App icons
• Context menus
• Dock
• Printing
• ProgressBar
• Queue
• Screens
• Settings
• Shell
• System
• Touch ID
• Testing
• Obfuscating and securing PHP code
• Build signing (#361)
  • macOS
  • Windows
• How to customise Electron / PR to NativePHP
• Security disclosures process
• Highlight current section
• Show ToC persistently on the right-hand side
• Sponsorship page
• Contributors page
• Show sponsors in sidebar
• Add next/previous section buttons to the bottom of pages
• Add Edit on GitHub link to pages

Package

filament/filament

Package Version

3.3.28

Laravel Version

12.19.3

Livewire Version

3.6.3

PHP Version

8.4.8

Problem description

For a Filament Panel Page that includes a child Livewire component, a Filament Notification fired by that child component is rendered twice by Filament's notifications.blade.php if a Livewire event is fired at the same time. If an event is not fired, the notification renders only once.

Expected behavior

The Filament Notification blade should be rendered only once for any call to the Notification object.

Steps to reproduce

Given the provided repo.

composer install
php artisan migrate
php artisan make:filament-user

In vendor/filament/notifications/resources/views/notifications.blade.php log out the $notifications variable:

@php
    use Filament\Support\Enums\Alignment;
    use Filament\Support\Enums\VerticalAlignment;

    \Log::info($notifications);
@endphp

Navigate to /admin/foobar .

Click "With Event" button. Refresh.

Click "Without Event" button. Refresh.

Checking laravel.log, the "With Event" log is proceeded by two renders of a notification with the same ID. The "Notification without Event" is proceeded by just one.

(See log output below)

Reproduction repository (issue will be closed if this is not valid)

https://github.com/jasonlund/filament-notification

Relevant log output

[2025-06-23 16:36:13] local.INFO: []  
[2025-06-23 16:36:42] local.INFO: []  
[2025-06-23 16:36:43] local.INFO: Notification with Event  
[2025-06-23 16:36:43] local.INFO: {"9f3994ea-cbdd-429b-9202-1c2aa6582117":{"id":"9f3994ea-cbdd-429b-9202-1c2aa6582117","actions":[],"body":null,"color":null,"duration":6000,"icon":"heroicon-o-check-circle","iconColor":"success","status":"success","title":"With Event","view":"filament-notifications::notification","viewData":[]}}  
[2025-06-23 16:36:43] local.INFO: {"9f3994ea-cbdd-429b-9202-1c2aa6582117":{"id":"9f3994ea-cbdd-429b-9202-1c2aa6582117","actions":[],"body":null,"color":null,"duration":6000,"icon":"heroicon-o-check-circle","iconColor":"success","status":"success","title":"With Event","view":"filament-notifications::notification","viewData":[]}}  
[2025-06-23 16:36:44] local.INFO: []  
[2025-06-23 16:36:46] local.INFO: Notification without Event  
[2025-06-23 16:36:46] local.INFO: {"9f3994ee-65f6-434d-95b4-e1c266b15e85":{"id":"9f3994ee-65f6-434d-95b4-e1c266b15e85","actions":[],"body":null,"color":null,"duration":6000,"icon":"heroicon-o-check-circle","iconColor":"success","status":"success","title":"Without Event","view":"filament-notifications::notification","viewData":[]}}  
[2025-06-23 16:36:52] local.INFO: []

Discussed in https://github.com/spatie/schema-org/discussions/202

Originally posted by indyjonesnl January 10, 2024

$lodgingBusiness = Schema::lodgingBusiness()
  ->openingHours(
    Schema::openingHoursSpecification()
      ->dayOfWeek([Schema::dayOfWeek()::Monday])
      ->opens(new DateTime('09:00:00'))
      ->closes(new DateTime('17:00:00'))
  )
  ->checkinTime(new DateTime('14:00:00'))
  ->checkoutTime(new DateTime('11:00:00'))

This results in the current date + time being included in the output "opens":"2024-01-10T09:00:00+00:00","closes":"2024-01-10T17:00:00+00:00" and ..."checkinTime":"2024-01-10T14:00:00+00:00","checkoutTime":"2024-01-10T11:00:00+00:00"...

While the Schema should contain only the time, formatted as 14:30:00+08:00.

Can someone point me in the right direction?

Laravel Version

12.21.0

PHP Version

8.4.11

Database Driver & Version

No response

Description

There seems to be an issue with grouping tasks in the scheduler in a specific way - I believe it's the same issue as specified in pull 53427 in the last comment made by @decadence.

I believe the issues arises when grouping tasks (with subgroups) in a specific way such as e.g.:

Schedule::days([1, 2, 3, 4, 5, 6])->group(function () {
    Schedule::between('07:00', '21:00')->group(function () {
        Schedule::call(Task1::class)->everyMinute();
        Schedule::call(Task2::class)->everyMinute();
    });

    Schedule::call(Task3::class)->at('23:45');
});

If we group the tasks in this way, we'd expect Task1 and Task2 to run every minute between 07:00 and 21:00 from Monday to Saturday (which works correctly) and Task3 to run once at 23:45 from Mon - Sat (which isn't the case) - Task3 never runs in this case, which we think is because the scheduler gets confused somehow and wants to run Task3 between 07:00 and 21:00 at 23:45.

If we schedule Task3 to run at an hour between 07:00 and 21:00 it works as expected, such as in the example below:

Schedule::days([1, 2, 3, 4, 5, 6])->group(function () {
    Schedule::between('07:00', '21:00')->group(function () {
        Schedule::call(Task1::class)->everyMinute();
        Schedule::call(Task2::class)->everyMinute();
    });

    Schedule::call(Task3::class)->at('08:00');
});

So it seems the call to between in the subgroup somehow messes with anything defined in the main group. We've resolved it for now by defining the schedule like:

Schedule::days([1, 2, 3, 4, 5, 6])->between('07:00', '21:00')->group(function () {
        Schedule::call(Task1::class)->everyMinute();
        Schedule::call(Task2::class)->everyMinute();
});

Schedule::days([1, 2, 3, 4, 5, 6])->group(function () {
        Schedule::call(Task3::class)->at('23:45');
});

Not sure if this is an actual bug or not, but I feel like approach nr. 1 should work, since nested grouping is supposedly supported and works in most cases except cases where you define different times with between and at and such.

Steps To Reproduce

Define some scheduler tasks in groups in a similar way as described above. The task that should run outside of the between window once per day will not run unless its time is within the between window.

Octane Version

v2.3.10

Laravel Version

v11.6.0

PHP Version

v8.3.6

What server type are you using?

FrankenPHP

Server Version

v1.1.4 PHP 8.3.6 Caddy v2.7.6

Database Driver & Version

Postgress

Description

Last week we updated our app previously using php-fpm running on Forge to use Laravel Octane with FrankenPHP. Our site is mostly an API that handles analytics events (Like google analytics). It uses the default Laravel api throttling.

In staging our app worked fine (30 req/sec same IP), but when deploying to production (1400 req/sec, different IPs) it started to fail, giving a lot of 429 Too Many Requests.

I quickly rolled back to php-fpm and after a few hours tried again with the same problem. Rolled back and the next day I switched to Swoole and it worked perfectly without changing a single line of code nor having to redeploy anything. So I can confidently say that is NOT a bug in my code, but rather a bug with FrankenPHP or the Octane integration with FrankenPHP.

My theory is that the RateLimiter is not reseting between requests so it's shared between different users. So multiple different users trigger the rate limiter:

This is my Rate limiter configuration:

// AppServiceProvider

RateLimiter::for('api', function (Request $request) {
    return Limit::perMinute(60)->by($request->user()?->id ?: $request->ip());
});

our production CACHE_STORE is redis. Throttling worked perfectly fine without octane and with octane but using Swoole. It failed with hundred of 429 Too Many Requests after installing FrankenPHP.

This is our bootstrap/app.php:

<?php

use Illuminate\Foundation\Application;
use Illuminate\Foundation\Configuration\Exceptions;
use Illuminate\Foundation\Configuration\Middleware;
use Illuminate\Support\Facades\App;

return Application::configure(basePath: dirname(__DIR__))
    ->withRouting(
        commands: __DIR__.'/../routes/console.php',
        health: '/up',
        then: function () {
            Route::middleware('api')
                ->prefix('api')
                ->as('api.')
                ->domain(config('app.domain'))
                ->group(base_path('routes/api.php'));

            Route::middleware('web')
                ->domain(config('app.domain'))
                ->group(base_path('routes/web.php'));

            Route::middleware('web')
                ->domain(config('playsaurus.ads.domain'))
                ->group(base_path('routes/ads.php'));
        }
    )
    ->withMiddleware(function (Middleware $middleware) {
        $middleware->throttleApi();

        $middleware->redirectTo(
            guests: '/login',
            users: '/',
        );

        $middleware->web(append: [
            \App\Http\Middleware\HandleInertiaRequests::class,
            \Illuminate\Http\Middleware\AddLinkHeadersForPreloadedAssets::class,
        ]);

        $middleware->api(append: [
            \App\Http\Middleware\ConfigureLocale::class,
        ]);

        $middleware->alias([
            'localize' => \App\Http\Middleware\ConfigureLocale::class,
            'embed' => \App\Http\Middleware\AllowsEmbeding::class,
        ]);
    })
    ->withExceptions(function (Exceptions $exceptions) {
        $exceptions->dontReport([
            \App\Services\Announcements\InvalidVariantKey::class,
            \App\Exceptions\CouponRedeemException::class,
        ]);
    })->create();

Steps To Reproduce

It's difficult to reproduce. Because I can't test it in production because that would mean a lot of downtime for our users.

My theory is that it would be possible to reproduce from multiple different IPs. But since I don't have the means to test it, I don't know.

What happened?

I just installed package and complement for AI powered solution. When I create an issue to test it I get :

I had to change the links function like this to make it work for me:

public function links(): array
{
    $rawText = Str::finish($this->rawText, 'ENDLINKS');

    $textLinks = $this->between('LINKS', 'ENDLINKS', $rawText);

    $textLinks = explode(PHP_EOL, $textLinks);

    $links = [];

    foreach ($textLinks as $textLink) {
        $textLink = str_replace('\\', '\\\\', $textLink);
        $textLink = str_replace('\\\\\\', '\\\\', $textLink);

        $decodedLink = json_decode($textLink, true);

        if ($decodedLink !== null) {
            $links[$decodedLink['title']] = $decodedLink['url'];
        }
    }

    return $links;
}

How to reproduce the bug

When I install the package in my project and use it with AI powered

Package Version

1.0

PHP Version

8.2.14

Laravel Version

11.14

Which operating systems does with happen with?

Windows

Notes

No response

Is LDAP support planned? I saw there was a lot of interest in this with version 2. Would be nice to have this onboard for v3. There is a package available https://github.com/DirectoryTree/LdapRecord-Laravel https://chrispian.com/laravel-filament-tutorial-customize-login-to-use-ldap

Package

filament/filament

Package Version

v3.3.13

Laravel Version

v11.44.7

Livewire Version

v3.6.3

PHP Version

v8.4.6

Problem description

After pressing "Select" to upload certain image nothing happens (no error too). Just nothing.

In logs I see that livewire getting null. Method multuple() is causing problem.

3 Android devices were tested. One of them: Samsung S21 FE (Android 14). On iOS and macOS, Windows everything is working.

Expected behavior

Image previews are shown (DB storing is not expected for testing this bug)

Steps to reproduce

Open Android phone Go to post creation http://filament-android-issue.devope.ru/admin/posts/create Upload multiple images at once

Reproduction repository (issue will be closed if this is not valid)

https://github.com/devope/filament-android-issue

Relevant log output

Package

filament/filament

Package Version

v4

Laravel Version

v12

Livewire Version

v3

PHP Version

8.3

Problem description

if using ->tenant() with ->navigation(false), the tenant menu doesn't open properly on safari

https://github.com/user-attachments/assets/456d4270-c57a-4b12-880a-1c6d7377e90d

Expected behavior

menu stays open after clicking

Steps to reproduce

use safari, ensure navigation->false() as in repo, attempt to open tenant switch end

Reproduction repository (issue will be closed if this is not valid)

https://github.com/andyov17/filament-tenant-issue

Relevant log output

When you install a UX package, if you have AssetMapper installed, we importmap:require the packages you need. We should also importmap:remove those when the package is uninstalled.

https://github.com/symfony/recipes/issues/1089#issuecomment-1885459144

What happened?

After installation, I noticed that in the browser console it outputs an error of wireEl is undefined.

How to reproduce the bug

Just install this package in a livewire project, preferable with Filament's admin package. And see the browser console.

composer create-project laravel/laravel test;
composer require filamentphp/filament;
composer require spatie/laravel-blade-comments;

Then go through the browser console and see the error

Package Version

1.0.1

PHP Version

8.2.0

Laravel Version

10.13.0

Which operating systems does with happen with?

macOS

Notes

Filament ......................................................
Packages ...... filament, forms, notifications, support, tables
Version .............................................. v2.17.44
Views ..................................... PUBLISHED: filament

Laravel Version

12.20.0

PHP Version

8.4.7

Database Driver & Version

No response

Description

I get an error: Unclosed '[' on line 93 does not match ')'

On this code:

@json([
    'items' => $helpers['benefit']['getAll']()->map(fn($item) => [
        'icon' => $item->icon,
        'title' => (string)$item->title,
        'description' => (string)$item->description
    ]),
    'translation' => '%:booking.benefits%'
])

This is syntactycally valid and the thing is that just by removing the description line it works:

@json([
    'items' => $helpers['benefit']['getAll']()->map(fn($item) => [
        'icon' => $item->icon,
        'title' => (string)$item->title
    ]),
    'translation' => '%:booking.benefits%'
])

I've tried replacing the description item by just

'a' => 'a'

And it throws error too, I've tried with trailing coma after title and crashes, with and without after description and a lot of things I've tried to thing of, but no lick finding a pattern.

BTW if you are wondering it's mapped instead of ->map->only because I need to cast the objects returned by the model with the __toString magic function, it's a custom object cast I made.

As a temp solution I just use this, which shows the prior is ok and works fine:

{!! json_encode([
    'items' => $helpers['benefit']['getAll']()->map(fn($item) => [
        'icon' => $item->icon,
        'title' => (string)$item->title,
        'description' => (string)$item->description
    ]),
    'translation' => '%:booking.benefits%'
], JSON_UNESCAPED_UNICODE | JSON_UNESCAPED_SLASHES) !!}

Steps To Reproduce

Just mockup the collection I have by placing this before the @json:

@php
    $helpers['benefit']['getAll'] = function () {
        return collect([
            (object)[
                'icon' => 'test',
                'title' => 'test',
                'description' => 'test',
            ]
        ]);
    };
@endphp

Package

filament/tables

Package Version

v4.0.0-beta22

Laravel Version

v12.21.0

Livewire Version

v3.6.4

PHP Version

PHP 8.4.11

Problem description

When using ->summarize() on a database connection with a "prefix", an error like "no such column: myprefix_myprefix_mytable.mycolumn" will be thrown.

Expected behavior

->summarize() can handle prefixed tables as well, without throwing an exception

Steps to reproduce

• in config/database.php, set any 'prefix'
• on a Filmanet resource table column (in example TextColumn), add a summarizer ->summarize(Sum::make())

Reproduction repository (issue will be closed if this is not valid)

https://github.com/softwaretechniker/filament-bugs-summarize

Relevant log output

SQLSTATE[HY000]: General error: 1 no such column: test_test_summarized_data.value (Connection: sqlite, SQL: select sum("test_test_summarized_data"."value") as "RQAlvga7lxoF1hDe" from (select * from "test_summarized_data") as "test_summarized_data")

Dashboard showing Operational

Front end showing no issues, but the status seems to still be linked to the incident even if it's closed as fixed

In raising this issue, I confirm the following (please check boxes):

• I have read and understood the contributors guide.
• I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.
• I have checked that the bug-fix I am reporting can be replicated.

Description of the problem

One of the important reasons for using hyperscript is that it handles escaping of characters which are reserved in html. Which prevents XSS.

spatie/html-element does not do this. Mainly because it uses strings as intermediate format instead of an object representation of the DOM.

What about allowing displaying post-install messages again, eg when running this?

composer recipes the/package

Hi,

With the polyfill, var_dump(mb_strlen(chr(254))) return 0. With the php8.0-mbstring extension, var_dump(mb_strlen(chr(254))) return 1;

versions : * v1.26.0

Thanks, Alex

Hi, I noticed this issue after trying to use the attachments while making use of this webhook package.

This issue has already surfaced once in issue 170 and continued in discussion 171, however it was not solved.

I have added log proof of this issue as previously asked on the older thread to indicate the differences between the Laravel request and the webhook call request. Full logs can be found in the attached files.

request()->all().log $this->webhookCall.log

Data from "request()->all()" 'attachment_details' => array ( 0 => array ( 'disposition' => 'inline', ), 1 => array ( 'content_id' => NULL, ), ), 'attachments' => array ( 0 => \Illuminate\Http\UploadedFile::__set_state(array( 'originalName' => 'image0.jpeg', 'mimeType' => 'image/jpeg', 'error' => 0, 'originalPath' => 'image0.jpeg', 'test' => false, 'hashName' => NULL, )), ),

Data from "$this->webhookCall" 'attachment_details' => array ( 0 => array ( 'disposition' => 'inline', ), 1 => array ( 'content_id' => NULL, ), ),

Code used to log this data

\Log::info('Request Data');
\Log::info(request()->all());

\Log::info('Webhook Call Data');
\Log::info(json_decode($this->webhookCall, true));

Package

filament/tables

Package Version

3.3.14

Laravel Version

11.44.7

Livewire Version

3.6.3

PHP Version

8.3.19

Problem description

When I use the search field to filter data, horizontal scrolling no longer works on mobile devices. I encountered the same problem in the demo (https://demo.filamentphp.com/shop/products). Trying to filter the data, it becomes impossible to scroll horizontally.

Expected behavior

horizontal scrolling also with filtered data on mobile

Steps to reproduce

Trying to filter the data

Reproduction repository (issue will be closed if this is not valid)

https://github.com/filamentphp/demo

Relevant log output

Describe the bug

When you attempt to dump a binary string or anything containing one (like an array or an object), Ray does not dump anything. It just fails silently.

Versions

Ray version (you can see this in "About Ray"): 2.8.1

You can use composer show to get the version numbers of:

• spatie/ray package version: 1.41.2
• spatie/laravel-ray package version (if applicable): 1.37.1

PHP version: 8.2.17 Laravel version (if applicable): 11.18.1

To Reproduce

Add this in your code:

ray(hex2bin('ae0f3d'));

Expected behavior

Ray should display this (like the console when dump is used):

b"®\x0F="

Desktop (please complete the following information):

• OS: MacOs
• Version: 14.6.1

using prompt engineering techniques provide enhancement to the Claude service class in the Claude prompt class, creating functions commonly used in Laravel applications. For example, brand builder, seo product optimizer, video and or image captioner, automated chatbots #goodfirstissue

Add in PHP 7.3 as Normalizer::normalize() argument for NFKC_Casefold normalization.

Package

filament/filament

Package Version

v3.3.31

Laravel Version

v12

Livewire Version

No response

PHP Version

PHP 8.3

Problem description

Hi, I'm experiencing an accessibility issue with Filament form components that have live() enabled. When a ToggleButton or Radio button triggers dynamic updates (e.g., updating a Placeholder component), the form elements become unresponsive to keyboard navigation.

https://github.com/user-attachments/assets/1cb3e3ad-7288-4306-ba64-bca1b95dc0cb

Expected behavior

Expected behavior:

• Should be able to change Radio button selections using arrow keys
• Should be able to toggle ToggleButtons using Space/Enter
• Focus should remain on the current element after live updates

Actual behavior:

• After the first selection, the Radio and Toggle button cannot be changed using keyboard
• The only workaround is to Tab to the next element and then Tab back

Steps to reproduce

1. Create a form with ToggleButtons or Radio buttons that have live() enabled
2. Add dependent components (like Placeholder) that update based on the live values
3. Navigate using keyboard (Tab) and select an option
4. Try to change the selection using keyboard

Reproduction repository (issue will be closed if this is not valid)

https://github.com/alanost/filamentphp.accessibility-focus-with-live

Relevant log output

Many of them are out of date, some by a few major versions!

It would be great to get these into good order and start keeping them up to date

When attempting to filter tests by test or file name pressing the "Enter" key has no effect.

Pressing "Enter" at the default screen correctly triggers a "test run" where all tests are run.

It was pretty simple to add so I'm adding this here both for documentation purposes, but also this is probably something really helpful to enable by default if you use Encore.enableReactPreset()...

npm install @pmmmwh/react-refresh-webpack-plugin react-refresh

if(Encore.isDevServer()) {
  const ReactRefreshWebpackPlugin = require('@pmmmwh/react-refresh-webpack-plugin');
  Encore.addPlugin(new ReactRefreshWebpackPlugin());

  Encore.configureBabel(config => {
    config.plugins.push(require('react-refresh/babel'))
  });
}

Octane Version

2.6.1

Laravel Version

11.41.3

PHP Version

8.3

What server type are you using?

Roadrunner

Server Version

2024.3.2

Database Driver & Version

No response

Description

ok this is in the borderline to be a bug but i write it anyway.

i am deploying using deployer , i suppose will happen for any Zero Downtime Deployments.

/releases/99/
/releases/100/
/releases/101/ 

and then a symbolic link from the latest release to /current , all pretty standard.

the problem come when running artisan octane:start vendor/laravel/octane/src/Commands/StartRoadRunnerCommand.php

will set roadrunner server with '-o', 'server.command='.(new PhpExecutableFinder)->find().','.base_path(config('octane.roadrunner.command', 'vendor/bin/roadrunner-worker')),

where base_path(...) will resolve to /releases/101/ not to /current

so in next deployment e.g. (/releases/102/) , when we run artisan octane:reload it will still use old /releases/101/ source code (i checked and yes if i go back to /releases/101/ and make a change it will be present after artisan octane:reload).

the solution is very simple, in config/octane.php you just need to add:

    'roadrunner'=>[
        'command' => env('OCTANE_ROADRUNNER_WORKER_PATH', base_path('vendor/bin/roadrunner-worker')),
    ]

OCTANE_ROADRUNNER_WORKER_PATH=../../current

would be nice is this added to config/octane.php , and maybe don't use base_path

or even better a option to provide the path in octane:start

Steps To Reproduce

deploy a octane laravel app using deployer , octane:reload will not work as expected

AST, or "abstract syntax tree", creates the expectation of a nested tree structure. In the case of a query string, the AST will only ever be one level deep; as multi nodes are combined into one.

If anyone wants to suggest a better, more clear name: you're welcome.

NotOrm Package

The goal is to make abstract code based on the package notorm to build a new orm system

https://www.algolia.com/doc/libraries/javascript/v5/upgrade/

When encountering nested tokens, they are parsed only during formatting, not when compiling the pattern. And the type of tokens are validated only during the rendering as well. But the native implementation detects such error during the instantiation: https://3v4l.org/Sf69D This means that the error handling required for the polyfill is not the same than for the native implementation.

These messages aren't displayed: https://github.com/symfony/flex/blob/1.x/src/Configurator/DockerComposeConfigurator.php#L51

Currently, for plural rules, the MessageFormatter polyfills uses the English rules for all locales (it ignores the locale). To be consistent with what we do in symfony/intl (used by symfony/polyfill-intl-icu to implement NumberFormatter and DateFormatter), we should rather fail explicitly here (using the English rules for a different locale would not give the right result anyway)

Describe the bug logUnguarded() works provided that $guarded is set explicitly in the model. If it is not set explicitly but globally set, say in AppServiceProvider using Model::unguard(); then nothing is logged.

To Reproduce

1. remove $fillable and $guarded from a model that use uses LogsActivity
2. call Model::unguard(); in AppServiceProvider in the boot method
3. set

    public function getActivitylogOptions() : LogOptions
    {
        return LogOptions::defaults()->logUnguarded();
    }

4. Make some changes to a model and save them

Expected behavior Some changed properties should be logged but none are

Versions (please complete the following information)

• PHP: 8.1
• Database: MySql
• Laravel: 9.38
• Package: larvel-activitylog

For some reason, our test suite is super slow. We should look into this and try to decrease memory usage and speed it up.

Parallel run:

  Tests:    316 passed (785 assertions)
  Duration: 13.64s
  Parallel: 10 processes

Regular run:

  Tests:    316 passed (785 assertions)
  Duration: 96.30s

Package

filament/filament

Package Version

v3.3.14

Laravel Version

v12.13.0

Livewire Version

No response

PHP Version

8.2

Problem description

I have Brand Resource with Categories Relation Manager.

In Categories Relation Manager, I have repeater for Menu Items that has File Upload for image.

After submitting the form: It doesn't let me click on the 'x' button to remove the image. Also when changing the image, it doesn't work. Need to upload the image twice.

Expected behavior

On clicking 'x' it should remove the image as it does normally. Uploading image on edit should work as intended.

Steps to reproduce

Use the repo I created. In that first create a brand, then create category with menu items. Now upload image for 1 menu item and save. Now open the same category with menu item and try removing the image. Doesn't work. Now try to change the image of that menu item, there will be an issue. Need to upload the same image twice.

Reproduction repository (issue will be closed if this is not valid)

https://github.com/faizanakbar10/filament-fileupload-repeater-issue

Relevant log output

I would love to see support for oAuth in Catchet. I know there are some other (closed) issues requesting the same functionality, but I think this would be a great addition for Catchet.

Package

filament/filament

Package Version

v3.x – Filament Demo site

Laravel Version

Whatever is used in the Filament Demo site as of today

Livewire Version

v3.x – Filament Demo site

PHP Version

Whatever is used in the Filament Demo site as of today

Problem description

See the following for a video demonstration of the issue on Filament's demo site: app.birdeatsbug.com/vmq0tUZ66zl2wkfJydzNXVUP3kI-pnGC-bxe2Uqua1ES

Navigating away from, and back/forward via the browser to, a Filament form does not rehydrate the form fields in question, resulting in an unexpected null error for said input, even when the browser has a non-null value for the form field.

Expected behavior

Expected that the submission of the form would reflect the visual state of the form fields.

Steps to reproduce

See the following for a video demonstration of the issue on Filament's demo site: app.birdeatsbug.com/vmq0tUZ66zl2wkfJydzNXVUP3kI-pnGC-bxe2Uqua1ES

This appears to be because the form fields are not rehydrated on browser back/forward cache.

Reproduction repository (issue will be closed if this is not valid)

https://github.com/johnbacon/demo

Relevant log output

Hi 👋🏼!

I am coming here to gather some feedback on my idea before starting working on it.

Background

I wanted to create a POC of https://github.com/symfony/skeleton made for Sylius. I created a simple recipe for sylius/core-bundle, then an example skeleton repo and I have found out my recipes does not work as another recipe already write files with the same name. Then, I noticed symfony/framework-bundle is always put as the first recipe to be executed, and this is a thing I wish to be able to configure.

Goal

Somehow allow myself to make (in this POC case) sylius/core-bundle as a first recipe to be executed. Of course, I can fork symfony/flex, but it would be perfect to avoid this way.

Idea

The idea is simple, we allow configuring such list for example in this way:

{
    ...
    "extra": {
        "flex": {
            "prioritized-recipes": [
                "sylius/core-bundle",
                "another/sylius-package",
                ...
            ]
        }
    }
    ...
}

In Flex we could implement this +/- this way:

        // symfony/framework-bundle recipe should always be applied first after the metapackages
        // however, we allow to override it with a list of prioritized recipes
        $recipes = $this->getPrioritizedRecipes();
        $recipes = array_merge($recipes, [
            'symfony/framework-bundle' => null,
        ]);
        $packRecipes = [];
        $metaRecipes = [];

instead current

        // symfony/framework-bundle recipe should always be applied first after the metapackages
        $recipes = [
            'symfony/framework-bundle' => null,
        ];
        $packRecipes = [];
        $metaRecipes = [];

Why?

• In some projects, we may want to load our recipes before the Symfony's ones
• In frameworks based on Symfony (like Sylius) we need to set up the whole project in our own way, so framework-bundle as a first recipe to be executed makes it unable for us

Other options

I have not checked it yet, but I believe we can achieve the similar feature using Composer's Event Dispatcher. But first, I would like to hear if such a feature is welcomed. Or maybe you have a better idea how to solve this. I am open to provide such feature right after we agree on some solution.

Hello,

if you plan an scheduled maintenance with an START and END date it will never appear on the dashboard. Only if you create them with an START date only it will appear. I think this is a bit confusing, because if i plan an schedule an weekly update, i want to declare an timeslot and dont want to enter again the cachet-scheduled-maintenance to enter an date at the end of my maintenance.

Can this function be controlled or changed?

Thanks

There's no Expectation to expect a class to use HasRequestPagination rather than HasPagination.

Description: I am using Flasher 2.0.1 in my Laravel 11 project and would like to know how to properly use the Flasher library in JavaScript. Additionally, I want to ensure that the JavaScript configuration is consistent with the settings defined in the flasher.php configuration file.

Details: Flasher Version: 2.0.1 Laravel Version: 11 Problem: Need guidance on using the Flasher library with JavaScript in a way that mirrors the configuration set in flasher.php.