Closed omoustaouda closed 1 year ago
I am running this module on numerous v4.4 and 4.5 sites and never had any issues with dev build. Can you tell us more about your hosting environment. Using an alias or not shouldn't matter so while this is acceptable it still shouldn't be needed
This PR is fixing the import name collisions that appears when the module is used with SilverStripe 4.4.4.
The issue is: when running
$ vendor/bin/sake dev/build flush=all
this error is appearing:
the 2 files affected are:
src/Adapter/ProtectedCachedAdapter.php
andsrc/Adapter/PublicCachedAdapter.php
currently in
src/Adapter/
PublicAdapter.php
andProtectedAdapter.php
are already using the class aliased:use SilverStripe\Assets\Flysystem\ProtectedAdapter as SilverstripeProtectedAdapter;
After applying the changes in this PR, the error is not appearing and
sake dev/build
can proceed.