You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the same File name is longer than the maximum allowed path length on this platform (4096) error on Ubuntu (not on MacOS) as mentioned in laravel/framework#32254, in case the rendered livewire content is relatively large. Smaller content doesn't give me problems.
file_exists(): File name is longer than the maximum allowed path length on this platform (4096): resources/views/<div> <here the entire rendered view is shown>
The text was updated successfully, but these errors were encountered:
I found the cause for this; it is not related to Livewire.
For reference; I was using Laravel Blade Components and returning the template as a string from the render method, instead of a blade view template. Some of them were pretty long and caused this error.
Just stumbled onto this on my Ubuntu testing server. I'm generating large html tables using multiple builder classes.
In Laravel 8 you can return instance Htmlable for which Laravel provides HtmlString.
Not perfect solution, but it was good enough in my case.
I'm running into an issue after deploying code to an Ubuntu server, that is similar to the issue described here: laravel/framework#32254
It's suggested by dries, that the issue is caused by calling render() on a view where the template does not come from a file.
Render is being called here:
livewire/src/Component.php
Line 130 in aee1c2b
The view template (not from a file) comes from here:
livewire/src/LivewireBladeDirectives.php
Line 24 in aee1c2b
I get the same
File name is longer than the maximum allowed path length on this platform (4096)
error on Ubuntu (not on MacOS) as mentioned in laravel/framework#32254, in case the rendered livewire content is relatively large. Smaller content doesn't give me problems.file_exists(): File name is longer than the maximum allowed path length on this platform (4096): resources/views/<div> <here the entire rendered view is shown>
The text was updated successfully, but these errors were encountered: