-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
1.9 unset fix #1561
1.9 unset fix #1561
Conversation
…all dropzone elements, even if they are set to multiple
…ed bug of unset affecting multiple image fields (such as a list)
Why do you have 74 files changed Ryan? Did you start from admin develop branch? Should only have the files you actually modified. |
Here was my process. Please let me know how I should do it differently.
When I follow this procedure, it obviously doesn't work well. It applies my original pushes described in the step How should I be doing this? |
It’s a little bit hard to follow what’s going on and what changed |
Just following up on this. But, I've explained every line in my main commit. I just have no way to do the PR against the 1.9 branch. I researched and I'd have to fetch upstream and do some other git related stuff that I flat out aren't that comfortable with or good at. I appreciate any assistance here. This fix would help so many clients |
@hdwebpros Everything is now merged to develop, so please try again. Github has very good documentation, so please read it, too. :) |
Fixed unset bug on 1.9 version. Not sure how to do this cleaner. The two commits I did that are noteworthy are:
135387e
264967a
I have 4 clients that have websites on Grav that use the same images on more than one page. That is why they need unset. If they delete the image, it gets removed from other pages too. Unset just removes the image but allows it to be on other pages.
The bug right now is that if you have a blueprint with more than one area for images, unset effects everything and sets everything to one image. These commits fix that. Tested locally.