Skip to content

Can we take over the elfinder's view path? #32

Open
@tabacitu

Description

@tabacitu

Right now what we do is that we publish blade files in the elfinder view path. In order for elfinder to use our custom views. But this creates problems... upgrading is difficult. Because those files need to be deleted and re-published.

Isn't there a way for us to "take over" that blade namespace? And point it to our blade views in the package?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions