My question would be if it’s possible in any ways to swap the deleted picture (position in the field of previous image) with the croppie one I’m saving after editing it and pressing a save button ( in croppie group)?
It could be possible to swap positions if " created date" was editable but it isn’t.
Therefore you need to change your DB structure.
Instead of the list of images make certain DB with 2 fields.
1 field - image is self
2 field - count ( number type)
Then connect it to whatever you need as a list of images
Now you can make RG with them and sort it by count.
And when you delete a certain cell of the image you can create a workflow to swap counts with each other.
So I’m using croppie plugin and designed a group where I can crop, flip, whatever then save the result image but it gets messy with the extra type (list of image) I made. It’s working but it’s not what I want, you have number 1 group, then 2, 3,etc… But when deleting image 2, the group 2 even collapsed still takes width and moreover the position 2.
So need to go back where I started with a rg and the list of image included as a field in my items type.
This wasn’t the right plugin, but the ezcode dragNdrop is what I would need. Must be a way to code this
I noticed the same thing when the cell is deleted the width keep. That might be a bug. I fixed it by adding conditions.
" When this group’s image is empty"
This is element is visible.
Well as I said it looks too messy. If I want 10 groups for 10 pictures it’s a lot of backed conditions. I just need a rg.
The drag and drop plugin solves one of those feature the listing group would have and highlights the fact that there is a possibility to have some backend code doing something similar but when editing then saving the picture with croppie or other plugins.
1) What you will have to do is to save the index of the picture you are editing as a custom state (let’s call it “pic_index”). So, if you are editing the image3.jpeg, your custom state pic_index will be 3.
2) Now you will run a workflow to save the first elements of the list in another costum state (list type). Let’s call this custom state “temp_list_1”. So you will record all the elements of the original list UNTIL index 2 (that will be the value of your custom state “pic_index” minus 1).
The temp_list_1 should be “image1.jpeg, image2.jpeg”
You will also have to save the last pasrt of the list in another custom state (list type). Let’s call this custom state “temp_list_2”. So you will record all the elements of the original list FROM index 4 (that will be the value of your custom state “pic_index” plus 1).
The temp_list_2 should be “image4.jpeg, image5.jpeg”
Now, what you have to do is to clear the original list and add all the separeted parts to rebuild it as before. Something like:
This is happening because you don’t have the last part of the list. This same behavior should be expected if you edit the first image, because you will not have the first part…
So what you can do to prevent this error is split the “add” to list action in trree separated parts instead of do it all at once as you shared in your image below.
Making this restriction you will prevent erros when editing the first image. Because if you are editing the first image, there is no “temp_list_1” to be added…
And you will add temp_list_2 ONLY WHEN pic_index < repeating_group:count
Making this restriction you will prevent erros when editing the last image. Because if you are editing the last image, there is no “temp_list_2” to be added…
