-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap Image Field $src in asset #75
Comments
Yeah I could, I'm surprised this would be enough of a fix, though. Are you not using the Croppa helpers on your public site? How is your Laravel configured so that Just trying to find the most comprehensive fix possible with these questions. Relates a bit to #63 |
I am using a couple different strategies to tackle the sub-directory issue. I have created a Service Provider:
I have also set up a env var that I change based on environment that I use in config/decoy/core to properly get path for assets and in config/decoy/site to properly set nav paths. The asset wrap would cover the instance where the image is not showing in the admin |
To get correct routes to destroy, I have also had to customize the shared footer haml files to use
to
|
Can we wrap the $src below from Bkwld's Image field in the asset method so it plays nice with Laravel sub-directory installs? Bkwld\Decoy\Fields\Image::renderEditor()
Tried using the container to override and running into issues with private methods and instances being new'd up instead of being made from the container.
The text was updated successfully, but these errors were encountered: