-
Notifications
You must be signed in to change notification settings - Fork 3
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
Upload replacement for Isotope #52
Comments
Its not possible to replace the isotope uploader widget with the valums widget via dca replacement? |
nope. Isotope uses a very special upload widget.
what could be done is really to just replace the "upload" button part of the widget, e.g. we'd have to write a new widget. |
For compat with the upcomming isotope 1.4.0 release (after 1.4.0beta2),
|
Hello, just wondering with the release of Isotope 1.4.0rc1, how do I get valumsFileUploader to work with that one correctly.? It is displayed and it also "uploads" the image but neither is it resized nor is it replaced in Isotope. Even with the above mentioned change to ValumsBeFileUpload::uploadTo EDIT: |
auto refresh is not suitable, because it would launch a reload as soon as all uploading files are completed, even if you are just selecting another file to upload, which will be closed automatically. |
I meant only for the pictures (Ajax like) not the whole product but I guess Isotope would require an update then. However, what would be great would be a button that basically does the same as save product, just that it is directly under upload because that way it would be clearer what to do. |
Since we can't use the widget as-is, perhaps you can ease the story for others to develop a version that integrates with isotope as well. Then people can just install e.g. isotope_valums and it will replace the tl_iso_products uploader with a values file uploader to upload multiple files. Maybe this is a bit too complex, because the isotope uploader is also a bit more than that.
The text was updated successfully, but these errors were encountered: