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
fm_elfinder:
#assets_path: / # default is /assets, this is where css/js elfinder files are
...
, and it seems that the assets_path parameter is defined but not utilized within the templates. However, it is used in ElFinderController and passed to template parameters
Am I correct in assuming that this parameter is presently non-functional?
I did notice that there is a pull request (PR) available at https://github.com/helios-ag/FMElfinderBundle/pull/509/files. If this PR is accepted, it may impact the current project configuration. In such a scenario, would the elfinder:install command need to be executed with the --docroot=<assets_path> flag?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi.
I've reviewed the configuration
, and it seems that the assets_path parameter is defined but not utilized within the templates. However, it is used in ElFinderController and passed to template parameters
Am I correct in assuming that this parameter is presently non-functional?
I did notice that there is a pull request (PR) available at https://github.com/helios-ag/FMElfinderBundle/pull/509/files. If this PR is accepted, it may impact the current project configuration. In such a scenario, would the elfinder:install command need to be executed with the --docroot=<assets_path> flag?
Could you please clarify this for me?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions