-
PackagePanel builder Package Versionv3.2.122 How can we help you?I have an application which has been running successfully for some time, but which is now failing with the error in the title. This happens only on the server, in both a production and a staging instance. However, on my development desktop, it runs perfectly. Immediately prior to this error, I did "composer update" on the staging and production instances. I did that in my development environment, and that continues to work as expected. I have cloned a copy of the repo onto both the development workstation and the server, and the problem occurs on the server test but not the workstation test. Both environments are running on Apache, without any containers, etc. The error occurs on every route, and the source is a Filament view, which differs according to the route. an example is The view blade files are identical between the development instance, and the staging and production instances. Laravel version in all cases is 10.48.22 This must be something simple I am overlooking which I can't find. I would appreciate any help or suggestions. This is the staging URL: https://staging.targetlab.co.za/ |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Beta Was this translation helpful? Give feedback.
I think you are right, but I am still mystified.
It is now working as expected - I ran filament:upgrade and the problem went away.
I had done this many times already, and it didn't work, but now it did.