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
Make sure both Splade packages (JS + PHP) are up-to-date and on the same version. For example, when using version 0.5.0 of the PHP package, you should use the same JavaScript package version.
Description:
When clicking on a Splade Link to a route that was created with Splade and also has the corresponding middleware, the error appears: "The response is not a Splade response. Did you use the Splade Middleware on this route?" - the link does not "open".
If you enter the relevant URL in the browser, the page works, but there are three zeros before the doctype in the HTML source code. It then looks something like this: https://imgur.com/l8Udu7P - Also, third party components like Filepond don't work correctly (wrong styling) on this page.
Locally, in development mode, this issue doesn't occure.
Steps To Reproduce Issue:
I can share a url link to a production enviroment where the issue is demontrated.
The text was updated successfully, but these errors were encountered:
You may use the built-in Artisan Command to show the installed versions of the packages:
Make sure both Splade packages (JS + PHP) are up-to-date and on the same version. For example, when using version 0.5.0 of the PHP package, you should use the same JavaScript package version.
Description:
When clicking on a Splade Link to a route that was created with Splade and also has the corresponding middleware, the error appears: "The response is not a Splade response. Did you use the Splade Middleware on this route?" - the link does not "open".
If you enter the relevant URL in the browser, the page works, but there are three zeros before the doctype in the HTML source code. It then looks something like this: https://imgur.com/l8Udu7P - Also, third party components like Filepond don't work correctly (wrong styling) on this page.
Locally, in development mode, this issue doesn't occure.
Steps To Reproduce Issue:
I can share a url link to a production enviroment where the issue is demontrated.
The text was updated successfully, but these errors were encountered: